USB to Bluetooth serial Adapter
Page 5 of IVTI50E Bluetooth Module User Manual IVT Corporation. BlueCore05-MM integrates a 16-bit stereo codec and it has a fully differential audio. OSy lei Blu oSy 5 Serial Interfaces lu 5.1 UART Interface oSy BlueSoleil I50e. With this one you can find out which one of your COM Ports are from a Bluetooth device: StackOverflow - Determine if serial port is normal COM or SPP I hope it helps somehow. If you find out how to do what you wanted, please let me know.
The Parani-SD1000U is a class 1 type Bluetooth USB adapter for Serial Port Replacement that supports 300 meters of wireless transmission distance by default. The working distance can be further extended up to 1000 meters using different antenna options. It is suitable for industrial and special applications because it has a longer communicaiton distance (1000m) than regular Bluetooth USB adapters. Allows up to 4 serial devices to be connected to PC USB port by Bluetooth wireless
USB Bluetooth Features
- Bluetooth Specification v2.0 + EDR Class 1
- Working distance (In an open field): Normally 300 meters, up to 1000m using patch antenna
- USB 2.0 interface
- Supports Windows, Linux, Mac OS and Windows CE.NET operating systems.
- No Bluetooth driver required. (No Toshiba or BlueSoleil driver required.)
- Provides transparent RS232 serial cable replacement for PC
- Supports Bluetooth Serial Port Profile (SPP)
- Supports up to 4 multiple simultaneous connections
- Interoperability with laptops, PDA terminals etc.
- Easy to use Windows configuration tool available.
- Remote configuration support
- Pairing button can also be used to pair Parani- SD1000U with any Bluetooth device that supports Bluetooth Serial Port Profile eg PARANI-SD1000 Serial to Bluetooth adapter.
- Using DIP switch, serial port parameters and flow control options can be easily configured without host computer
- Can connect to serial Bluetooth modules - PARANI-ESD1000 for your own PCBs
- Works with Sena BTerm App for Android Smart Phones
USB Bluetooth Serial Adapter Specification
Parani-SD1000U | |||||
Standards | - Bluetooth 2.0+EDR Class 1 - USB 2.0 | ||||
Max Transfer Rate | 3 Mbps (EDR) | ||||
Frequency Range | 2.402 ~ 2.480GHz | ||||
Transmit Output Power | +18dBm | ||||
Receive Sensitivity | - Basic 1Mbps: -90dBm - EDR 2Mbps: -88dBm - EDR 3Mbps: -87dBm | ||||
Diagnostic LED | - Mode - Connect - Serial-Rx/Tx | ||||
Antenna Connector | RP-SMA | ||||
Antenna Gain | - Default Stub Antenna: 1 dBi - Optional Dipole Antennas: 3 dBi & 5 dBi - Optional Patch Antenna: 9 dBi | ||||
Working Distance (In Open Field) |
| ||||
Driver Software | FTDI(FT232R) USB-Serial driver in public domain (http://www.ftdichip.com/Drivers/VCP.htm) No Toshiba or BlueSoleil driver required. | ||||
Supported Bluetooth Profiles | Serial Port Profile (SPP) | ||||
Computer OS Support | - Windows 7 - Windows 7 x64 - Windows Server 2008 - Windows Server 2008 x64 - Windows Vista - Windows Vista x64 - Windows Server 2003 - Windows Server 2003 x64 - Windows XP - Windows XP x64 - Windows 2000 - Windows ME - Windows 98 - Linux - Mac OS X - Mac OS 9 - Mac OS 8 - Windows CE.NET (Version 4.2 and greater) | ||||
Environmental | Operating Temperature: -20˚C ~ +70˚C | ||||
Storage Temperature: -40˚C ~ +85˚C | |||||
Humidity: 95% Non-condensing | |||||
Physical properties | Dimension(LxWxH):
| ||||
Weight: 56 g | |||||
Regulatory Approvals | FCC, CE, TELEC, KCC, IC, Bluetooth SIG | ||||
Warranty | 1 year limited warranty |
Bluetooth Serial networks
PARANI-SD1000U can operate as a master in a Bluetooth network with up to 4 slaves, where the slaves can be other venders products, more PARANI-SD1000U units or serial (RS232) to Bluetooth units - PARANI-SD1000.
Two network options are available:
Multi-drop mode
One master communicates with four slaves simultaneously and bidirectional (master <---> slaves), which can replace wired Multi drop feature of RS422/485.
Node switching mode
One Master (M) always keeps connected to four slaves (S1,S2,S3,S4), but it communicates with only one slave at a time. User can switch among the slaves by using an AT command.
Overview of Bluetooth Wireless solutions
Bluetooth Transforms are no longer supported.
In this profile, the Transform provides a virtual com port to communicate with the remote device. It can be used as a wireless replacement for RS232. To connect with the SPP profile, the remote device should first be paired with the local device. So to test the SPP profile, use the Pair/Unpair Transform along with the SPP Transform. In the Pair/Unpair Transform, specify the MAC address of the Remote device to connect with the SPP Profile.
Prerequisite
To use this Transform, the BlueSoleil Application should be installed. The BlueSoleil service must be running prior to creating and starting a Bluetooth project. Activating BlueSoleil can be done simply by plugging in the Bluetooth USB Network Adapter (dongle).
Creating a Harness for the Bluetooth SPP Connector using MxTransIt
1.Create an MxVDev project for Bluetooth SPP testing.
2.If necessary, select Simulation->Edit Harness from the MxVDev main menu to open MxTransIt.
3.To connect with SPP profile, the local device has to pair first. Select the Bluetooth PairUnpair Transform from the MxTransIt Toolbox.
4.Set the properties of the Bluetooth PairUnpair Transform.
5.Add the Bluetooth SPP Transform to the harness by double-clicking in the Toolbox.
Export the Ports
1.Right-click on the BluetoothTransform PairUnpair Transform and export the ports.
2.Right-click on the BluetoothSPP Transform and export the ports as shown below.
3.The Export Ports form is displayed:
4.Select the required ports from the list of available ports
5.Click OK to export all selected ports to MxVDev.
6.Click to save the harness.
Ports
Inport | |
SPPProfileConnect/Disconnect | This is a message Signal used to send commands to Connect/ Disconnect the SPP Profile. In MxVDev, double-click on the Signal to display this dialog and create a transition. |
Outports | |
SPPConnectionState | This is a discrete Signal, which gives the present status of the SPP connection. The Enum values of the SPPConnectionState variable are: •Connected. •NotConnected |
SPPResponse | This is a message Signal which shows the SPP profile response. |
SPP Testing
Local PC working as a Bluetooth SPP Initiator
1.Pair the local PC with the remote device using Pair/Unpair device variable as discussed in Pair/Unpair–Testing.
2.Create a Scenario and a TestCase with the SPPProfileConnect/Disconnect, SPPConnectionState, and SPPResponse Signals.
3.Connect the SPP profile by sending the connect command on the SPPProfileConnect/Disconnect Signal.
The connection status is displayed on SPPConnectionState. SPPResponse provides the responses from the SPP profile.
In the sample TestCase, SPP connects at time 5 seconds.
4.A virtual serial com port is generated if the SPP connection is successful on both systems.
5.Open the device manager to view the new com port numbers.
6.Open and configure the hyper terminals in local device as well in remote device using newly created com port numbers.
7.Enter text in HyperTerminal of the Local PC. The same text appears in HyperTerminal window of Remote PC as shown in the figures below.
Test PC as a Bluetooth SPP Acceptor |
1.Pair the Local PC with the Remote device using Pair/Unpair device variable as discussed in Pair/Unpair–Testing.
2.After pairing with the Head Unit (or any remote device which supports the SPP profile), the Head Unit initiates SPP connection by default. The Local PC accepts the SPP request from the Head Unit (or other remote device). There is no need to send the command to connect SPP with the Local PC.
Note: The remote device is a Head Unit in the vehicle or any other unit which supports SPP.
3.Create a Scenario and TestCase using the SPPConnectionState and SPPResponse Signals.
The connection status is displayed on the SPPConnectionState Signal. SPPResponse provides the responses of the SPP profile.
Below is a sample TestCase to test SPP profile connection. Here we are connecting SPP.
4.After Connecting the SPP profile, you can send AT commands or any other messages to the Head Unit (or any remote device) using the virtual serial port created by SPP the connection. The Head Unit (or other remote device unit which has the same capabilities) reads the commands or messages and responds.
In this way the Local PC can communicate with a Head Unit (or remote device) using SPP.
If the remote device closes the virtual com port connection, the SPP connection is closed at both sides.
Note: The remote device should be able to open the virtual com and send/receive data or an application should be present to process the messages.