> 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.
hello half bubble,
the RX has 3 bluetooth ports. we run 2 bluetooth ports on our GPS system simultaneously; one tethered to the ATX1230 and the other tethered to a mobile phone for the internet.
cheers.
Ah! TPS1200 Smart Station seems to have only one bluetooth port.
Leica upgraded it and the ATX1230 with bluetooth a year or two after the 1200s came out.
It looks like a (the?) fundamental problem I've been having is related to the way the RX1250 communicates with the modem on my phone. I've been exchanging email and log files with Mirko Solazzi, the BlueDUN developer, and he found some AT commands in use that his application didn't recognize. However, even after adding those in (I'm currently on BlueDUN v1.20c), the modem negotiation gets stuck in a loop indicating that the RX1250 is expecting a response that BlueDUN doesn't know how to provide.
Mr. Solazzi has asked me if I can provide a log file from a successful RX1250/BlueDUN session. If any of you have time to do this, here are the basic instructions:
1. Launch BlueDUN on your phone.
2. Go into the BlueDUN settings, scroll to the bottom and check the Enable Logger and Log to File boxes.
3. Fire up your RX1250 and run a successful modem session with BlueDUN. It doesn't have to be long, just long enough to get connected to a caster.
4. Close BlueDUN.
5. (You'll need a file browser for this next step. I like ES File Explorer, a free Android app.) Launch your file browser and navigate to the com.bluedun folder. Open the folder and locate application.log. (If you've logged other sessions you'll have multiple log files with names like application-1.log, application-2.log, etc.)
6. Once you've located the log file, there are a number of ways to proceed. Probably the easiest is to do a long press on the filename to bring up the Operations menu, then scroll down to Share. Tap Share and and scroll to your email application, tap the email app name to bring up a new message. Enter my email address (jhframe [at] dcn.org) and send it off.
7. Thanks!
OK mobilizing ... deploying tripod to back 40 and points beyond ... will submit data upon return to quarters
... check your email
jim,
i have successfully connected our TCRP1205+ to the internet via a samsung galaxy. i expect my trial with the GPS will be successful as it uses the same internet connection.
i used bludun and used settings for a GSM device. it uses AT commands in the GSM page only; no GPRS, the page is blank. you will need an APN to connect to the internet.
Init1_AT&FE0Q0V1X4S0=1^MAT+C
cont_MEE=0^MAT&W0^M
Init2:AT+CBST=^S,0,^C^M
Dial:ATD^#^M
Hangup:ATH^M
Escape:~~~~++
good luck.
My ignorance of GSM, CDMA and GPRS is near-total, which probably accounts for much of my trouble in this matter. What I'm particularly unclear about is how BlueDUN actually makes its connection. If it merely serves as a pass-through between the incoming bluetooth connection and the phone's modem, I may be chasing my tail. I assumed that it somehow took the TCP/IP data coming over the BT connection and passed it on to the phone's internal TCP/IP stack, but I now suspect that not to be what's happening.
I tried the GSM setup shown above, but it doesn't seem to matter what I put in the AT command fields of the RX1250, the log file always looks about the same: it shows a loop comprising three AT commands coming from the RX1250:
AT+CREG?
AT
AT+CPIN?
And the BlueDUN responses to them:
+CREG: 1,1
OK
+CPIN: READY OK
Lather, rinse, repeat.
I'm still waiting for the next response from the BlueDUN developer, who has been remarkably willing to help sort this out. Stay tuned!
well jim, turns out my confidence was misplaced; TPS1200 connects fine, GPS1200 no connection. I have some full debugging log files to send you if you want to send them on to the developer. one with a successful connection to the TPS and the other the unsuccessful connection to the GPS.
cheers.
hello Jim,
this is what a successful connection looks like
***************************************************
2012-09-27 10:44:37.385 AEST INFO com.blue_dun main - BlueDUN v.1.20 Started - Android=4.0.3
2012-09-27 10:44:38.692 AEST INFO com.blue_dun main - BlueDUN_Activity Clicked Start Service
2012-09-27 10:44:41.207 AEST INFO com.blue_dun Thread-2100 - Testing Internet: OK
2012-09-27 10:44:41.766 AEST INFO com.blue_dun main - BT Server channel 3 ready!
2012-09-27 10:45:03.589 AEST INFO com.blue_dun Thread-2102 - BT Client accepted: status=paired channel=3 socket=OK
2012-09-27 10:45:04.696 AEST INFO com.blue_dun Thread-2101 - Received AT data=[AT
]
2012-09-27 10:45:04.701 AEST DEBUG com.blue_dun Thread-2101 - Partial Command=[]
2012-09-27 10:45:04.706 AEST DEBUG com.blue_dun Thread-2101 - Composed AT Command=[AT
]
2012-09-27 10:45:04.710 AEST DEBUG com.blue_dun Thread-2101 - Elaborate AT Command=[AT
]
2012-09-27 10:45:04.717 AEST INFO com.blue_dun Thread-2101 - AT command: AT
2012-09-27 10:45:04.720 AEST INFO com.blue_dun Thread-2101 - Response: OK
2012-09-27 10:45:04.726 AEST INFO com.blue_dun Thread-2103 - Packet sent to BT channel, length=6
2012-09-27 10:45:05.252 AEST INFO com.blue_dun Thread-2101 - Received AT data=[AT+CPIN?
]
2012-09-27 10:45:05.256 AEST DEBUG com.blue_dun Thread-2101 - Partial Command=[]
2012-09-27 10:45:05.259 AEST DEBUG com.blue_dun Thread-2101 - Composed AT Command=[AT+CPIN?
]
2012-09-27 10:45:05.267 AEST DEBUG com.blue_dun Thread-2101 - Elaborate AT Command=[AT+CPIN?
]
2012-09-27 10:45:05.272 AEST INFO com.blue_dun Thread-2101 - AT+ command: AT+CPIN?
2012-09-27 10:45:05.278 AEST INFO com.blue_dun Thread-2101 - Response: OK
2012-09-27 10:45:05.283 AEST INFO com.blue_dun Thread-2103 - Packet sent to BT channel, length=6
2012-09-27 10:45:05.305 AEST INFO com.blue_dun Thread-2101 - Received AT data=[AT+CREG?
]
2012-09-27 10:45:05.309 AEST DEBUG com.blue_dun Thread-2101 - Partial Command=[]
2012-09-27 10:45:05.313 AEST DEBUG com.blue_dun Thread-2101 - Composed AT Command=[AT+CREG?
]
2012-09-27 10:45:05.317 AEST DEBUG com.blue_dun Thread-2101 - Elaborate AT Command=[AT+CREG?
]
2012-09-27 10:45:05.321 AEST INFO com.blue_dun Thread-2101 - AT+ command: AT+CREG?
2012-09-27 10:45:05.325 AEST INFO com.blue_dun Thread-2101 - Response: OK
2012-09-27 10:45:05.332 AEST INFO com.blue_dun Thread-2103 - Packet sent to BT channel, length=6
2012-09-27 10:45:08.368 AEST INFO com.blue_dun Thread-2101 - Received AT data=[AT+CREG?
]
2012-09-27 10:45:08.373 AEST DEBUG com.blue_dun Thread-2101 - Partial Command=[]
2012-09-27 10:45:08.379 AEST DEBUG com.blue_dun Thread-2101 - Composed AT Command=[AT+CREG?
]
2012-09-27 10:45:08.383 AEST DEBUG com.blue_dun Thread-2101 - Elaborate AT Command=[AT+CREG?
]
2012-09-27 10:45:08.388 AEST INFO com.blue_dun Thread-2101 - AT+ command: AT+CREG?
2012-09-27 10:45:08.394 AEST INFO com.blue_dun Thread-2101 - Response: OK
2012-09-27 10:45:08.406 AEST INFO com.blue_dun Thread-2103 - Packet sent to BT channel, length=6
2012-09-27 10:45:09.121 AEST INFO com.blue_dun Thread-2101 - Received Packet: 7E FF 03 C0 21 01 03 00 12 01 04 05 DC 05 06 00 00 95 36 07 02 08 02 D0 6B 7E
2012-09-27 10:45:09.134 AEST INFO com.blue_dun Thread-2101 - LCP frame type received
2012-09-27 10:45:09.145 AEST INFO com.blue_dun Thread-2101 - Option [code=1] not supported
2012-09-27 10:45:09.151 AEST INFO com.blue_dun Thread-2101 - Option [code=5] not supported
2012-09-27 10:45:09.155 AEST INFO com.blue_dun Thread-2101 - LCP Config Request [1] received, id=03 responseType=4
2012-09-27 10:45:09.163 AEST INFO com.blue_dun Thread-2101 - Sending Packet: 7E FF 03 C0 21 04 03 00 0E 01 04 05 DC 05 06 00 00 95 36 C7 9C 7E
2012-09-27 10:45:09.172 AEST DEBUG com.blue_dun Thread-2101 - Sending EsPack: 7E FF 7D 23 C0 21 7D 24 7D 23 7D 20 7D 2E 7D 21 7D 24 7D 25 DC 7D 25 7D 26 7D 20 7D 20 95 36 C7 9C 7E
this is what an unsuccessful connection looks like:
***************************************************************
2012-09-27 10:36:22.904 AEST INFO com.blue_dun main - BlueDUN v.1.20 Started - Android=4.0.3
2012-09-27 10:36:43.508 AEST INFO com.blue_dun main - BlueDUN_Activity Clicked Start Service
2012-09-27 10:36:47.449 AEST INFO com.blue_dun Thread-2089 - Testing Internet: OK
2012-09-27 10:36:48.292 AEST INFO com.blue_dun main - BT Server channel 3 ready!
2012-09-27 10:37:19.505 AEST INFO com.blue_dun Thread-2091 - BT Client Rx Controller accepted: status=paired channel=3 socket=OK
2012-09-27 10:37:21.275 AEST INFO com.blue_dun Thread-2090 - Received AT data=[AT
]
2012-09-27 10:37:21.279 AEST DEBUG com.blue_dun Thread-2090 - Partial Command=[]
2012-09-27 10:37:21.284 AEST DEBUG com.blue_dun Thread-2090 - Composed AT Command=[AT
]
2012-09-27 10:37:21.290 AEST DEBUG com.blue_dun Thread-2090 - Elaborate AT Command=[AT
]
2012-09-27 10:37:21.296 AEST INFO com.blue_dun Thread-2090 - AT command: AT
2012-09-27 10:37:21.301 AEST INFO com.blue_dun Thread-2090 - Response: OK
2012-09-27 10:37:21.306 AEST INFO com.blue_dun Thread-2092 - Packet sent to BT channel, length=6
2012-09-27 10:37:21.837 AEST INFO com.blue_dun Thread-2090 - Received AT data=[AT+CPIN?
]
2012-09-27 10:37:21.845 AEST DEBUG com.blue_dun Thread-2090 - Partial Command=[]
2012-09-27 10:37:21.848 AEST DEBUG com.blue_dun Thread-2090 - Composed AT Command=[AT+CPIN?
]
2012-09-27 10:37:21.856 AEST DEBUG com.blue_dun Thread-2090 - Elaborate AT Command=[AT+CPIN?
]
2012-09-27 10:37:21.861 AEST INFO com.blue_dun Thread-2090 - AT+ command: AT+CPIN?
2012-09-27 10:37:21.866 AEST INFO com.blue_dun Thread-2090 - Response: OK
2012-09-27 10:37:21.872 AEST INFO com.blue_dun Thread-2092 - Packet sent to BT channel, length=6
2012-09-27 10:37:21.902 AEST INFO com.blue_dun Thread-2090 - Received AT data=[AT+CREG?
]
2012-09-27 10:37:21.906 AEST DEBUG com.blue_dun Thread-2090 - Partial Command=[]
2012-09-27 10:37:21.909 AEST DEBUG com.blue_dun Thread-2090 - Composed AT Command=[AT+CREG?
]
2012-09-27 10:37:21.916 AEST DEBUG com.blue_dun Thread-2090 - Elaborate AT Command=[AT+CREG?
]
2012-09-27 10:37:21.919 AEST INFO com.blue_dun Thread-2090 - AT+ command: AT+CREG?
2012-09-27 10:37:21.927 AEST INFO com.blue_dun Thread-2090 - Response: OK
2012-09-27 10:37:21.931 AEST INFO com.blue_dun Thread-2092 - Packet sent to BT channel, length=6
2012-09-27 10:37:24.972 AEST INFO com.blue_dun Thread-2090 - Received AT data=[AT+CREG?
]
2012-09-27 10:37:24.979 AEST DEBUG com.blue_dun Thread-2090 - Partial Command=[]
2012-09-27 10:37:24.985 AEST DEBUG com.blue_dun Thread-2090 - Composed AT Command=[AT+CREG?
]
2012-09-27 10:37:24.990 AEST DEBUG com.blue_dun Thread-2090 - Elaborate AT Command=[AT+CREG?
]
2012-09-27 10:37:24.994 AEST INFO com.blue_dun Thread-2090 - AT+ command: AT+CREG?
2012-09-27 10:37:25.002 AEST INFO com.blue_dun Thread-2090 - Response: OK
2012-09-27 10:37:25.007 AEST INFO com.blue_dun Thread-2092 - Packet sent to BT channel, length=6
2012-09-27 10:37:25.049 AEST ERROR com.blue_dun Thread-2090 - Read BT data error: Software caused connection abort
2012-09-27 10:37:35.238 AEST INFO com.blue_dun Thread-2090 - Before BT disconnect:BTServer_Thread stop=false
2012-09-27 10:37:35.257 AEST INFO com.blue_dun Thread-2090 - After BT disconnect:BTServer_Thread
2012-09-27 10:38:10.540 AEST INFO com.blue_dun Thread-2093 - BT Client Rx Controller accepted: status=paired channel=3 socket=OK
2012-09-27 10:38:12.252 AEST INFO com.blue_dun Thread-2090 - Received AT data=[AT
]
2012-09-27 10:38:12.257 AEST DEBUG com.blue_dun Thread-2090 - Partial Command=[]
2012-09-27 10:38:12.262 AEST DEBUG com.blue_dun Thread-2090 - Composed AT Command=[AT
]
2012-09-27 10:38:12.267 AEST DEBUG com.blue_dun Thread-2090 - Elaborate AT Command=[AT
]
2012-09-27 10:38:12.273 AEST INFO com.blue_dun Thread-2090 - AT command: AT
2012-09-27 10:38:12.276 AEST INFO com.blue_dun Thread-2090 - Response: OK
2012-09-27 10:38:12.281 AEST INFO com.blue_dun Thread-2094 - Packet sent to BT channel, length=6
2012-09-27 10:38:12.815 AEST INFO com.blue_dun Thread-2090 - Received AT data=[AT+CPIN?
]
2012-09-27 10:38:12.822 AEST DEBUG com.blue_dun Thread-2090 - Partial Command=[]
2012-09-27 10:38:12.827 AEST DEBUG com.blue_dun Thread-2090 - Composed AT Command=[AT+CPIN?
]
2012-09-27 10:38:12.832 AEST DEBUG com.blue_dun Thread-2090 - Elaborate AT Command=[AT+CPIN?
]
2012-09-27 10:38:12.838 AEST INFO com.blue_dun Thread-2090 - AT+ command: AT+CPIN?
2012-09-27 10:38:12.849 AEST INFO com.blue_dun Thread-2090 - Response: OK
2012-09-27 10:38:12.853 AEST INFO com.blue_dun Thread-2094 - Packet sent to BT channel, length=6
2012-09-27 10:38:12.873 AEST INFO com.blue_dun Thread-2090 - Received AT data=[AT+CREG?
]
2012-09-27 10:38:12.878 AEST DEBUG com.blue_dun Thread-2090 - Partial Command=[]
2012-09-27 10:38:12.883 AEST DEBUG com.blue_dun Thread-2090 - Composed AT Command=[AT+CREG?
]
2012-09-27 10:38:12.888 AEST DEBUG com.blue_dun Thread-2090 - Elaborate AT Command=[AT+CREG?
]
2012-09-27 10:38:12.895 AEST INFO com.blue_dun Thread-2090 - AT+ command: AT+CREG?
2012-09-27 10:38:12.900 AEST INFO com.blue_dun Thread-2090 - Response: OK
2012-09-27 10:38:12.904 AEST INFO com.blue_dun Thread-2094 - Packet sent to BT channel, length=6
2012-09-27 10:38:15.962 AEST INFO com.blue_dun Thread-2090 - Received AT data=[AT+CREG?
]
2012-09-27 10:38:15.966 AEST DEBUG com.blue_dun Thread-2090 - Partial Command=[]
2012-09-27 10:38:15.969 AEST DEBUG com.blue_dun Thread-2090 - Composed AT Command=[AT+CREG?
]
2012-09-27 10:38:15.978 AEST DEBUG com.blue_dun Thread-2090 - Elaborate AT Command=[AT+CREG?
]
2012-09-27 10:38:15.984 AEST INFO com.blue_dun Thread-2090 - AT+ command: AT+CREG?
2012-09-27 10:38:15.988 AEST INFO com.blue_dun Thread-2090 - Response: OK
2012-09-27 10:38:15.994 AEST INFO com.blue_dun Thread-2094 - Packet sent to BT channel, length=6
2012-09-27 10:38:16.063 AEST ERROR com.blue_dun Thread-2090 - Read BT data error: Software caused connection abort
2012-09-27 10:38:26.250 AEST INFO com.blue_dun Thread-2090 - Before BT disconnect:BTServer_Thread stop=false
2012-09-27 10:38:26.272 AEST INFO com.blue_dun Thread-2090 - After BT disconnect:BTServer_Thread
2012-09-27 10:38:30.790 AEST INFO com.blue_dun main - BlueDUN_Activity Clicked Stop Service
2012-09-27 10:38:30.806 AEST INFO com.blue_dun main - Before BT disconnect:BlueDUN Service stop=true
2012-09-27 10:38:30.807 AEST INFO com.blue_dun Thread-2090 - BTServer_Thread exit
2012-09-27 10:38:30.813 AEST INFO com.blue_dun Thread-2095 - Fail to accept BT client: Operation Canceled
2012-09-27 10:38:30.838 AEST INFO com.blue_dun main - After BT disconnect:BlueDUN Service
2012-09-27 10:38:35.247 AEST INFO com.blue_dun main - BlueDUN v.1.20 Closed
What caused the unsuccessful session? Both those logs looks like most of the logs I've recorded, except mine never got to the part where actual NTRIP data was transferred.
The BlueDUN developer is stumped -- he needs to know what the RX1250 is expecting in response to the CPIN and CREG commands. And I'm hopelessly in the dark as to the sticking points.
in the bluedun settings i have enabled the command to ignore AT command errors. it may ave made a difference.
jim, my guess is that there may be slight differences in how the connection is being handled software wise due to operating system differences. The TPS1200 runs on a windows CE kernel. The VIVA controller is running on windows CE 6.0. the RX1250 is runing on the earlier windows CE 5.0.
when you drop out into windows and look at the CE networking i think you can see that smartworx was just front-ending to windows CE and creating connections in windows. 6.0 may be better than 5.0, and the TPS1200 may be managing the connection itself being on a kernel.
i have another RX1250 in the office, circa 2008, which is versus about 2004 for the one i have unsuccessfully tried to connect. i will give it a try and get back to you.
The older TPS 1200s run a VXworks kernel, which is a stripped-down UNIX-like kernel. Same as the Mars rover.
I also checked the "ignore AT command errors" box. Everything worked (and I am starting to see how lucky that was!) so I haven't tried it unchecked.
> The older TPS 1200s run a VXworks kernel, which is a stripped-down UNIX-like kernel. Same as the Mars rover.
>
> I also checked the "ignore AT command errors" box. Everything worked (and I am starting to see how lucky that was!) so I haven't tried it unchecked.
half bubble,
did your info about the VXworks kernel come from a leica tech too? my local techs told me it was a windows CE kernel?? i'm starting to wonder if some of them just guess at this stuff?!?!:-S
I think I have some actual lit that says so. It sure acts like it. When the 1200 first came out they were telling everyone it was great because it wasn't WinCE.
In the USA people wanted to run more familiar data collector software. So Leica changed over to CE give that option (and eventually developed Viva, I gather). I think the RX1250 / Smart Rover package was the first with CE?
I have no idea if later TPS1200s are using CE instead of vxWorks. Seems likely the 1200+ units are.