Startup delayed when no FC/SITL present due to network auto-detection retries

[OmkarSarkar204]

Is there an existing issue for this?

• I have searched the existing issues

Description of the bug

I noticed a delay of approximately 2 seconds every time the application starts up when no flight controller is connected.

Steps To Reproduce

1. Disconnect all Flight Controllers.
2. Ensure no SITL or MAVLink simulators are running.
3. Run the application: python3 -m ardupilot_methodic_configurator
4. Observe the console output timestamps.

Expected behavior

The application should check the default network ports and, if the connection is refused (no available port to connect) it should move on immediately without retrying or sleeping This would make the startup feel instant.

Screenshots / Logs

Software information

• Operating system: Linux
• arduPilot Methodic Configuration version:
• Python Version: 3.10

Additional context

Is this delay intended behavior? If not, I have the fix to submit.

[amilcarlucas]

If there is a SITL running or an FC connected and the first connection attempt fails for some reason, then the user will wonder why it does not connect. So we do need to retry at least once to make sure. Hence the delay.

But do submit a PR, I'll take a look at it.

[OmkarSarkar204]

Thank You!
Makes sense. I’ve submitted PR #1201 with auto-detection retries reduced to 2, balancing a second check with faster startup.
Hope this works.