gerdam Posted August 8, 2019 Report Posted August 8, 2019 Hi guys, its been a whle since ive been here,please could you help.i have aquantum 133 controller that was switched off, and lo and behold when switched back on the low battery light came on and the program has been lost.im useing proworx to try and go on line with the controller but keeps timing out(364) ,i am able to connect to other quantums with no problem.the cpu is ready with no faults. please help. Quote
collinsd70 Posted August 12, 2019 Report Posted August 12, 2019 Hi gerdam. Welcome to the forum, what is your communication method? Could it be that the path you are trying to use has been reset to default addresses and settings due to the low battery fault? Try connecting directly using the Modbus or Modbus Plus port.... Regards Daniel Quote
gerdam Posted August 12, 2019 Author Report Posted August 12, 2019 Thanks for the reply Daniel,i deed try connecting via Modbus and Modbus plus ports,whats strange is that after being powered down over the weekend i managed to write the program on my first try today, what changed?? . Quote
Modiconbob Posted August 19, 2019 Report Posted August 19, 2019 Once the processor has lost its' memory, the comm addresses default back to 1 for MB & MB+. Once the program is reloaded and the processor is started to Run, the addresses will be set by the newly reloaded program. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.