Error when downloading a program in a Freelance, model PM783F
We made a modification in the program. During the time we download the program in the CPU, the system stopped to work when the download sequence was at 50% completed. At this time, the error led on the CPU was active, and we were not able to ping the processor. So we asked to the operator to remove the power on the CPU and put it back. When the supply came back on the CPU, we observed that the download was completed. My question is how could we prevent that, becauce we can't stop the processor cause by a download error.
Voted best answer
This may happen when controller memory already occupied and via download user trying to fit code more than available memory space. this may happen if user perform incremental download of larger chunk of code or download code more than available space.
Remedy to this by default configuration data (PRAM) is 900KB and max of objects are 3000 this information can be found in AC700F parameterization in HW structure. by changing this data (increase PRAM by 200KB and object by 500). Should allow or fit more code inside controller. Note that any changes in boot parameter needs controller stop to download these changes, so careful if it's a running plant situation. And advised this changes to be managed by expert, I suggest read AC700F engineering manual search boot parameter or HW configuration AC 700F or get help of local ABB support line for this. Hope that helps.
thanks for providing the error information. It indicates an unexpected condition in the CPU.
You should report this issue to the ABB support organization. Maybe they can provide a solution for it.
You should report every unexpected stop of the CPU to the ABB support organization.
After a second verification of the CPU log, I saw that the error occured 2 times. I think that the first one was when we start the CPU for the first time, because the date and time is not correct. We also didn't notice anything when it is produced. It was in May 2015.
The second time, the CPU was running process when he freezed.