#Lost the will to live

1 messages · Page 1 of 1 (latest)

golden arrow
#

Don't you think you're exaggerating the situation by a huge margin?

What do you mean you got no answers?
You have asked for help last month (your only post) and Neil told you to do something.
#1297976091188920401 message
We have never heard from you about the results of this step. Why do you blame us if it is actually you who didn't report on the progress?
If you had reported then that it had not changed the situation, someone would have certainly contacted you and tried to help you further.

Also, If you take a look at the threads in various support channels, you will find many of them solved. This is because we always try to provide help to the extent of our knowledge and free time. Keep in mind this is an open source project, built and maintained by volunteers. We are not paid and yet we try as best as we can to help everyone who is building their own cockpit as we all are on the same boat. 🙂

Another thing, very important one.
Have you been in contact with CoreFlight?
We don't know that because you never mentioned it.
The supplier/manufacuter/seller of the hardware you bought should be the first place to seek the help. @kind lodge is in this server so he might be able to help you.

On the side note:
Sure, you can buy hardware that rely on manufacturers own software and isn't MF compatible. Ask yourself however what will happen if that company will ditch a software or what worse, will disappear from the market and at some point you will be left with hardware but no software to control it. Unfortunately we have seen such of cases in past.
This is where MF is helping. Sometimes ,compatibility is stright forward aka plug and play. Other times it might require some internal changes to make it compatible with any other software.

kind lodge
#

Hello there,
I see Gus is frustrated because of the connection problem...
I've been in touch from the start to today even though it is out of business hours.
And, the connection is established when I attempt to help via the remote desktop connection. Then, MF lost the connection again.

There is an unstable behaviour of the connection there.

For Gus, I'll attach the log here. May we find the issue?

cursive stream
#

How about making sure usb sockets are no going into a power saving mode? Are the com ports listed stable and not changing at all for any connection and no conflicts. Are there too many connections and a mains powered usb hub would be better. Are the panels own power supplies stable? Difficult to know without a few bits of equipment to test power supplies.

#

Drop the baud rate down via device manager, are the cable long and near mains supplies?

kind lodge
#

The devices are working nicely after connection is established.
However, sometimes the devices listed as "compatible" instead of the device/module name

#

For example, all was fine for the last 4 days. And he told me that there was no connection today.

cursive stream
#

going to get into the dodgy area here of programming something that shouldn't have it's firmware changed.

kind lodge
#

It's hard to know that without the help from Gus...

cursive stream
#

yep

#

he'll need to know exactly what the interfces are

kind lodge
#

The easiest way of eliminating most of the questions is connecting the modules to different PC. Is this possible somehow? @nova rock

golden arrow
#

Yeah, with extra information we can't help.
Basically what @cursive stream said, need more info how it is connected.

golden arrow
#

Maybe @inner field could read something from this log?

inner field
#

I don't know anything about the coreflighttech products, but there are two Arduinos getting detected and they are not reporting mobilfight info when queried:

11/19/2024 06:51:20(902): MobiFlightModule.GetInfo(): Retrieved board: Arduino Mega 2560, Arduino Mega 2560, /, .
11/19/2024 06:51:20(902): MobiFlightModule.GetInfo(): Retrieved board: Arduino Mega 2560, Arduino Mega 2560, /, .
11/19/2024 06:51:20(903): MobiFlightModule.Disconnect(): Disconnected Arduino Mega 2560:COM3.
11/19/2024 06:51:20(903): MobiFlightModule.Disconnect(): Disconnected Arduino Mega 2560:COM8.

If they were responding properly to Mobiflight there would be a serial number and version in there and there isn't. Not sure why, but it sounds vaguely related to what @proven pivot just opened a pull request for: https://github.com/MobiFlight/MobiFlight-FirmwareSource/pull/344

proven pivot
#

Could be indeed related, from the log:
'11/19/2024 06:51:16(720): ExecutionManager.mobiFlightCache_OnButtonPressed(): Generic USB Joystick => Button 11 => PRESS => No config found.
11/19/2024 06:51:20(902): MobiFlightModule.GetInfo(): Retrieved board: Arduino Mega 2560, Arduino Mega 2560, /, .
11/19/2024 06:51:20(902): MobiFlightModule.GetInfo(): Retrieved board: Arduino Mega 2560, Arduino Mega 2560, /, .
11/19/2024 06:51:20(903): MobiFlightModule.Disconnect(): Disconnected Arduino Mega 2560:COM3.
11/19/2024 06:51:20(903): MobiFlightModule.Disconnect(): Disconnected Arduino Mega 2560:COM8.`
A button press detected from a Joystick before the config gets read. But I am not 100% sure.

#

@nova rock are you still here and willing to do some tests? Like disconnecting the joystick and testing if this improves the situation?
I guess you know which COM ports the modules are using. If so I would send you a link to do some more tests.

proven pivot
proven pivot
pallid talon
#

Similar programs like SimHub that scan the COM Devices, can handle arduinos and connect/poll them constantly, will disturb MobiFlight. It's 100% reproducable on my side.

It's like, when MobiFlight starts, and the timing is ok, the device gets detected and stays that way. When timing with some other tool fails and the device is maybe used or polled already, MobiFlight detects compatbile.

Stopping other programs and starting MobiFlight gets the devices instantly recognized and never fails on that with restarts, unless "other programs" are started again.

proven pivot
#

Yes, good hint. Cura is another problematic program...

inner field
#

yes absolutely. Cura is a big offender. So is, oddly, my UPS software

golden arrow
#

I've been in contact with Yasar and he informed that this gentlemen unfortunately do not want to communicate anymore, despite Yasar attempts.

I will close this thread and mark as solved even though it isn't. Unfortunately we have no other way to investigate this issue.

potent canyonBOT
#

Since this is resolved I'm locking the thread. For additional questions or similar issues please start a new thread in #1028767888242376794. Happy flying!