2019-01-19 at 22:51 #2450markGuest
2019-01-20 at 11:11 #2452
Yes this is possible. SSP BT / BT Classic creates a COM port and this acts just like a serial cable. You need to pair the PC with the BT module used in the droipController to create the COM port. Once you have this select the port in the dropController Windows app.
See http://www.dropcontroller.com/connecting-dropcontrollerpc-via-bluetooth/. This is for a BlueSoleil Bluetooth dongle but the process is similar for other dongles.
2019-01-20 at 12:39 #2453
Just realised I changed the handshake for wired serial and this may no longer work.
2019-01-20 at 16:04 #2454markGuest
Oh OK – so I’m not sure which is the answer then.
I’m not using a dongle – my laptop has built in bluetooth. I’ve paired succesfully with the dropcontroller and when I look in my device manager I have 4 com ports set to 9600 8,N,1. When I open the windows app I’m given 4 com port choices 3,4,5,and 6 but I can’t connect through any of them
It’s not a big deal if I have to use a cable but if it’s possible wirelessly it’s one less wire in the mix.
2019-01-20 at 16:07 #2455markGuest
Actually I’ll add something to that. When I try to connect I get a ‘connecting’ message and that’s the end of it. I have to use task manager to kill the dropcontroller app – it never comes back and won’t close on its own.
2019-01-21 at 04:08 #2457markGuest
I see the problem. It’s in the form1.vb file.
If (count <= 12) Then
receivedData = ReceiveSerialData()
debug(“received data = ” & receivedData)
If (receivedData = “H”) Then
connected = True
debug(“HELLO reply received”)
Timer_checkConnect.Enabled = True
timerConnectFlag.Text = “ON”
The initial handshake is waiting for an H
The response from the arduino sketch, though, is
<V,184.108.40.206,Nov 1 2018><HELLO>
Any chance of getting a Windows build that will accept the appropriate handshake?
2019-01-21 at 21:20 #2458markGuest
I’ve gone ahead and fixed it so that it works with the current handshake – it will only work with the current version of the Android BT app.
If anyone needs it the .exe file can be found here. Just download the original from here and then overwrite the exe file with this one.
2019-01-22 at 01:02 #2459markGuest
Sorry – there was a second <FTS> handshake that I hadn’t noticed. The build has been updated and now seems to work fine
2019-01-24 at 02:52 #2461martynGuest
As you have discovered the windows app and the android app expect different commands for the handshake. I know I had a reason for changing them but can’t remember why. Probably lazy programming.
I am busy for the next week or two but when I get back I will try to update so that both usb and Bluetooth use the same commands again.
2019-02-08 at 13:11 #2531
- This topic has 9 replies, 2 voices, and was last updated 3 years, 7 months ago by .
Viewing 9 reply threads
Viewing 9 reply threads