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

Failed to ack / failed to write request / failed to send network tunnel txrx request #8

Open
LollosoSi opened this issue Apr 15, 2023 · 6 comments

Comments

@LollosoSi
Copy link

Hello, I'm setting up nrfnet in a raspberry pi 4 and 3, everything went okay until running, this is the output.
Perhaps one of my modules is faulty? ping seems to work, very slowly.
Some packets make it through

image

@LollosoSi
Copy link
Author

LollosoSi commented Apr 16, 2023

Nothing's wrong with my wiring or software, one of my radios seems to be unable to send ACK payloads for some reason. Some packets still make it through
Outputs of the two radios using the ManualAcknowledgements example (note: not the same instance in picture, numbers do not correspond for each transmission)
image
image

@LollosoSi
Copy link
Author

LollosoSi commented Apr 17, 2023

Adding a line consistent output for the 2 radios. Which one is broken? Could be both? The empty ACK packet makes me suspicious, not sure if that is expected behaviour
image
image

One of the two survived an ESC catching fire and blowing up, under an adapter board like this one
image
The regulator was slightly overvoltaged (6V) and ended up heating the radio module

Waiting for new modules to be delivered to confirm the hardware issue.
My research is over until someone responds

@LollosoSi LollosoSi changed the title Failed to ack / failed to write request / failed to send network tunner txrx request Failed to ack / failed to write request / failed to send network tunnel txrx request Apr 23, 2023
@LollosoSi
Copy link
Author

Update: received the new modules and the problem persists. perhaps it's related to wiring

@Kyuchumimo
Copy link

I have the same problem as this issue.

@LollosoSi
Copy link
Author

I have the same problem as this issue.

I ended up writing my own driver in my repo branch tunlink2. I haven't finished writing the new readme and two radios per board are recommended.

Have a look and let me know if you need more help

@LollosoSi
Copy link
Author

I have the same problem as this issue.

Is the problem solved?

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

No branches or pull requests

2 participants