Hi NI,
I spent most of the afternoon troubleshooting a strange error with the XNET Flush.vi that did not sem to behave properly. After much investigation, my tentative conclusion is that some of the following:
- A XNET session is opened as "Frame Out Stream"
- With a cluster defined as ":can_j1939:"
- And you send messages that have a payload of 8 bytes or less
- On a bus that is empty (i.e. no other CAN device to acknowledge)
At times, cause these results:
- Property node XNET Session -> Number Of Values Pending ALWAYS returns zero (0)
- XNET Flush.vi doesn't work and after a period long enough, you get error -1074384888
If I change my payload to 9 bytes or more, then both the property node and the Flush work. [Edit: This is not always the case in the end. However, sometimes it helps the buffer works...]
This has been nagging me on both XNET 15.5 and 16.1. Are there any open CAR about the Tx Buffer for J1939 sessions?!?!
Olivier
----------------------------
Refrence
Error -1074384888 occurred at an unidentified location
Possible reason(s):
NI-XNET: (Hex 0xBFF63008) A write queue overflowed. Solution: wait until queue space becomes available and retry.
