Giving MDC1460 controllers unique address'
- viron11111
- Topic Author
- Offline
Less
More
- Posts: 3
- Thank you received: 0
7 years 7 months ago #29531673
by viron11111
Giving MDC1460 controllers unique address' was created by viron11111
I have a robot with 4 MDC1460's on board. We're using the USB connections. I noticed this topic: dev.roboteq.com/dev1/index.php/forum/14-...-roboteq-controllers
However, ^cad and ~cad does not work with my devices and I couldn't find an equivalent command in the manual. Is there another way to give each controller a different address?
Thanks.
However, ^cad and ~cad does not work with my devices and I couldn't find an equivalent command in the manual. Is there another way to give each controller a different address?
Thanks.
Please Log in or Create an account to join the conversation.
7 years 7 months ago #29531674
by niko
Replied by niko on topic Giving MDC1460 controllers unique address'
Hello,
The mentioned topic was 4 years ago. So, now you can use CNOD instead of CAN.
The mentioned topic was 4 years ago. So, now you can use CNOD instead of CAN.
Please Log in or Create an account to join the conversation.
- viron11111
- Topic Author
- Offline
Less
More
- Posts: 3
- Thank you received: 0
7 years 7 months ago #29531676
by viron11111
Replied by viron11111 on topic Giving MDC1460 controllers unique address'
Thanks for the response.
I changed the NodeID with ^CNOD and confirmed the change with ~CNOD. However, the USB device ID for all of the devices is still: usb-Roboteq_Motor_Controller_MDC14XX-if00.
We're using a ROS launch file that accesses the serial port via by-id. With FTDI serial devices, each device has a unique ID that we reference with udev rules.
Is there some way that I can change the ID or uniquely identify the motorcontroller, through the serial port, besides the by-path method (which changes when we plug them into different ports)?
I changed the NodeID with ^CNOD and confirmed the change with ~CNOD. However, the USB device ID for all of the devices is still: usb-Roboteq_Motor_Controller_MDC14XX-if00.
We're using a ROS launch file that accesses the serial port via by-id. With FTDI serial devices, each device has a unique ID that we reference with udev rules.
Is there some way that I can change the ID or uniquely identify the motorcontroller, through the serial port, besides the by-path method (which changes when we plug them into different ports)?
Please Log in or Create an account to join the conversation.
7 years 7 months ago #29531678
by niko
Replied by niko on topic Giving MDC1460 controllers unique address'
Hello,
the USB id cannot change. The idea is that when you connect to a device, in order to know which device it is you type~CNOD and get the node id you have configured.
the USB id cannot change. The idea is that when you connect to a device, in order to know which device it is you type~CNOD and get the node id you have configured.
The following user(s) said Thank You: viron11111
Please Log in or Create an account to join the conversation.
- viron11111
- Topic Author
- Offline
Less
More
- Posts: 3
- Thank you received: 0
7 years 7 months ago #29531683
by viron11111
Replied by viron11111 on topic Giving MDC1460 controllers unique address'
Thanks.
Please Log in or Create an account to join the conversation.
7 years 7 months ago #29531716
by korence
Replied by korence on topic Giving MDC1460 controllers unique address'
Helpful post, thanks.
Please Log in or Create an account to join the conversation.
Moderators: tonysantoni
Time to create page: 0.068 seconds