0
Under review

Blue screen on MD4-7 while operating

fdube 10 months ago in IQANdesign updated by Gustav Widén (System support) 9 months ago 10

Hi,

I was wondering if anyone had blue screens happening while in operation?

I currently have an intermittent blue screen problem on an Md4-7 running Iqan 6.06. Images of one event are attached. The busload on the can-buses are low with no error frames.

What is the processor utilization of the application?  It looks like there was a watchdog reset in the first 4 pictures.  The last picture, I am not sure what happened there.

This MD4-7 unit runs with a cycle time of 10ms and the cycle utilization remains within 52% +/- 3%. We were able to reproduce this error while logging the cycle utilization on CAN and there was no change prior to event. 

Should we look somewhere else? As for the last image, is there a way to go and fetch the latest logs? Since these blue screens happen randomly, expecting the user to pull out his cell phone and grab a photo fast enough seems pretty unlikely that we collect the correct image.

The last picture looks like the MD4 is scrolled up to show a historic error from July 16th 15:29 (year not included, but version was 5.04 at the time). That old one looks like it was too much outgoing CAN traffic on CAN-C. 

The timestamp on the two more recent watchdog resets indicate both occurred during startup. 

Our average bus loads for CAN-A, B, C and D are respectively 13.5%, 9.7%, 24.5%, 2.5%. We were able to reproduce this event while logging all CAN buses and we did not notice a change in bus load prior to the event.  

Hi Gustav,

Any possible avenues to resolve this problem? My colleague answered your questions.

Let us know if you need additional information.

Thanks

Under review

Thank you. At a 10 ms cycle, MD4 cycle utilization at 55% is quite high, but if this is the peak value it does not explain the error. A relevant test could be to modify the application to include a MEM channel that record the peak utilization. If it peaks at startup, it would be impossible to catch with an IQANrun graph. 


On MD4, it is is possible It is possible to get the full history of crash reports by getting a clone with debug info. The IQANscript get clone action has a property for retrieving this, but to extract the information the clone with debug info would have to be sent to us at Parker and manually decoded here. 

An MD4 clone with this information could be quite large, it is good to be at the machine so you can extract it via local Ethernet connection. 


I also recommend you to reach out to your local Parker rep on how to get the information across.

Further troubleshooting will involve looking specifically at the application, so it is best to take it through the conventional support channels. 


Hi Gustav, thanks for the reply. Do we need to purchase an IQANscript license to retrieve those debug logs? The IQANsimulate trial version says we can only connect to a simulator. It seems I can only retrieve "logs" with IQANrun and not "debug logs".

The script needs to be created with a licensed copy of IQANscript. If you do not have IQANscript, the local Parker rep can provide a script file for you. I believe someone from the team has already reached out to you by now.