Hello, sorry for the slow response
Yes the set digital IO on the driver currently does nothing, I would display a message in the log to tell users as such but that would cause the robodk api to break when communicating with the driver.
As you noted, the IO ports don't match across all the robots and to further add complication, if my understanding is correct these IO ports also need to be connected to real IO's in the ladder programmer for setting and reading these IO values to provide anything useful.
Generally we try and make the drivers and post processor behave as interchangeably as possible. I'm open to suggestions on how best to implement this but from my understanding I just use the value the user sets in robodk directly in the function that the motoman HSE manual calls "I/O Data Reading / Writing Command"
目前我没有访问权限to a motoman robot and controller to test significant changes to the driver like adding the underlying function for setting and reading a digital output and dynamically changing a tools center point (TCP) but when I do the version number of the driver will read 6.x.x
Phillip
Yes the set digital IO on the driver currently does nothing, I would display a message in the log to tell users as such but that would cause the robodk api to break when communicating with the driver.
As you noted, the IO ports don't match across all the robots and to further add complication, if my understanding is correct these IO ports also need to be connected to real IO's in the ladder programmer for setting and reading these IO values to provide anything useful.
Generally we try and make the drivers and post processor behave as interchangeably as possible. I'm open to suggestions on how best to implement this but from my understanding I just use the value the user sets in robodk directly in the function that the motoman HSE manual calls "I/O Data Reading / Writing Command"
目前我没有访问权限to a motoman robot and controller to test significant changes to the driver like adding the underlying function for setting and reading a digital output and dynamically changing a tools center point (TCP) but when I do the version number of the driver will read 6.x.x
Phillip