Hello All! I'm embarking on a new project and have been searching the forums to assist in what is looking to be a rather challenging task.
We are using an TM258LF42DT which has a Sub-DB9 CAN port. The end device is an automotive sensor that supports J1939. The sensor has a heating element which must be turned on/off based on other process conditions. Once the sensor heater is on, the sensor will start providing data.
The task is to establish bi-directional communication with the sensor; we need to be able to send the sensor a command string (to turn-on the heating element), read the data provided in real-time, and when the process is finished send the same command string (to turn-off the heating element).
Looking at the Schneider documentation, it appears the M258 only supports CANopen; a M241 or M251 required for native J1939 support. I've assembled and read through a fair bit of documentation at this point; I've covered the port itself (Hardware Guide), CANopen Configuration (Programming Guide), and SoMachine Templates (Programming Guide). I've also been researching elsewhere to learn about .EDS files, as well as the differences between CANopen / J1939.
I will readily admit I am out of my depth here. At this point I'm hoping to ascertain whether it is even possible to create a custom device template to communicate with the J1939 sensor using the CANopen port, or if I will need a gateway/translator as a go-between? From my other research, it appears that while they share the same physical layer, the two methods use different approaches for the higher level communication layer.
Thanks!
We are using an TM258LF42DT which has a Sub-DB9 CAN port. The end device is an automotive sensor that supports J1939. The sensor has a heating element which must be turned on/off based on other process conditions. Once the sensor heater is on, the sensor will start providing data.
The task is to establish bi-directional communication with the sensor; we need to be able to send the sensor a command string (to turn-on the heating element), read the data provided in real-time, and when the process is finished send the same command string (to turn-off the heating element).
Looking at the Schneider documentation, it appears the M258 only supports CANopen; a M241 or M251 required for native J1939 support. I've assembled and read through a fair bit of documentation at this point; I've covered the port itself (Hardware Guide), CANopen Configuration (Programming Guide), and SoMachine Templates (Programming Guide). I've also been researching elsewhere to learn about .EDS files, as well as the differences between CANopen / J1939.
I will readily admit I am out of my depth here. At this point I'm hoping to ascertain whether it is even possible to create a custom device template to communicate with the J1939 sensor using the CANopen port, or if I will need a gateway/translator as a go-between? From my other research, it appears that while they share the same physical layer, the two methods use different approaches for the higher level communication layer.
Thanks!
Last edited: