#Arduino UNO clone crashing and limitation of Arduino MEGA.

1 messages · Page 1 of 1 (latest)

strong pumice
#

Hi guys! I know that documentation says UNO is experimental, but anyway I decided to ask to be sure. I ordered an Arduino MEGA today to test behaviour compared with UNO.

The problem with UNO is - crashing MobiFlight to desktop without any notification. I have only non-momentary switch connected to the Arduino and configured for RNWAY TURNOFF LIGHTS. 1 of maybe 40 times when I switch the button, the MobiFlight exiting. Only on switch situations. What can be a reason? It's only this that UNO is experimental or a problem is deeper?

And a second question - I know that documentation says that I can use 127 Arduinos on Windows, but I need use at least 5 or 6 to create my project. Is it possible that PC with PCI-E USB HUB can handle it or not?

Greetings for you all!

copper elk
#

Starting with the easy second question: 5-6 arduinos is no problem at all on Windows via a hub

#

For the first question, it shouldn't crash and wouldn't be because it is an Uno. Can you get the crash information for me? Run Event Viewer from the start menu then expand Windows Logs > Application. Look for red errors from MobiFlight, click on one, and paste the details here

#

There are probably two errors logged for each crash

#

And what version of MobiFlight are you running? It says in the title bar.

strong pumice
#

Thanks for so quick reply!

Using MFConnector.exe version 9.6.0

Yes I see this crash errors. The details are in my language. Let me change system language and I will paste it here.

copper elk
#

I can probably figure it out in your language too 😄

#

the function names and whatnot won't change which is what I need to see

strong pumice
#

It's okay! Now is in English!

Faulting application name: MFConnector.exe, version: 9.6.0.0, time stamp: 0x63624c70
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x1e5c8604
Exception code: 0xe0434352
Fault offset: 0x0012e292
Faulting process id: 0x1be34
Faulting application start time: 0x01d91f86bc8556fe
Faulting application path: E:!Pobrane\MFConnector.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 505119c2-f033-4d3c-8e7d-f7b7c4248f23
Faulting package full name:
Faulting package-relative application ID:

Aplikacja: MFConnector.exe
Wersja architektury: v4.0.30319
Opis: proces został przerwany z powodu nieobsłużonego wyjątku.
Informacje o wyjątku: System.FormatException
w System.Number.StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)
w System.Number.ParseInt32(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)
w MobiFlight.MobiFlightModule.OnButtonChange(CommandMessenger.ReceivedCommand)
w CommandMessenger.CmdMessenger.InvokeCallBack(MessengerCallbackFunction, CommandMessenger.ReceivedCommand)
w CommandMessenger.CmdMessenger.HandleMessage(CommandMessenger.ReceivedCommand)
w CommandMessenger.Queue.ReceiveCommandQueue.ProcessQueue()
w CommandMessenger.AsyncWorker.<Start>b__20_0()
w System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
w System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
w System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
w System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
w System.Threading.ThreadHelper.ThreadStart()

copper elk
#

yep, cool

#

The crash will be gone in the next release as I added code to handle this gracefully. Still doesn't change the fact that the Uno is sending garbage though. I believe Jaime had this problem too and it was due to interference from other devices.

strong pumice
#

I understand! More I can say that I have done a "stress" test for it and got a two cables and short-circuit them in a very short time and almost always the program exited.

So there's a chance that with MEGA the problem can be solved? Really don't need use the UNO cause of lack amount of pins, but I'm still afraid that problem can cause crashes with MEGA too.

copper elk
#

It's a pretty rare problem, I think only two other people have had it before. The crash will go away in the next release, instead what will happen is the button push will just seem like it got missed.

strong pumice
#

Amazing! So I'm lucky I see haha! I'll test it with MEGA and report whether the problem persists or not. So so much thanks for help. You guys doing a amazing job with MobiFlight!