V0N_hydro
Member
I'm trying to get a schneider m340 plc to talk to a woodward easygen 3100 enginer controller over canbus. The 3100 is just a unit to test with, final product will have two easygen 3400 and five LS-5 breaker controllers all talking on canbus.
I've loaded the easygen 3100 EDS file in to the unity hardware catalog manager, added the 3100 to the canopen bus in unity, assigned the same node ID in the easygen as in unity, and have the two connected with a straight-through serial cable (both devices have DB9 male connectors for canbus.) no termination resistors ... I suppose this could be the problem?
the M340 is the canbus master, the easygen and all other devices will be slaves.
I can't get the easygen to leave the pre-operational state. I can send the NMT commands to stop it and the status for the slave ID goes to stopped in M340 canbus master. the m340 is configured to start the node in the bootup procedure configuration for the slave. When I send the NMT command to start the node it goes to preoperational but never leaves pre-operational.
The number of transmitted and received frames shown in the M340 PLC climbs at a steady rate and they are nearly equal, leading me to believe that the straight-through serial cable without resistors is working fine as a communications channel.
I have also tried to configure a TPDO in the easygen 3100 using the toolkit software and configured the same TPDO in the m340 in unity, but since the easygen never leaves preoperational state the PDOs don't come in to play.
Using the CANopen tab on the easygen device in unity allows read a SDO to be sent, this returns an "illegal server failure" status.
any thoughts?
I've loaded the easygen 3100 EDS file in to the unity hardware catalog manager, added the 3100 to the canopen bus in unity, assigned the same node ID in the easygen as in unity, and have the two connected with a straight-through serial cable (both devices have DB9 male connectors for canbus.) no termination resistors ... I suppose this could be the problem?
the M340 is the canbus master, the easygen and all other devices will be slaves.
I can't get the easygen to leave the pre-operational state. I can send the NMT commands to stop it and the status for the slave ID goes to stopped in M340 canbus master. the m340 is configured to start the node in the bootup procedure configuration for the slave. When I send the NMT command to start the node it goes to preoperational but never leaves pre-operational.
The number of transmitted and received frames shown in the M340 PLC climbs at a steady rate and they are nearly equal, leading me to believe that the straight-through serial cable without resistors is working fine as a communications channel.
I have also tried to configure a TPDO in the easygen 3100 using the toolkit software and configured the same TPDO in the m340 in unity, but since the easygen never leaves preoperational state the PDOs don't come in to play.
Using the CANopen tab on the easygen device in unity allows read a SDO to be sent, this returns an "illegal server failure" status.
any thoughts?