jsd
jsd copied to clipboard
Prestonr feature add wkc driver saves
Added a function that can be called by fastcat to confirm if jsd devices are operational at time of bad working counter. This will allow one to differentiate between situations where the CPU is overloaded and if there is simply poor physical connections to a device.
I have attached three pictures: The first being where the entire JSD device is turned off (corresponds to poor power to the jsd bus). The second where a single device at the end of the bus was unplugged (corresponds to a single bad device connection). The third being where the timeout for jsd_read was set to a very small number to force the underlying SOEM function to time out (corresponds to no faulty JSD connections).
TODO: Need to update the jsd tests to avoid test failures.