Good catch. My only excuse is I was editing Paul's programs and re-posting them, and he was just starting from the example. I didn't delete the compare block. These days I don't use the CANbus status register in my logic - it is more of an informational tool. Like this error counter:
I've found UniCAN to be extremely reliable if you don't overthink it.
My reply could be read as "speed is of the essence'', but it's not true. What I want to do is run UniCan as it appears in it's description, and have it totally reliable. I can only get this to work by having calls being made at a given periodic speed. There is a fine time interval that the joined systems will tolerate. Cabling is spec and only quite short runs less than 2m.
My eagerness to do it like you say is to have it done "properly". It has always seemed a bit odd that having a request sent periodically via the ladder always has the potential for a conflict with another request somewhere else on the loop. Especially doing it with a "defined" time interval. It is unlikely, but entirely possible, that calls from different plcs could coincide exactly, and do so for some time if based on something like SB 13 or 15.
I think at the moment that I'd love the Creators to chime in and explain exactly how it all works, how the loop reacts to different plc calls etc. Help gives information, but I think it could go into a lot more depth, covering things like Structs etc. The "mechanics"of how it all works ok, including any time allowances for the amount of data zinging around, would be nice to know.
It is only logical, Captain, that more data means more time needed!
@Saragani @AlexUT @Cara Bereck Levy ?