Need to pass data from a battery powered sensor to a PC via a RF link. Would prefer
a COM Port emulation at 115,200 Baud. I already have a pair of nRF52 Development
Kits. Need a set of firmware files/project which looks like a COM port to a PC.
Need to pass data from a battery powered sensor to a PC via a RF link. Would prefer
a COM Port emulation at 115,200 Baud. I already have a pair of nRF52 Development
Kits. Need a set of firmware files/project which looks like a COM port to a PC.
Hi Warren
Regardless of which project you run the nRF52DK should enumerate a com port when connected to the PC, and the default baudrate is 115200.
This com port is set up by the Segger programming chip, and by default it will be connected to the UART interface of the nRF52832 device. This means that any data sent from the UART in the nRF52832 will be passed along to the virtual com port, through the Segger device (and vice versa for data sent from the PC).
If you need the nRF52 chip itself to act as a virtual com port you would have to get the nRF52840 DK, since the nRF52832 doesn't have an on chip USB interface.
Best regards
Torbjørn
You are not getting what I want or need!
I do NOT want to have anything to do with USB.
I need to replace a RS232 wired connection from a microcontroller that gathers sensor
data with a wireless solution at a high baud rate. The nRF must look like a COM port
to the Windows PC (via an intermediatory BlueTooth dongle).
If this can be done, then I need a project with this so configured.
Thanks,
Warren
Hi Warren
There is no standard serial port profile defined for BLE, like there was for Bluetooth classic, so there is no easy way to have a BLE device appear as a CDC device in Windows unfortunately.
If you can use a Nordic kit as the intermediary Bluetooth dongle then you can get around this quite easily: Simply program one DK with the ble_app_uart_c example, and connect it to the PC over USB (this kit will be the dongle). No changes to the code should be necessary.
Then program a second DK with the ble_app_uart example, and reassign the UART pins in the code so that you can connect the UART to an external device. Because of the pin crossbar in the device you can route the UART pins to any GPIO you like.
If using a Nordic kit as the dongle is not an option (which your comment regarding not having anything to do with USB seems to imply), then this is a bit more challenging.
In this case you need to connect to the Nordic device using BLE API's in Windows, and find some way to link the BLE device with a CDC device. Using something like this Virtual Serial Port Driver from Eltima you can create a virtual comport pair in Windows, and make a custom application that relays data between the BLE device and one of the virtual comports. The second virtual comport will then give you access to the remote BLE device as if it was a RS232 device.
Can you confirm whether or not you could use a Nordic device as the intermediary dongle?
It would certainly simplify your project greatly, rather than having to rely on third party solutions and constantly running Windows applications.
We just released the nRF52840 Dongle as well, which is intended to be a low cost programmable dongle for applications like the one you describe.
Best regards
Torbjørn
Hi Warren
There is no standard serial port profile defined for BLE, like there was for Bluetooth classic, so there is no easy way to have a BLE device appear as a CDC device in Windows unfortunately.
If you can use a Nordic kit as the intermediary Bluetooth dongle then you can get around this quite easily: Simply program one DK with the ble_app_uart_c example, and connect it to the PC over USB (this kit will be the dongle). No changes to the code should be necessary.
Then program a second DK with the ble_app_uart example, and reassign the UART pins in the code so that you can connect the UART to an external device. Because of the pin crossbar in the device you can route the UART pins to any GPIO you like.
If using a Nordic kit as the dongle is not an option (which your comment regarding not having anything to do with USB seems to imply), then this is a bit more challenging.
In this case you need to connect to the Nordic device using BLE API's in Windows, and find some way to link the BLE device with a CDC device. Using something like this Virtual Serial Port Driver from Eltima you can create a virtual comport pair in Windows, and make a custom application that relays data between the BLE device and one of the virtual comports. The second virtual comport will then give you access to the remote BLE device as if it was a RS232 device.
Can you confirm whether or not you could use a Nordic device as the intermediary dongle?
It would certainly simplify your project greatly, rather than having to rely on third party solutions and constantly running Windows applications.
We just released the nRF52840 Dongle as well, which is intended to be a low cost programmable dongle for applications like the one you describe.
Best regards
Torbjørn
