Search found 26 matches
- Thu Feb 11, 2016 8:40 pm
- Forum: Developer discussions
- Topic: Crazyradio node driver help
- Replies: 14
- Views: 9830
Re: Crazyradio node driver help
Ya, I flashed it with what was on github a few months ago. Might try re-flashing again with the latest, but no, that's not what I got from the factory. Lemme see what I can do with the current set of tests, its encouraging that I got a callback, but it might be the continuous carrier mode test that ...
- Thu Feb 11, 2016 8:25 am
- Forum: Developer discussions
- Topic: Crazyradio node driver help
- Replies: 14
- Views: 9830
Re: Crazyradio node driver help
Thanks @arnaud, I'm seeing version 99.53 on my crazyradiopa. Crazyradio PA USB Dongle: Product ID: 0x7777 Vendor ID: 0x1915 (Nordic Semiconductor ASA) Version: 99.53 Serial Number: 15C15E4739 Speed: Up to 12 Mb/sec Manufacturer: Bitcraze Location ID: 0x14100000 / 6 Current Available (mA): 500 Curren...
- Tue Feb 09, 2016 5:18 pm
- Forum: Developer discussions
- Topic: Crazyradio node driver help
- Replies: 14
- Views: 9830
Re: Crazyradio node driver help
Wow, really strange. I still cannot get a read after sending an array packet. No led activity either. If I use the original crazyradio/examples/ptx.py I get the light and the callbacks. So I think the dongle is okay. Maybe this is a platform problem? What platform and node version are you using `nod...
- Tue Feb 09, 2016 1:26 am
- Forum: Developer discussions
- Topic: Crazyradio node driver help
- Replies: 14
- Views: 9830
Re: Crazyradio node driver help
Thanks @arnaud, I just updated the repo so if you pull it now, and run it, you should only see the one active test that's failing. It's not much different than the chrome client code, but instead of using the browser, I'm only using node and node-usb and mocha to run the tests. I'm pretty sure I'm d...
- Sun Feb 07, 2016 8:54 pm
- Forum: Developer discussions
- Topic: Crazyradio node driver help
- Replies: 14
- Views: 9830
Re: Crazyradio node driver help
@arnaud, I'm a little stuck here. The node-usb guys took a look at my code and they think its doing the right thing. I'm claiming interface 0, which has endpoint 0x01 and 0x81 and they are labeled out and in respectively. Then, I write an array to 0x01 and in the callback, I try reading from 0x81, b...
- Fri Feb 05, 2016 12:59 am
- Forum: Developer discussions
- Topic: Crazyradio node driver help
- Replies: 14
- Views: 9830
Re: Crazyradio node driver help
Its strange, I'm not sure if there's a bug in the usb library or I'm doing something wrong, but whenever I try to read from 0x81 it stalls out. In fact, the dongle seems to heat up too. Here's a thread I started with node-usb folks. https://github.com/nonolith/node-usb/issues/111 Any ideas? Thanks.
- Wed Feb 03, 2016 9:06 am
- Forum: Developer discussions
- Topic: Crazyradio node driver help
- Replies: 14
- Views: 9830
Re: Crazyradio node driver help
@arnaud, different question: I'm trying to setup bulk transfer out for endpoint 1, which I believe is correct. However, my test exits properly and then subsequent tests timeout. It looks like the endpoint is not released. Any idea? Here's the spec. describe.only('Packet tests', function() { var ifac...
- Wed Jan 20, 2016 5:39 am
- Forum: Developer discussions
- Topic: Crazyradio node driver help
- Replies: 14
- Views: 9830
Re: Crazyradio node driver help
Will do. Thanks!
- Tue Jan 19, 2016 7:45 am
- Forum: General discussions
- Topic: CrazyRadio not able to Connect to Scan for crazyflie
- Replies: 5
- Views: 6638
Re: CrazyRadio not able to Connect to Scan for crazyflie
also, if you're comfortable with node.js you can check your radio running the tests here: https://github.com/adjavaherian/crazyradio-node-driver. all tests should pass with dongle plugged in.
- Tue Jan 19, 2016 7:15 am
- Forum: Developer discussions
- Topic: LIBUSB_ERROR_ACCESS
- Replies: 18
- Views: 12160
Re: LIBUSB_ERROR_ACCESS
fyi, I was just working on a node-usb version of the radio driver and ran into a similar problem with lib_usb. I think you need to downgrade to node 0.12.7 if you haven't already and then re-run npm install. try the n node version manager if you haven't yet? https://github.com/tj/n