Open ottensmeyer opened 3 years ago
Update - tried with an XC430-W150-T - has the same indirect address/data addresses as the XM and works without problems. No idea why the XL doesn't seem to work as expected.
Hi @ottensmeyer Thank you for your inquiry and sorry about your incovenience. In the current XL330 firmware, there's a bug that some indirect address and data are not properly linked. The next firmware update includes the fix for this bug.
Thanks Will - glad it wasn't me doing something dumb. Do you have an ETA on the next update? Would I need to update the Wizard to obtain the firmware update, or will the Wizard recognize the presence of an update for the 330 automagically?
Cheers Mark
Hi @ottensmeyer Thank you for your understanding. Once the Wizard 2.0 software is updated, you'll get a notification. The firmware update should be done manually as there are many customers who want to keep using a specific firmware version for their product. Wizard 2.0 supports multiple module firmware update and you don't need to remove any connection from the system for a simple firmware update. https://emanual.robotis.com/docs/en/software/dynamixel/dynamixel_wizard2/#firmware-update-all
The next update is scheduled in this month, but in case you urgently need to test the feature, please try the temporary firmware below. Please note that this firmware fixes the indirect address & data bug and provided as is which does not guarantee its integrity. https://drive.google.com/file/d/1a3gQKBToUtmg_l8UejzMILWscYeQwp7s/view?usp=sharing Download will be available for the next 7 days. Thank you!
Hi Will - just installed the temporary fix - looks like it's working fine - thanks very much for the early access - will keep my eyes out for the full update!
best, Mark
On Mon, May 31, 2021 at 8:22 PM Will Son @.***> wrote:
Hi @ottensmeyer https://github.com/ottensmeyer Thank you for your understanding. Once the Wizard 2.0 software is updated, you'll get a notification. The firmware update should be done manually as there are many customers who want to keep using a specific firmware version for their product. Wizard 2.0 supports multiple module firmware update and you don't need to remove any connection from the system for a simple firmware update.
https://emanual.robotis.com/docs/en/software/dynamixel/dynamixel_wizard2/#firmware-update-all
The next update is scheduled in this month, but in case you urgently need to test the feature, please try the temporary firmware below. Please note that this firmware fixes the indirect address & data bug and provided as is which does not guarantee its integrity.
https://drive.google.com/file/d/1a3gQKBToUtmg_l8UejzMILWscYeQwp7s/view?usp=sharing Download will be available for the next 7 days. Thank you!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ROBOTIS-GIT/DynamixelSDK/issues/502#issuecomment-851726859, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADEPGIF2QZGD4AZTLOXT5MTTQQR4FANCNFSM45XD7TGQ .
ISSUE TEMPLATE ver. 1.2.0
Please fill this template for more accurate and prompt support.
Which DYNAMIXEL SDK version do you use?
Which programming language/tool do you use?
Which operating system do you use?
Which USB serial converter do you use?
Which DYNAMIXEL do you use?
Have you searched the issue from the closed issue threads?
Please describe the issue in detail
I am trying to use the indirect addressing example with the XM540 and XL330 servos (Protocol 2.0). With the XM540, I change the address values in the #defines, change the position start/end locations to reasonable values (0, 1023), update the LED values (from 255 to 1), and I correctly read the position and moving state values
When I do the same for the XL330, the position values are correctly read out, but the moving state never changes from 0. I've replaced the moving state address (122) to other 1-byte addresses (e.g. temperature (146), LED state (65)), which also only read 0.
Writing using indirect address works fine - the goal_position and LED commands are accomplished successfully
Am I doing something wrong in using indirect addressing? The example is for the Dynamixel PRO 54-200, and USB2DYNAMIXEL, and the example works correctly for the XM540 and OpenCR, but not the XL330
I've confirmed using the DYNAMIXEL Wizard 2.0 that the moving, temperature and other states are reading correctly from the XL330, which has address values for each of these the same as what's on the eManual (the Wizard also shows that the XL330 is not in need of an update)
Typical output using XM540 - PresPos is correctly reported, and IsMoving output shows the correct temperature (about 28) using the code below: