Hi guys,
We encountered a problem with our attendance panel which is based on EMX module. 11 of 14 panels stopped working last week in one of our customer’s building. The runtime was about two months without any reported problems. So funny is, that all drop-outs was reported within 30 minutes. I have figured out following:
- The initial problem was System.IO.IOException when saving attendance event on SD card. In this case, we display error screen with error description and by tapping the screen we restart panel by calling:
Microsoft.SPOT.Hardware.PowerState.RebootDevice(true);
- After this restart, initialization of panel fails with NotSupportedException trying to perform first operation with SD card (which was successfully mounted). The stack trace is following:
#### Exception System.NotSupportedException - CLR_E_NOT_SUPPORTED (1) ####
#### Message:
#### Microsoft.SPOT.IO.NativeIO::CreateDirectory [IP: 0000] ####
#### System.IO.Directory::CreateDirectory [IP: 000a] ####
#### Fides.MicroCommon.utils.SDCard::CreateDir [IP: 000c] ####
#### Fides.MicroCommon.Logger.TextFileLogger::init [IP: 001c] ####
#### Fides.MicroCommon.Logger.TextFileLogger::.ctor [IP: 000d] ####
#### fides.asset.AttendancePanel.MainThread::init [IP: 0049] ####
#### fides.asset.AttendancePanel.MainThread::Run [IP: 0004] ####
#### fides.asset.AttendancePanel.Program::Main [IP: 0008] ####
A first chance exception of type 'System.NotSupportedException' occurred in Microsoft.SPOT.IO.dll
after this exception, we display same error screen again, user restarts panel by tapping the screen and then everything repeats.
- To get rid of this state, panel must be disconnected from power supply, restart button must be held for more than 3 seconds or RebootDevice must be called with false “soft” parameter:
Microsoft.SPOT.Hardware.PowerState.RebootDevice(false);
After one of these operation, our panels are up again with runtime more than one week.
Has anyone experienced something similar to this? What does NotSupportedException means when you call Directiory.Exists? Any ideas how can I prevent this situation? Why only hard reset works?
We start to think that it is something with ethernet. Our board design comes out form your dev kit board so pin 3.3V_3 (37) is connected directly with ethernet plug. Should’t be there any choking coil to prevent some voltage spikes?
Thanks for any help
Martin