I have a J1939 network (ISOBUS) connected to my PLC. I can receive various PGNs such as 65256 (Vehicle Direction/Speed) and 65254 (Time/Date). However, I cannot receive 65267 (Vehicle Position). PGN 65267 (VP) contains SPN 584 (Latitude) and SPN 585 (Longitude). On the network both SPNs return a value of -210 (meaning the CAN message payload is zero in both cases). The conversion settings are the default values and appear to be correct (see attached screenshot). Using a CAN analyser I can see that...
The Codesys online help makes it clear that the RTR option is only available for transmit PDOs (see attached screenshot "RTR.png"). https://content.helpme-codesys.com/en/CODESYS%20CANbus/_can_edt_canopen_device_pdos.html Given that this is the intended behaviour I need to find a work around. The device that I'm working with is an Axiomatic AX021101 CANOpen valve controller. Here is a link to the user manual. https://products.axiomatic.com/Asset/UMAX021101.pdf Section 3.1.14 (p. 54) makes it clear...
The Codesys online help makes it clear that the RTR option is only available for transmit PDOs (see attached screenshot "RTR.png"). https://content.helpme-codesys.com/en/CODESYS%20CANbus/_can_edt_canopen_device_pdos.html Given that this is the intended behaviour I need to find a work around. The device that I'm working with is an Axiomatic AX021101 CANOpen valve controller. Here is a link to the user manual. https://products.axiomatic.com/Asset/UMAX021101.pdf Section 3.1.14 (p. 54) makes it clear...
For clarity, I've attached screenshots of the RPDO and TPDO configuration dialog boxes.
I have a CANOpen device that does not allow the RTR option on PDOs (both receive and trasmit). When configuring this device in Codesys I can edit the TRANSMIT PDO and untick the RTR option, but there is no tick box for the RECEIVE PDO. As a result, errors are raised during initialization (abort code 16#06090030) and the RPDO does not function. I then have to manually override the COB-ID used by RPDO to get it working. Is there a reason why the RPDO editor is missing the RTR tick box? Can anything...
Oops! I was looking at the wrong example project. It makes sense now. Thanks for your help.
I've had a look at the example code you pointed me to. Unfortunately, I can't see any examples of a write function that does not use SDO messages. Can you be more specific about which function block might work?
Thank you for your reply and sorry for my delayed response. I was not able to test your suggestion until now. I've created a program using the SDO_WRITE4 function block and I can now write SDOs. For example, I can change the baud rate of a CANOpen device. However, I don't understand how to use SDO_WRITE4 to write LSS messages. This function block takes in the destination node-id on the DEVICE input. However, LSS messages use special reserved COB-IDs without node-ids. Is there a way to get around...