Stalled Pipe

RE: Stalled Pipe

Hung Bui — Thu, 19 Feb 2015 10:10:16 GMT

@Darren: Could you take a screen shot of what you have in Device Manager ? Usually you should see only one device (COM port) for each dongle.
(You may need to update the image in your Question since it's not possible to post comment with image).

RE: Stalled Pipe

DazzaNL — Wed, 18 Feb 2015 13:57:55 GMT

The original questions I asked here haven't been answered, I still don't know why the pipe stalls and why there are 3 J-link devices identified by windows. If I were to develop my own application, how do I know which device to use out of the 3? How do I know that the stalling pipe isn't a bug in the firmware or that my hardware isn't faulty? I would be trying to solve these issues with my code whereas they may be more fundamental.

Regards,

Darren.

RE: Stalled Pipe

Hung Bui — Tue, 17 Feb 2015 14:09:16 GMT

@DazzaNL: You have accepted the answer on the case that Kenneth handles. Do you still have any confusion regarding this case ? As Kenneth mentioned the S210 and ANTUSB-m are different and they don't have the same interface.

RE: Stalled Pipe

DazzaNL — Thu, 12 Feb 2015 09:15:04 GMT

Also, I asked this question some days ago. When I did the first project I used HEX codes to communicate with the ANTUSB-m, so for example to assign a channel would be something like "A4 04 42 00 00 00 00 E2" and this worked really well. These HEX commands are all listed on the documentation for the ANT Stack under the S210 documentation. This is the cause of some of my confusion as to why it doesn't work.

RE: Stalled Pipe

DazzaNL — Thu, 12 Feb 2015 08:39:28 GMT

Hi,

Thank you for your reply, although I must admit to being a little confused. The documentation for the S210 is almost exactly the same as the one for the ANTUSB-m, leading me to think that it was effectively the same thing.

I have worked through the examples in the past but none of them allow me to do what I need. If I have the Bike S&C example on the DK board what do I need to have on the Dongle to receive the data?

Ultimately I need to be able to configure 8 channels (from LabVIEW) that will connect to 8 different DK boards that will be running the same software, except for the channel numbers. If this is easier to implement on the ANTUSB-m then I will use that but surely it is also possible on the dongle without significant coding?

Thanks again for your help.

Darren.

RE: Stalled Pipe

Hung Bui — Wed, 11 Feb 2015 22:22:36 GMT

Hi DazzaNL,

The nRF51 Dongle is quite different from the ANTUSB.m dongle.

The S210 won't handle any command from the USB port. The S210 provides an ANT stack that the application programmed on the chip can use to set up to transmit and receive ANT package.

The USB interface on the dongle mainly works as an USB-COM port. And if you want to control the dongle from PC you would need to develop your own application that receive command from UART and then process that command to transmit or receive ANT packet.

I would suggest you to follow the quick start section here. You can try the broadcast example that you can use ANTUSB-m to verify that the nRF51 dongle broadcasts something.

RE: Stalled Pipe

DazzaNL — Wed, 11 Feb 2015 15:59:02 GMT

Hi,

I am trying to communicate with the Dongle as a USB RAW device from LabVIEW. I have previously done the same thing with an ANTUSB-m device but now I want to expand my application further. For testing purposes I am using the Bike S&C application on the nRF51 DK board to test the setup.

I have only placed the S210 onto the dongle, my understanding is that this will allow me to send my own HEX commands the same as for the ANTUSB-m. Is this true?

Cheers,

Darren.

RE: Stalled Pipe

Hung Bui — Wed, 11 Feb 2015 15:38:43 GMT

Hi Darren,

Could you let me know more about the set-up you trying to make ?

Which application did you flash on the chip besides the S210 softdevice dongle ?

How do you want to control the dongle from the PC via USB ?