Skip to content
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

Allow Serial5 port to be available as MAVLink or other serial protocol #2552

Closed
utkinpol opened this issue Jul 13, 2015 · 12 comments
Closed

Comments

@utkinpol
Copy link
Contributor

Hi, Issue relates to the restriction on available serial ports in a dual GPS setup with Serial1 used for telemetry, Serial 2,3,4 used for GPS, Teensy, minimOSD, etc.
Integration with Storm32 controller requires a dedicated serial port and it would be helpful to have Serial5 port also available.
On certain boards such as AUAV x2 Serial4 port does not exist at all and it limits functionality even more.
It would be very helpful to have Serial5 port available.

@rmackay9 rmackay9 changed the title AC 3.3 - Allow Serial5 port to be available for general use Allow Serial5 port to be available as MAVLink or other serial protocol Jul 13, 2015
@Ivosch
Copy link

Ivosch commented Nov 8, 2016

Please plan this feature to the next release, I would appreciate it too.

@peterbarker
Copy link
Contributor

We can do this in master now.

@simjman
Copy link

simjman commented Apr 13, 2018

Is it possible to get this working in Antenna Tracker?

@amilcarlucas
Copy link
Contributor

Did you compiled the antenna tracker source code from master branch and tested it ?
What exactly did not work ?

@simjman
Copy link

simjman commented Apr 13, 2018

Yes I compiled the antenna tracker source code as I understand that it pulls this change from the libraries. I am not familiar with C#, but decided to have a look anyway. Would be interested to learn more, but don't really have the time at the moment - already wasted a couple of days following the logic behind the mavlink side of things.

Anyway, as soon as sysid_thismav changes (in my case, to 2), I was no longer able to connect to the pixhawk. It would sit in an endless loop of "getting params". When I changed the aerial platform to 10 and the tracker back to 1, it would connect, but would keep cycling the connection between the aerial platform and tracker and wouldn't show the parameters for the aerial platform in mission planner. Hope that makes sense.

@amilcarlucas
Copy link
Contributor

The source code for the tracker is written in C++, not C#. that one needs to be build from source.

Make sure you use the latest Mission Planner 1.3.56 or something like that. MP is written in C#. But there is no need to recompile it from source AFAIK.

@simjman
Copy link

simjman commented Apr 13, 2018

Ok no worries. My misunderstanding of the different languages. I'm not familiar with C++ either. I built it with source using the px4 console and I've also messed around in eclipse.

I should note that I have previously had the tracker working on v1.0.0 firmware, but now need the extra serial port.

@simjman
Copy link

simjman commented Apr 13, 2018

Also, I am using the latest version of mp

@rmackay9
Copy link
Contributor

rmackay9 commented Apr 14, 2018

No need to even compile it yourself actually. Just go to the MP's Install Firmware screen and press Ctrl-Q to get the bleeding edge developer version. It's untested though so it may not work.

@simjman
Copy link

simjman commented Apr 14, 2018

Ok good to know, will give it a crack now.

So it doesn't give the bleeding edge developer version for the antenna tracker - however all the others worked!

mp firmware install - ctrl q

@simjman
Copy link

simjman commented Apr 18, 2018

Ok so it does give the dev version for tracker even though the label doesn't update, however this gave the exact same problem I experienced from when I was building the firmware myself. The tracker gets hung up as soon as the vehicle connects and the sysid for the tracker changes (in this case to 2).

I tried changing the sysid of the vehicle and setting the tracker to 1, but this caused the tracker and vehicle to constantly cycle the connection. I understand that this isn't necessarily your issue, but changing the sysid of the vehicle from 1 also stopped the teensy on the tracker from sending telemetry to the taranis - this may be a simple change to the teensy code, but haven't looked into it (this was confirmed using the official working release).

Also, as a side note (and yes I understand this is more for the support forums or app development) does anyone know if it is possible for the tower app to work properly with the antenna tracker?

Appreciate your time and help.

@simjman
Copy link

simjman commented May 1, 2018

Is there going to be any traction on this or do I need to create an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants