the rx1250 rover should be set to use "internet 1" to get corrections
"internet 1" talks to "port 3 (bluetooth)" set to use a GSM phone as a device.
you need:
1) android app called bluedun
2) bluetooth on the rx1250
3) ntrip turned on /set up/login / password / ntrip mount point set on the rx1250
4) make a new default GSM phone device for port 3 on the rx1250 for the bluetooth to talk to, gprs 115k n-8-1 etc. This seems to talk to blueDUN on the android phone ok.
should just work. maybe if you did all the cussing up front it would take less than the whole afternoon it took me yesterday.
root beers all around! Sure is amazing stuff when it works!
I only just figured out how to *answer* the dang smart phone a couple weeks ago.
Now I have an incentive to keep it charged ...
For a while I was doing it the other way round, with GNSS internet radio on a netbook and bridging the bluetooth to wifi. That uses the bluetooth more as a serial connection and lets the pc handle the NTRIP stuff.
edit: yah, sure you betcha, have at for a cheat sheet.
Now that it works, anyone want to trade a siemens MC75 cell modem in a GFU housing for a Leica 900mhz spread spectrum radio in a GFU housing? That would complete my ultimate hiking rig.
> the rx1250 rover should be set to use "internet 1" to get corrections
> "internet 1" talks to "port 3 (bluetooth)" set to use a GSM phone as a device.
I don't have an "internet 1," and I haven't been able to get my phone to pair with anything other than BT1, so I'm trying BT1 for the connection to the phone and -- temporarily, at least -- using a cable to the ATX1230.
> you need:
> 1) android app called bluedun
Got BlueDUN, but I'm not sure it's talking correctly with the RX1250.
> 2) bluetooth on the rx1250
I think I'm good there. I still haven't ironed out all the wrinkles, but I know there's BT communication.
> 3) ntrip turned on /set up/login / password / ntrip mount point set on the rx1250
Should be good there.
> 4) make a new default GSM phone device for port 3 on the rx1250 for the bluetooth to talk to, gprs 115k n-8-1 etc. This seems to talk to blueDUN on the android phone ok.
Item 4 is where I'm having trouble. Could you post all your settings under your GSM entry (AT commands, etc.)?
Thanks!
there will be a moment when you start blueDUN on the phone that it offers you 120 seconds to pair with the rx1250.
You might need to, at least once, on the rx1250, on your bt1 port, use "control" to get it to search for devices to pair with. (My phone shows up as a "Comet" but that's all I know -- the ATX1230 antenna also shows up but that is only for if you have SmartPole or some other strings on your Leica piano.
This is in older 1200 SmartWorx, so might be different on a newer unit.
I made a "new" GSM phone profile with the default settings as a device for Internet1 to talk to. Init strings were included in the defaults so I can't claim any genius or tweaking there.
Now that I think about it, on our unit there was at least an hour of going in circles to remember where I saw the chance to create "internet1". You have to create it before you use it. Trying to use just the bluetooth without Internet makes it work like a serial port instead of a network bridge.
Somewhere in the menus, you have to tell it to expect the RTK corrections on internet1 and then inetnet1 connects to your bluetooth port, sees a GSM phone there, and makes it dial.
Also somewhere in there, you have to get the rx1250 to pair with the phone, there will be a moment when you type in "0000" as a passcode on the BlueDUN end.
jim,
the proper order of things is you must firstly establish an internet connection with your GPRS device. you will know this happens properly when you pair with your phone and you will get status messages along the lines of 'port 3 connected' then 'GSM initialised' then 'Connected to the internet'. once the connection is established you will see a '@' looking symbol appear next to the stop-and-go icon (the little guy with a pole or tripod)
once the internet interface (phone) has been set up 'Net 1' 'Net 2' or 'Net 3' will become an option for the RTK interface. you can select any of these to set up you NTRIP details in.
if you want to send me your email i can send you the documentation a leica tech sent me on connecting to the internet and using NTRIP.
cheers.
> if you want to send me your email i can send you the documentation a leica tech sent me on connecting to the internet and using NTRIP.
I'll take all the info I can get: jhframe [at] dcn.org
Thanks!
yep! that is a clearer explanation of the "gotta create the internet connection before you can use it" concept.
Your "whole afternoon" experience is starting to look like a walk in the park compared with mine. I'm well into Day 2 of this. Getting closer, perhaps, but still not there.
I got the Internet interface created, and the NET1 port assigned to the Real-Time interface. However, when I start BlueDUN on my phone, here's what I see on the RX1250, in quick succession:
BT 1: No response from GSM
BT 1: GSM not initialized
BT 1: Bluetooth connection OK
BT 1: GSM initialized
BT 1: No Bluetooth connection
This cycle of messages repeats every 17 seconds or so.
On the phone, this is what BlueDUN reports on its interface, in the same cycle:
Waiting for BT Client...
BT Client Accepted...
Modem Negotiating...
My problem may be with the AT commands. My phone service is from Sprint, which is CDMA, so none of the default phone profiles are likely to work as-is. I don't know what the RX1250 is expecting in response to its AT command strings, so I'm in the dark as to how to configure those for my phone.
I set BlueDUN up to log everything to see if I could figure out what's going on. Below is a typical log entry for the cycle. If one of you who has this working can send me a BlueDUN log file of a successful session, that might point me in the right direction.
2012-09-23 15:06:06.111 PDT INFO com.blue_dun Thread-10855 - BT Client Rx Controller accepted: status=paired channel=3 socket=OK
2012-09-23 15:06:06.627 PDT INFO com.blue_dun Thread-10852 - Received AT data=[AT
]
2012-09-23 15:06:06.631 PDT DEBUG com.blue_dun Thread-10852 - Partial Command=[]
2012-09-23 15:06:06.636 PDT DEBUG com.blue_dun Thread-10852 - Composed AT Command=[AT
]
2012-09-23 15:06:06.643 PDT DEBUG com.blue_dun Thread-10852 - Elaborate AT Command=[AT
]
2012-09-23 15:06:06.648 PDT INFO com.blue_dun Thread-10852 - AT command: AT
2012-09-23 15:06:06.652 PDT INFO com.blue_dun Thread-10852 - Response: OK
2012-09-23 15:06:06.657 PDT INFO com.blue_dun Thread-10856 - Packet sent to BT channel, length=6
2012-09-23 15:06:07.186 PDT INFO com.blue_dun Thread-10852 - Received AT data=[AT+CPIN?
]
2012-09-23 15:06:07.193 PDT DEBUG com.blue_dun Thread-10852 - Partial Command=[]
2012-09-23 15:06:07.197 PDT DEBUG com.blue_dun Thread-10852 - Composed AT Command=[AT+CPIN?
]
2012-09-23 15:06:07.204 PDT DEBUG com.blue_dun Thread-10852 - Elaborate AT Command=[AT+CPIN?
]
2012-09-23 15:06:07.208 PDT INFO com.blue_dun Thread-10852 - AT+ command: AT+CPIN?
2012-09-23 15:06:07.213 PDT INFO com.blue_dun Thread-10852 - Response: OK
2012-09-23 15:06:07.218 PDT INFO com.blue_dun Thread-10856 - Packet sent to BT channel, length=6
2012-09-23 15:06:07.247 PDT INFO com.blue_dun Thread-10852 - Received AT data=[AT+CREG?
]
2012-09-23 15:06:07.252 PDT DEBUG com.blue_dun Thread-10852 - Partial Command=[]
2012-09-23 15:06:07.261 PDT DEBUG com.blue_dun Thread-10852 - Composed AT Command=[AT+CREG?
]
2012-09-23 15:06:07.266 PDT DEBUG com.blue_dun Thread-10852 - Elaborate AT Command=[AT+CREG?
]
2012-09-23 15:06:07.269 PDT INFO com.blue_dun Thread-10852 - AT+ command: AT+CREG?
2012-09-23 15:06:07.273 PDT INFO com.blue_dun Thread-10852 - Response: OK
2012-09-23 15:06:07.277 PDT INFO com.blue_dun Thread-10856 - Packet sent to BT channel, length=6
2012-09-23 15:06:10.313 PDT INFO com.blue_dun Thread-10852 - Received AT data=[AT+CREG?
]
2012-09-23 15:06:10.320 PDT DEBUG com.blue_dun Thread-10852 - Partial Command=[]
2012-09-23 15:06:10.323 PDT DEBUG com.blue_dun Thread-10852 - Composed AT Command=[AT+CREG?
]
2012-09-23 15:06:10.329 PDT DEBUG com.blue_dun Thread-10852 - Elaborate AT Command=[AT+CREG?
]
2012-09-23 15:06:10.332 PDT INFO com.blue_dun Thread-10852 - AT+ command: AT+CREG?
2012-09-23 15:06:10.336 PDT INFO com.blue_dun Thread-10852 - Response: OK
2012-09-23 15:06:10.340 PDT INFO com.blue_dun Thread-10856 - Packet sent to BT channel, length=6
2012-09-23 15:06:10.371 PDT ERROR com.blue_dun Thread-10852 - Read BT data error: Software caused connection abort
2012-09-23 15:06:20.552 PDT INFO com.blue_dun Thread-10852 - Before BT disconnect:BTServer_Thread stop=false
2012-09-23 15:06:20.630 PDT INFO com.blue_dun Thread-10852 - After BT disconnect:BTServer_Thread
if you make a "new" phone profile, is there a default for a CDMA phone?
> if you make a "new" phone profile, is there a default for a CDMA phone?
I thought there was one, but if there was I must have (ahem) unintentionally deleted it. I seem to recall looking at it's parameters, though, and finding that they were the same as for a modem. I may be mistaken about that, though.
jim,
easy fix. bring up the list of 'GPRS Internet Devices' again. press [SHIFT][F5]. all the default devices will reappear again.
cheers.
> easy fix. bring up the list of 'GPRS Internet Devices' again. press [SHIFT][F5]. all the default devices will reappear again.
Okay, did that. No CDMA, though. I guess the CDMA that was in there before was some sort of custom thing. If it held any magic secrets, they appear to be gone now. 🙁
Jim,
CDMA settings:
CDMA Phone,modem,yes,19200,none,8,1,RTS/CTS
GSM/CSD: no command lines listed
GPRS/Internet: Init 1:AT^D, Connect:ATD#777^M
just managed to connect our viva CS controller to the internet using BlueDUN. i used the settings for a nokia GPRS device.
> just managed to connect our viva CS controller to the internet using BlueDUN. i used the settings for a nokia GPRS device.
Is your Android device a GSM phone? I'm beginning to wonder if it's my carrier (Sprint), or CDMA itself that's causing the trouble. I used the settings half bubble suggested to create a new device, but I get the same connect/initialize/disconnect cycle noted above.
jim,
our devices are 3G & 3.5G. the settings for the nokia phone were for a GPRS device.
cheers.
Mrs. Bubble would be crushing it with the scientific method and graph paper. I just push the buttons as fast as the CPU will keep up until I have a feel for what crashes it and what changes the output messages. It's the "Everything is an electric guitar" approach. As soon as it works, whatever I did to get there is boring and irrelevant, because now I can get back to playing music / running the instrument / graceful surveying.
I have gotten techno-fatigue: Once something works, don't mess with it. If it stops working odds are higher all the time you will replace the unit rather than the settings. And the new unit will have a completely different interface, cable ends, batteries, data plan, vocabulary, etc.
There are learning curves, the knowledge at the top of which will serve you your whole life, and there are learning curves, the knowledge at the top of which will be obsolete before you get there, due to cables and batteries and firmware and memory cards and support contracts.
The vague memory that has surfaced this morning is that in some obscure menu, you have to enter the APN for the carrier. Mine is "epc.tmobile.com", probably you need something like that for Sprint. If you have already done this, never mind. Without it, you can dial the carrier all day and never get net.
never mind, looks like APNs are a GSM thing. still reading.
are you sure your plan allows tethering? Some carriers block things like BlueDUN so that you will upgrade to their $$$ tethering plan. When you do, they push out a tiny firmware patch to your phone to allow it -- with their service.
Not sure if the bluetooth can do more than one pairing at a time?
Use the cable to the ATX1230 if you want to use the bluetooth for the cell phone.
There was a moment when everything else was right when BlueDUN popped up a menu asking for a PIN for the Leica, and that is always "0000" -- only had to enter it once.
