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

PH2: UAVCAN GPS not found on CAN1 #5272

Closed
WickedShell opened this issue Nov 24, 2016 · 27 comments
Closed

PH2: UAVCAN GPS not found on CAN1 #5272

WickedShell opened this issue Nov 24, 2016 · 27 comments

Comments

@WickedShell
Copy link
Contributor

Issue details

UAVCAN GPS (Zubax GNSS2) is not detected on CAN1. Confirmed with AC3.4.2, but I suspect it applies to all firmware versions and have tagged it as such. Tested with BRD_UAVCAN 2, and GPS_TYPE 9. (Power cycled after shifting ports as #4902 is still unfixed).

Version

AC3.4.2 (bed521e)

Platform

[ x ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover

Hardware type

Pixhawk 2

@WickedShell
Copy link
Contributor Author

@tridge if you get a chance to look at this that would be helpful. I've confirmed that plane has the same behaviour (44c5fee)

@Benjammin88
Copy link

Same issue here, except I still cannot get external compass detection on can 2, only GPS

@Benjammin88
Copy link

Issue not being able to detect external compass still persists on 3.4.3

@proficnc
Copy link
Contributor

Is yours a version 1 or 2?

@Benjammin88
Copy link

Benjammin88 commented Dec 10, 2016 via email

@proficnc
Copy link
Contributor

proficnc commented Dec 10, 2016 via email

@Benjammin88
Copy link

Benjammin88 commented Dec 10, 2016 via email

@proficnc
Copy link
Contributor

proficnc commented Dec 10, 2016 via email

@WickedShell
Copy link
Contributor Author

WickedShell commented Dec 10, 2016 via email

@Benjammin88
Copy link

Benjammin88 commented Dec 10, 2016 via email

@WickedShell
Copy link
Contributor Author

WickedShell commented Dec 10, 2016 via email

@Benjammin88
Copy link

Benjammin88 commented Dec 10, 2016 via email

@magicrub
Copy link
Contributor

magicrub commented Dec 11, 2016 via email

@WickedShell
Copy link
Contributor Author

WickedShell commented Dec 11, 2016 via email

@Benjammin88
Copy link

Benjammin88 commented Dec 11, 2016 via email

@RoyPercepto
Copy link

Hi,
Any updates regarding this issue?
I can't get GPS/Compass on CAN1 and on CAN2 no Compass

@Benjammin88
Copy link

Benjammin88 commented Jan 22, 2017 via email

@magicrub
Copy link
Contributor

@benjammin1988 This is a generous offer, thank you! Any takers?

@tridge
Copy link
Contributor

tridge commented Jan 26, 2017

@benjammin1988 the most common issue is slow startup times of the CAN device, leading to it not being available when sensors are probed. I increased the delay time waiting for CAN startup recently. Can you please try with master (ie. 'latest' in MissionPlanner).
If it doesn't work, then please get a nsh shell, and run "uavcan status" first with the zubax on CAN1 then on CAN2. There are two ways to get a nsh shell:

  1. boot with no microSD inserted and connect to USB port as a serial device. Then run "uorb start", "uavcan start" and then after about 10 seconds run "uavcan status"
  2. boot normally and use nsh over MAVLink. MissionPlanner has this in its terminal connection menu. Just run "uavcan status" as uavcan will already be started

I'd love to get a Zubax2, but I suspect we'll be able to solve this together without you sending me one. For realtime diagnostics together please try gitter https://gitter.im/ArduPilot/Hardware or ping me on Skype as AndrewTridgell (or both!)

@Benjammin88
Copy link

Benjammin88 commented Jan 27, 2017 via email

@davidbitton
Copy link
Contributor

I have a PH2.1 and a Zubax 2. Here are the results from the nuttshell:

NuttShell (NSH)
nsh> uorb start
nsh> uavcan start
PX4: param_find(UAVCAN_NODE_ID)
PX4: param_find(UAVCAN_BITRATE)
uavcan: Node ID 1, bitrate 1000000
uavcan: SW version vcs_commit: 0x8a196281
uavcan: sensor bridge 'gnss' init ok
uavcan: sensor bridge 'mag' init ok
uavcan: sensor bridge 'baro' init ok
nsh> uavcan status
Pool allocator status:
        Capacity hard/soft: 500/250 blocks
        Reserved:  2 blocks
        Allocated: 2 blocks
UAVCAN node status:
        Internal failures: 0
        Transfer errors:   0
        RX transfers:      0
        TX transfers:      55
CAN1 status:
        HW errors: 27
        IO errors: 27
        RX frames: 21
        TX frames: 37
CAN2 status:
        HW errors: 4300
        IO errors: 4300
        RX frames: 0
        TX frames: 37
ESC actuators control groups: sub: 0 / req: 0 / fds: 2
ESC mixer: NONE
Sensor 'gnss':
RX errors: 0, receiver node id: N/A

Sensor 'mag':
devname: /dev/mag
channel 0: empty
channel 1: empty
channel 2: empty
channel 3: empty
channel 4: empty

Sensor 'baro':
devname: /dev/baro
channel 0: empty
channel 1: empty
channel 2: empty
channel 3: empty
channel 4: empty

nsh>

however I cannot get connect via MP terminal as terminal support was removed from the firmware. Thanks.

@Benjammin88
Copy link

Benjammin88 commented Feb 4, 2017 via email

@davidbitton
Copy link
Contributor

No I haven't. I was assume I should see multiple compass values in the Status tab of MP. Let me check.

@davidbitton
Copy link
Contributor

A live compass calibration failed for compass #1 which I'm guessing is on the Zubax.

@Benjammin88
Copy link

Benjammin88 commented Feb 4, 2017 via email

@WickedShell
Copy link
Contributor Author

@EShamaev this appears to still be an issue. Would you have a chance to look at this? (Additionally are you tracking detecting a GPS being detected after the system has been booted? Or is that just not on the agenda for UAVCAN gps's?)

@EShamaev
Copy link
Member

EShamaev commented Jun 8, 2017

This issue and last message is dated far before new CAN drivers.
So I will safely close this one, however we can continue on #6400

@EShamaev EShamaev closed this as completed Jun 8, 2017
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

8 participants