• State Answer Suggested
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 134 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BP-AM2BLDCSERVO: CRC Failure in Tamagawa Diagnostic with LP-AM243 + BP-AM2BLDCSERVO

Shinsuke SHIRAHAMA
Prodigy 10 points
Part Number: BP-AM2BLDCSERVO
Other Parts Discussed in Thread: LP-AM243, MCU-PLUS-SDK-AM243X

Tool/software:

I'm trying to run Tamagawa Diagnostic using the combination of LP-AM243, BP-AM2BLDCSERVO, and a Tamagawa encoder, as described on this web page.

However, all the commands shown in the console result in a "CRC Failure" message, and it doesn't seem to be working correctly.

For example, when I send the command “0 : Data readout, Absolute (Data ID 0)”, the signals on DATA+ and DATA– are output as shown in the waveform shown below.

Looking at the diagram in “Hardware Setup of Booster Pack + LP for Tamagawa” it appears that the system operates using a 2-wire RS-485 connection for DATA+ and DATA–. In that case, shouldn't J24 be set to ON instead of OFF?

I'm using the following SDK versions:

  • MCU-PLUS-SDK-AM243X: 11.00.00.15
  • MOTOR-CONTROL-SDK-AM243X: 09.02.00.09

If there are any specific settings or configurations I should check to ensure proper operation, I would appreciate your guidance.

Best regards, 

Shinsuke

  • 0
    TI__Mastermind 27774 points

    Hi

    Difference between 2-wire and 4-wire is availability of clock signal in differential form.  Keeping J24 ON maybe correct configuration if we do not need clock signal. We will review this and respond back.

    Are you seeing any problem in getting a response from the encoder?

    Regards

    Dhaval

  • 0 in reply to Dhaval Khandla
    Prodigy 10 points

    Hi all,
    Thank you for your support.
    It turned out that the encoder we were using had a non-standard specification, which was the reason communication was not working as expected. 
    After switching to a standard-compliant encoder, we confirmed that the sample code works correctly and that commands are being sent and received properly.
     
    Apologies for the confusion, and thank you again for your assistance.
     
    Best regards, 
     
    S.SHIRAHAMA