Hostmot2 smart-serial (ALL) It is now possible to identify smart-serial remotes by their serial number rather than how they are connected to the system by setting use_serial_numbers = 1 in the loadrt hostmot2 line The effect it to change pin names from hm2_5i25.0.8i20.0.1.fault.U-current-not to hm2_8i20.ABCD.fault.U-current-not Where in the first example the 8i20.0.1 refers to the 8i20 plugged into the second channel of sserial port 1, and in the second example it refers to the 8i20 with a serial number with the last 4 digits ABCD. (There is a very small danger of serial number collision.) |
hm2_5i23.0.7i64.0.0.output-00 and hm2_5i23.0.7i64.0.0.output-00-invert |
hm2_5i23.0.7i64.0.0.output-00 and hm2_5i23.0.7i64.0.0.output-00-invert |
hm2_5i23.0.8i20.0.0.max_current changes to being controlled by two pins: hm2_5i23.0.8i20.0.0.current.maxlim hm2_5i23.0.8i20.0.0.current.minlim |
Either board version may run either firmware version, however. |
Either board version may run either firmware version, however. |
HAL_INPUT - pin name changed eg. input.0.btn.trigger should be renamed to input.0.btn.joystick
hm2_5i25.0.8i20.0.1.fault.U-current-notto
hm2_8i20.ABCD.fault.U-current-not
Where in the first example the 8i20.0.1 refers to the 8i20 plugged into the second channel of sserial port 1, and in the second example it refers to the 8i20 with a serial number with the last 4 digits ABCD. (There is a very small danger of serial number collision.)
Hostmot2 7i64 driver Digital inputs change from
hm2_5i23.0.7i64.0.0.digin.00.in and hm2_5i23.0.7i64.0.0.digin.00.in-notto
hm2_5i23.0.7i64.0.0.input-00 and hm2_5i23.0.7i64.0.0.input-00-notDigital outputs change from
hm2_5i23.0.7i64.0.0.digout.00.out and hm2_5i23.0.7i64.0.0.digout.00.invertto
hm2_5i23.0.7i64.0.0.output-00 and hm2_5i23.0.7i64.0.0.output-00-invert
Hostmot2 8i20 driver
hm2_5i23.0.8i20.0.0.amp-enablepin deleted.
hm2_5i23.0.8i20.0.0.max_currentchanges to being controlled by two pins:
hm2_5i23.0.8i20.0.0.current.maxlim hm2_5i23.0.8i20.0.0.current.minlim
Fault/Status? registers are now individual pins.
hm2_5i25.0.8i20.0.1.fault.U-current / hm2_5i25.0.8i20.0.1.fault.U-current-not hm2_5i25.0.8i20.0.1.fault.V-current / hm2_5i25.0.8i20.0.1.fault.V-current-not hm2_5i25.0.8i20.0.1.fault.W-current / hm2_5i25.0.8i20.0.1.fault.W-current-not hm2_5i25.0.8i20.0.1.fault.bus-high / hm2_5i25.0.8i20.0.1.fault.bus-high-not hm2_5i25.0.8i20.0.1.fault.bus-overv / hm2_5i25.0.8i20.0.1.fault.bus-overv-not hm2_5i25.0.8i20.0.1.fault.bus-underv / hm2_5i25.0.8i20.0.1.fault.bus-underv-not hm2_5i25.0.8i20.0.1.fault.framingr / hm2_5i25.0.8i20.0.1.fault.framingr-not hm2_5i25.0.8i20.0.1.fault.module / hm2_5i25.0.8i20.0.1.fault.module-not hm2_5i25.0.8i20.0.1.fault.no-enable /hm2_5i25.0.8i20.0.1.fault.no-enable-not hm2_5i25.0.8i20.0.1.fault.overcurrent / hm2_5i25.0.8i20.0.1.fault.overcurrent-not hm2_5i25.0.8i20.0.1.fault.overrun / hm2_5i25.0.8i20.0.1.fault.overrun-not hm2_5i25.0.8i20.0.1.fault.overtemp / hm2_5i25.0.8i20.0.1.fault.overtemp-not hm2_5i25.0.8i20.0.1.fault.watchdog / hm2_5i25.0.8i20.0.1.fault.watchdog-not hm2_5i25.0.8i20.0.1.status.brake-old / hm2_5i25.0.8i20.0.1.status.brake-old-not hm2_5i25.0.8i20.0.1.status.brake-on / hm2_5i25.0.8i20.0.1.status.brake-on-not hm2_5i25.0.8i20.0.1.status.bus-underv / hm2_5i25.0.8i20.0.1.status.bus-underv-not hm2_5i25.0.8i20.0.1.status.current-lim / hm2_5i25.0.8i20.0.1.status.current-lim-no hm2_5i25.0.8i20.0.1.status.ext-reset / hm2_5i25.0.8i20.0.1.status.ext-reset-not hm2_5i25.0.8i20.0.1.status.no-enable / hm2_5i25.0.8i20.0.1.status.no-enable-not hm2_5i25.0.8i20.0.1.status.pid-on / hm2_5i25.0.8i20.0.1.status.pid-on-not hm2_5i25.0.8i20.0.1.status.sw-reset / hm2_5i25.0.8i20.0.1.status.sw-reset-not hm2_5i25.0.8i20.0.1.status.wd-reset / hm2_5i25.0.8i20.0.1.status.wd-reset-not
The under volt and no-enable pins appear as both status and fault, this is because different firmware versions treat the situations differently. Typically in RevB? boards both lack of enable and low bus voltage stop the card, whereas in the RevD? boards the only stop the output and the board recovers when the condition is removed. Either board version may run either firmware version, however.