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

UAVCAN node id falsely identified as duplicate id #15477

Open
flytrexguy opened this issue Oct 1, 2020 · 10 comments
Open

UAVCAN node id falsely identified as duplicate id #15477

flytrexguy opened this issue Oct 1, 2020 · 10 comments
Labels

Comments

@flytrexguy
Copy link

Bug report

Issue details

The map of node's unique hardware id to UAVCAN node id is stored in persistent storage. So when connecting a different device with the same node id (after disconnecting the first device and rebooting AP of course) it will report it as duplicate id.

How to recreate the bug:
Connect a UAVCAN device with a static node id. Then reboot AP and connect a different device (with a different hw id) with the same static node id.

Version
Copter-4.0.4

Platform
[ ] All
[ ] AntennaTracker
[X] Copter
[ ] Plane
[ ] Rover
[ ] Submarine

Airframe type
hex

Hardware type
mRoControlZeroF7

@Vkd4U2NtVkZOVg
Copy link

Vkd4U2NtVkZOVg commented Oct 31, 2020

Have the same issue with CUAV X7 Pro and UAVCAN pmu, I have two same pmu with the same id, one of them is broken, so I replace with the other one, but the PreArm: UC: Duplicate Node com.hex.here../xx pops up. So I have to disable the pmu by now. any idea how to solve this?

@IamPete1 IamPete1 added the CAN label Aug 16, 2021
@JacksonUAS
Copy link

Was this ever resolved? Whats the work around? I think ive managed to recreate it :)

@tridge
Copy link
Contributor

tridge commented May 12, 2023

@JacksonUAS I've pinged @SchrodingersGat

@David-OConnor
Copy link
Contributor

I'm getting this too. Anything I can do to help?

@SchrodingersGat
Copy link
Contributor

From memory, @JacksonUAS resolved the issue by clearing the DNA cache

@JacksonUAS
Copy link

Never found a solution, clearing the cache solved it for a bit, then it came back. Went to Piccolo, no issues since.

@magicrub
Copy link
Contributor

Can people pretty please state what version they are running when reporting a problem.

@WickedShell
Copy link
Contributor

I've seen and resolved this on 4.0 aircraft with clearing the DNA cache.

So when connecting a different device with the same node id (after disconnecting the first device and rebooting AP of course) it will report it as duplicate id.

This sounds like it's working correctly? You used a different device with the same ID, that sounds like an error, what have I missed?

@JacksonUAS
Copy link

JacksonUAS commented Jul 25, 2023

Connecting the same device, with the same node ID, produces the error as well.

On the test aircraft we were using, ESC power was separate to avionics. Booting up the ESCs after the FC, and populating them on the bus, with static IDs, generated new instances in the DNA cache....

@David-OConnor
Copy link
Contributor

Same issue, re same device/same id.

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

No branches or pull requests

9 participants