-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SITL Ser2TCP issue #1817
Comments
We should really replace these binary programs (in particular the Linux monstrosity) with code we own / control. Note the C-lang instances are what is shipped with the so called "Next "configurators. You may find working "drop in" replaceable binaries in the archives here |
Thank you for the answer
tried to reboot, to use sudo... the same |
The same issue with golang AND c version compiled on my PC |
version of SITL?
which then works:
as does:
Linux distro & version? |
You have configured |
Yes, you can see it on my screen |
I can't see it, you didn't show the Ports tab. |
The SITL reads the used ports from the saved eeprom; if you haven't set up the port as a serialTX, the SITL cannot see it and it doesn't matter what you do on the SITL tab. |
And you must also have set up the rx type in the Receiver tab. Seems like there is no software issue here, rather incomplete configuration. |
Yohoo!!!
Don't see any stick actions, but I'll double check all the configurations and tell you later |
Ready to continue ) Trying with InavConfigurator 6.1
Receiver TAB - Serial + CRSF PS: still can connect on /dev/ttyUSB0 and see data (I thought that ttyUSB0 should be locked after the bridge connection) |
Works perfectly here (CRSF). It is probable that your USB-TTL adaptor cannot handle "non-standard" baud rates.
So again, SITL and ser2tcp work perfectly if you've (a) configured everything correctly and (b) you use adequate hardware. Maybe I'll add a warning to |
The only way is to test it, I'm going to update the 'C' ser2tcp to provide a warning. I'll let you know when it's done. |
Thanks!
…On Thu, Aug 10, 2023 at 1:53 PM Jonathan Hudson ***@***.***> wrote:
The only way is to test it, I'm going to update the 'C' ser2tcp to provide
a warning. I'll let you know when it's done.
—
Reply to this email directly, view it on GitHub
<#1817 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA72A26OMGRMTVDXPL7WEI3XUS4T3ANCNFSM6AAAAAA3J4Z4XY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
You can ungzip / rename and try the following. It will report any difference in desired baudrate and device actual rate. This seems only to be a Linux issue; on FreeBSD, MacOS and Windows the driver reports the speed as requested.
This small difference is OK, the converter works just fine with configurator / SITL. The other device that sets itself to 460800 does not work with the SITL / Configurator. |
I'm trying to use serial2tcb bridge to connect my ELRS receiver by usr2ttl adapter to SITL
Ubuntu 23.04
I have an error
If I'm trying to run this command manually - error the same
./Ser2TCP --comport /dev/ttyUSB0 --baudrate 420000 --tcpport 5762 --ip 0.0.0.0
I tried to use another program (python serial2tcp) and it works correct
The text was updated successfully, but these errors were encountered: