Menu

Topic-icon HBL 2396 R53 CAN issue

More
8 months 3 days ago #29534475 by atestasecca
Hi

I have an issue with a SDO CAN communication script.
The program has been tested with a SBL 2360 controller and it was working.
Now I would like to use this program on a HBL 2396 but I can't read the answers on CANBUS.

Here is the start of my program
Codid_Right = 0x600 + 2

' check the status of the  right (read statusword at 0x6041 subindex 0x00)
setcommand(_CS,1,Codid_Right)
setcommand(_CS,3,0x40)
setcommand(_CS,4,0x41)
setcommand(_CS,5,0x60)
setcommand(_CS,6,0x00)
setcommand(_CS,2,4)
wait(10)
frame = getvalue(_CF) ' check if a frame has been received

If frame > 0 Then
     data_low = getvalue(_CAN,7)

but frame stay always at 0.

Do you know if the "CAN FRAME" operation (?CF) is working on a HBL 2396 R53 with the USB plugged?
If not how can we read the CAN answer?

Thank you for your time

If not

Please Log in or Create an account to join the conversation.

More
8 months 2 days ago #29534480 by Gabriel_Isko
Replied by Gabriel_Isko on topic HBL 2396 R53 CAN issue
Can you send ~UID in the console tab of roborun+ and let me know what the result is?

Please Log in or Create an account to join the conversation.

More
8 months 2 days ago #29534483 by atestasecca
Replied by atestasecca on topic HBL 2396 R53 CAN issue
Hello Gabriel,

See in the attachment picture the UID feedback.

And my problem is solved it was a wrong setup, the controller was only listening the node 4 so no possibilities to communicate to the node 2.

Thank you for your time
Attachments:

Please Log in or Create an account to join the conversation.

More
8 months 16 hours ago #29534484 by Gabriel_Isko
Replied by Gabriel_Isko on topic HBL 2396 R53 CAN issue
Okay, I'm glad you solved the problem.

I just realized too, that you could also use our CANOpen implementation, rather than constructing the Raw frame yourself. It would be a lot simpler.

Please Log in or Create an account to join the conversation.

Moderators: tonysantoni
Time to create page: 0.272 seconds
Go to top