arrie
commented
10 years ago Hi Nathan,
In an attempt to provide you with some more information on my current scenario, i've flashed again and started from scratch. I loaded the arduino with the irq ping sample(learn something new every day). Also rewired the rbpi according to this link: (https://gist.github.com/natevw/5789019)
Results are closer it seems, below the feedback from the 2 units:
on the arduino(ping) Now sending 75146 Now sending 76147 Now sending 77148 Now sending 78148
on the rbpi(pong) PONG back
Then switched roles around with the following result
on the arduino:(pong) RF24/examples/pingpair_irq/ ROLE: Receiver STATUS = 0xff RX_DR=1 TX_DS=1 MAX_RT=1 RX_P_NO=7 TX_FULL=1 RX_ADDR_P0-1 = 0xffffffffff RX_PW_P0-6
on the rbpi(ping) PING out Piping out 0 Piping out 1 ...... Piping out 16
This time I was actually able to see an error begin thrown: events.js:72 thow er; // Unhandled 'error' event ^ Error: Packet timeout, transmit queue flushed. at index.js:340:28 at index.js:79:25
Here's where i'm currently stuck. Think i'm very close - but obviously still missing something. Any ideas?
Kind Regards, Armand.
natevw
Hi Nathan,
First off, thank you for the time and effort you put into these projects - really appreciated by somebody as inexperienced as me. I'm extremely new to the world of programming for hardware and still learning, so please bear with me.
In short: I'm trying to get comms from a rbpi to an arduino via a node restfull service. I'm currently testing using express with node 0.10.2. I have confirmed that the rbpi can indeed communicate with the arduino by running stanleyseow's pingtest - so as far as I know the actual hardware seems to function as expected. In all the tests stanleyseow's ping app is loaded on the arduino.
I've tried using this repo (node-nrf) in order to get things going, but with no luck thus far. I installed all the dependencies via sudo npm install. The app seems to runs fine, but with either option (ping/pong) when running node test.js there seems to be no comms sent or received from the arduino when I look at the serial monitor on the arduino. I know this is a bit vague, but i'm not sure how one would go about debugging a problem like this? My first thought was that perhaps it's got something to do with permissions, or perhaps that for this project the nrf module needs to be hooked up differently?
I've also tried using your other project (node-rf24) where you created a node wrapper for stanleyseow's implementation. I fixed the compile error for node 0.10.x by adding the needed type cast 'uv_after_work_cb' to the 'uv_queue_work' methods where applicable, but unfortunately ran into problems here as well. Everything compiled fine, and node-gyp successfully compiled the node module, but it seems that when I try and do any call, I get a segmentation fault, after-which the service simply stops. I've seen the segmentation fault before when running the RF24 pingtest example without elevated permissions. I have tried running node as root - but this seems to have no effect.
I was hoping you would be able to provide me with some insight or possible solutions for my problems in order to get going - as the project i'm working on only needs really simple comms just to get started with the rest layer in order to do a poc. Hope to hear back from you.
Kind Regards, Armand.