With a machine I'm working with i get a communication error when I'm updating some softstop limits. As soon as I update the code the drives do not want to operate. Using the MC_readStatus I'm receiving errors as soon as i want to start a movement. Using MC_ReadAxisError i see that i receive error 131, no response. With a SMC3_ETC_ReadParameter_CoE i do not recieve any driver errors.
Does anyone know how i can figure out what the error is and how to solve it. When i go back to the old software no errors occur.
Im working with a legacy machine running a Beijer PLC with some Mitsubishi drives. running on Codesys 3.5 SP10. the runtime version is probably 3.5.3. The drives are all Ethercat Drives (CoE). All using the SM3_drive_ETC libary and the SM3_basic library.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With a machine I'm working with i get a communication error when I'm updating some softstop limits. As soon as I update the code the drives do not want to operate. Using the MC_readStatus I'm receiving errors as soon as i want to start a movement. Using MC_ReadAxisError i see that i receive error 131, no response. With a SMC3_ETC_ReadParameter_CoE i do not recieve any driver errors.
Does anyone know how i can figure out what the error is and how to solve it. When i go back to the old software no errors occur.
Im working with a legacy machine running a Beijer PLC with some Mitsubishi drives. running on Codesys 3.5 SP10. the runtime version is probably 3.5.3. The drives are all Ethercat Drives (CoE). All using the SM3_drive_ETC libary and the SM3_basic library.