Quote:
Originally Posted by Joe Ross
The 2012 LabVIEW CAN Library implemented an isochronous mode. It does not block, but also doesn't look for the Ack. It's designed for sending periodic updates where you don't care if a particular message is received. There's a boolean input for whether you want isochronous or blocking.
|
I see the isochronous mode for the Motor Control Set, but nothing else.
I also see that Read Status sets a timeout of 0 for messages continually transmitted, but could also do a transaction (with 10ms timeout) if requesting something on-demand.
Everything else is still blocking (set parameters require Ack, read parameters are synchronous).
Really, CAN is designed to never care if a message is received, and to transmit everything continuously (with less important information at a slower rate). Having an Ack message makes no sense to me.
Edit: Motor Set defaults to synchronous mode, and the Isochronous input is not in the help. I'm guessing many teams still run in synchronous mode. It should default to isochronous mode, IMO.