Questions
0
MD3 blue screen_LOG HANDLER
Hello,
just got that message on a MD3 screen, any idea the root cause ?
Br
/Adrien
Customer support service by UserEcho
Share
Topic stats
- 0 Votes
- 5 Replies
- 2 Followers
- 1,377 Views
Hello,
just got that message on a MD3 screen, any idea the root cause ?
Br
/Adrien
Customer support service by UserEcho
sounds the system logs and alarm logs are full and locked up the module.
Hello Andrien.
The logs being full should not cause this.
When the logs are full the MD3 will either stop logging or start to replace the oldest log entries, depending on what is set in the application.
Do you know what version of firmware is loaded in the unit?
Does this always happen or only sometimes?
Hello Thomas,
ah ok!
it's 2.63.1
it have been happening at least twice in the past and after reloading the Clone it was working again for few months or a year (we was not dealer for that brand in the past so I do not have the all historic)
I had real troubles to get connection with the display after loading the .ida original program from OEM, can’t communicate with the display after I shut it down.
to connect I am obliged to press the back arrow to get in SAFE MODE, then I send a BLANK program before I load ida file.
After that I get stuck again with RUN 2 communication (Using CAN through KVASER)
At the moment the customer went back to the machine with a new display and the original ida program (but no customer’s settings file because I could not connect any longer)
I have:
Two options I was thinking:
Did you test the other CAN buses on the module.
If the application you downloaded had a generic bus located on the bus you where connected to you would not be able to communicate with it anymore after the download.
And logs do not get downloaded when you download a clone file.
The clone does have the logs in them but they are the only part that does not get downloaded with a clone.
it have been woking to swap from Bus C to Bus A, now I can connect anytime and reprogram as needed
thanks