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

Support for reading second GPS instance is broken #8945

Closed
priseborough opened this issue Feb 22, 2018 · 9 comments · Fixed by #9019
Closed

Support for reading second GPS instance is broken #8945

priseborough opened this issue Feb 22, 2018 · 9 comments · Fixed by #9019
Assignees
Labels

Comments

@priseborough
Copy link
Contributor

Bug Report

The firmware at commit 19e706f is unable to read a second GPS receiver connected to the TELEM2 port of a pixracer after making the following modifications:

  1. set SYS_COMPANION to zero
  2. Modify rcS file to start the second GPS instance, eg priseborough@f273157

The following console output is generated when the GPS status is queried:

screen shot 2018-02-23 at 8 16 17 am

Both reeceivers are UBlox M8N units and both work when plugged into the GPS port. The TELEM2 port is able to connect to a modem under normal usage.

@priseborough priseborough changed the title Pixracer unable to read data from second GPS Support for reading second GPS instance is broken Mar 4, 2018
@priseborough
Copy link
Contributor Author

I have repeated this test with a pixhawk cube and it is not possible to get a GPS to connect to any port other than the default GPS port. The test used this commit to prevent GPS or companion computer connections starting on boot:

priseborough@8f2faf1

On the pixracer I connected the GPS receiver to the TELEM2 port and attempted to start using' gps start -d /dev/ttyS2'

The driver cycled through a range of GPS protocols and baud rates attempting to connect.

Repeating this test using the GPS connected to the TELEM2 port on a pixhawk 'cube' and starting the GPS via 'gps start -d /dev/ttyS2' produced the same result. I was unable to find a port mapping that worked for the GPS2 port.

@bkueng
Copy link
Member

bkueng commented Mar 5, 2018

This should fix it: #9019. Can you cross-test it?

@priseborough
Copy link
Contributor Author

Fixed on my hardware TXS.

@Rickyg32
Copy link

Rickyg32 commented Apr 1, 2018

Has this issue been fixed in a gold release of code. I have the latest official build on my pixracer and it doesn't see the second GPS so curious how to get it working.

@bkueng
Copy link
Member

bkueng commented Apr 3, 2018

Not yet, just in the latest beta version.

@Rickyg32
Copy link

Rickyg32 commented Apr 3, 2018

bkueng thanks man. any idea on timing. I am a month away from wanting to maiden this new build so its not a problem for me right now. But you know what its like,m you want to remove all the bugs as you encounter them before you put it in the air.

@bkueng
Copy link
Member

bkueng commented Apr 3, 2018

Hard to say, but a month should be enough. Alternatively you can:

@Rickyg32
Copy link

Rickyg32 commented Apr 3, 2018

Thanks man. I can wait. I have lots to do and the reality is, even if I wanted to maiden tomorrow, missing a gps isn't a real issue. I can wait, I just appreciate your getting back to me. I truly appreciate it

@Rickyg32
Copy link

hows that new release coming

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

Successfully merging a pull request may close this issue.

3 participants