https://forge.codesys.com/forge/talk/Engineering/thread/7528a56515/2020-07-08T14:56:36.318000ZRecent posts to J1939 PGN Receive Timeout/Watchdog2020-07-08T14:56:36.318000Z2020-07-08T14:56:36.318000Zkohanrshttps://forge.codesys.com/u/kohanrs/https://forge.codesys.com80f66e00b3d97c18a559e24f85ba587bf8a1e38f

<div class="markdown_content"><p>Hello, Does anyone know the reason ReceiveParameterGroup Error flag get set if a Proprietary-A Peer-to-Peer PGN (0xEF00) is passed to it? It works fine with Proprietary-B PGNs ( 0xFFC2). Thank You</p></div>

2020-06-22T06:38:23.562000Z2020-06-22T06:38:23.562000Zsgronchihttps://forge.codesys.com/u/sgronchi/https://forge.codesys.com086676820ba5d92b51b8a1dba7beb0a32f617379

<div class="markdown_content"><p>Well, you need to build the ParameterGroup only once, so you can just call it the first cycle with xExecute = FALSE and from the second one with xExecute = TRUE, and connect ReceiveWatchdog.xEnable to ReceiveParameterGroup.xDone (if you want to be sure, interpose a latch between them).</p></div>

2020-06-21T12:47:16.769000Z2020-06-21T12:47:16.769000Zmr337https://forge.codesys.com/u/mr337/https://forge.codesys.com89e7636e660737eb6ad6f2c73b2caa564f790dc2

<div class="markdown_content"><p>Wanted to add that worked perfectly. An interesting thing is the ReceiveWatchdog has an xEnabled param while the ReceiveParameterGroup need a rising edge signal. I think as a general rule the rising edge frequency needs to be faster than the timeout on the ReceiveWatchdog.</p></div>

2020-06-18T22:26:12.845000Z2020-06-18T22:26:12.845000Zmr337https://forge.codesys.com/u/mr337/https://forge.codesys.com74a90750d62a3c3caf7b6ca4eb11357d05a7c42f

<div class="markdown_content"><p>Ah, I was some what close! I saw ReceiveWatchdog and thought it was only at the ECU leve. Gotta try this!</p></div>

2020-06-18T15:27:32.819000Z2020-06-18T15:27:32.819000Zsgronchihttps://forge.codesys.com/u/sgronchi/https://forge.codesys.com8e293e8cde31930b04a6aee9898001b8c40b9e62

<div class="markdown_content"><p>ReceiveParameterGroup is for "building" the needed data structure. You should pipe itfParameterGroup into ReceiveWatchdog: <a href="https://help.codesys.com/webapp/8LVZD-HU9xCDZg4RnKWx5CheJCc%2FReceiveWatchdog;product=IoDrvJ1939;version=3.5.14.0" rel="nofollow">https://help.codesys.com/webapp/8LVZD-HU9xCDZg4RnKWx5CheJCc%2FReceiveWatchdog;product=IoDrvJ1939;version=3.5.14.0</a></p></div>

2020-06-18T00:12:02.323000Z2020-06-18T00:12:02.323000Zmr337https://forge.codesys.com/u/mr337/https://forge.codesys.com8790bf69f3be2b7a86d556767428d2140b9d3147

<div class="markdown_content"><p>Hi All,</p> <p>I am looking into getting the last received timeout for a specific PGN. I am interfacing with a few actuators that use the same address ECU address 0, but different reporting PGN to separate the actuators. In addition the PGN does not have a heartbeat bit or byte of anykind. This is not ideal but outside our ability to change.</p> <p>In Codesys we build out an Actuator remote ECU and all actuators report back to the ECU, just under different PGNs. The issue is using the ECU watchdog will only check for a single message received. Since we have several actuators all but a single actuator could be disconnected and the watchdog won't trigger.</p> <p>So what I am trying to do is get the last received time for a particular PGN. Few things I have tried:</p> <ol> <li>Modifying the mapped PGN values to some value to mark it as dirty. New messages will reset the message knowing we received a proper message. Unfortunately the mapped values are read only.</li> <li>Use the J1939.ReceiveParameterGroup on a 1s timer to see if a PGN has been received. I can't seem to get anything out of the FB <code>itfParameterGroup</code> along with an eError of <code>WRONG_PARAMETER</code> and no clue how that isn't working.</li> </ol></div>