I’ve recieved my new Reach RS+ units, setting up a base station and rover for use in agricultural field. I’m connecting my rover to a Panasonic Toughbook CF31 and/or CF19 (which ever one I can get to work) but when trying to make connection to the Rover it treats the unit as a voice connection and errors out. I have run the old RS models on these toughbooks before with no issues. Is there a setting on these new units to make it connect as a serial connection as previously had with old models?
I also have a Send Error (111) on the position output which from a couple unsolved strings that may be my complication but no where does it describe how it effects BT connectivity.
The send error 111 is normal when there is no BT data flowing. Once connected it will go away.
It may a BT thing on the laptop even though it worked before, may something new with the BT on the PC complicating things.
Do some googling or youtubing about BT settings and connection. Going to have to fiddle around until you get it working unless someone here steps you through each step.
I was able to get a serial port to open on BT settings, but will fail connection. I cannot reproduce this issue with previous Rs models only these new RS+.
I cannot remember, and I am away from equipment, but I think when the BT connection is working, it has voice connection and a multimedia connection to? Can’t remember, but seemed to have 2 items here not just 1? Using BT settings in windows you can set up an incoming and outgoing BT port connection, you may be mixing them up?
ToreCrash (TB_RTK) has something on youtube about BT connections in Windows…check that out too.
Edit: well I cannot find it, but thought he had a windows BT tutorial…might have been someone else.
Thank you for the video and wished it had helped. Unfortunately my control panel looks different than yours, and I have a Bluetooth Local COM option with no settings to change when clicked, only to create Virtual COMM ports. I’ve also attached a photo of the error I get from trying to make connection to my Reach model.
Yeah they will be different with different OS versions but should still have similar or same settings to get things working. I am sure you have exhausted all the variable settings to try to get to work.
Maybe the Emlid people will jump in here.
Windows 10 here…but then again, I am using the non-plus Reach RS units. Looks like your using windows 7.
There might some encryption settings that need toggled? Maybe see if a update available for Windows BT driver?
The Bluetooth COM PORT should be INCOMING for communication from the Reach RS/RS+ correct?
Not OUTGOING COM PORT correct? Wonder if he has them backwards?
Maybe remove the devices altogether and start all over and reinitiate the BT link from scratch?
Same in ReachView BT setup. Make sure to use your BT password code that is in ReachView. Windows is weird, it will give a random code (i.e. 5318008)(read that upside down) and ask if it matches your 123456 code that is in ReachView and select yes and it works? go figure. WHile other programs devices must match the code in ReachView, i.e. 123456.
I think I may have narrowed it down to being a Windows 7 problem. Using other computers with Windows 10 I can connect BT. Currently downloading Windows 10 on our toughbooks to see if it works.
SIDE NOTE: I’m having serious concerns about heat stress on these new units. Have never had them unexpectedly shutdown while in the sun. 3 units that I’ve tested so far today have all at some point shutdown while outside in the sun. Anyone having similar problems?
