CHIRP

Thanks for the report.

This error is raising because the driver does not wait enough for the answer, this is the most time consuming task: to smooth this little details, this change with different OS and even with USB drivers. With a radio at hand to test this subtask is hidden from the user, but in this case we need to work this out.

Please use the main thread for this radio, do not open different issues. Use this thread: #4933

I will put a corrected driver with a more generous timeout for you to test in the main thread.

Thanks.

73 Pavel CO7WT.

No problem.

This issue is now closed.