| Versions |
  |
|
| Author |
 Topic  |
|
frder
Italy
45 Posts |
 Posted - 04 mai 2006 : 22:55:06
|
The royaltek 2001 has the battery backup. So when SBAS is enabled, it remains enabled when the receiver is switched off and even if the main battery is pulled out.
francesco
|
Edited by - frder on 04 mai 2006 22:57:44 |
 |
|
|
gpspassion
93427 Posts |
Posted - 04 mai 2006 : 23:19:58
|
Well the BT-338 has a backup battery too, so that's not the deciding factor, but good news anyway, can't check on my 2001 though because SBAS is enabled by default. I guess I could disable it to see what happens ;-)
_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer? |
|
|
|
monobeg
7 Posts |
Posted - 04 mai 2006 : 23:28:01
|
Interesting.
So are there any SiRF III units out there now that don't have SBAS enabled by default? |
|
|
|
frder
Italy
45 Posts |
Posted - 05 mai 2006 : 12:46:26
|
The royaltek 2001, at least mine (december 2005), does'nt have the SBAS activated by default.
francesco |
Edited by - frder on 05 mai 2006 12:47:10 |
|
|
|
gpspassion
93427 Posts |
Posted - 05 mai 2006 : 13:03:28
|
Yes, they have different versions like Globalsat for the BT-338, can't find out though even looking at the FW version, having said that, what FW does yours have ?
_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer? |
|
|
|
frder
Italy
45 Posts |
Posted - 05 mai 2006 : 20:50:53
|
GSW3.1.1_3.1.00.07-C23B1.00
francesco |
|
|
|
dantexas
3 Posts |
Posted - 17 mai 2006 : 06:08:01
|
Here's my story: I have a GlobalSat BU-353 driver. The receiver was first recognized ok, but no fix. I was next to window but inside the house. Then I did something stupid: I played around with Sirf demo and changed to Sirf protocol. Now the receiver is no longer recognized in GPS Info and I cannot switch back to NMEA protocol in Sirf Demo (nothing happens if I choose "Switch to NMEA" from the Action menu).
I've disconnected the receiver from the computer and waited 24h (as suggested in another forum) for the receiver to reset to factory settings. Still, it is not recognized in GPS info.
How do you switch back to NMEA?
Is there another way to reset the receiver? |
|
|
|
gpspassion
93427 Posts |
Posted - 17 mai 2006 : 10:03:27
|
Welcome to the forums. With a wired receiver you can't do much wrong with that type of action, connect with SiRFdemo and then do Action/Synchronize, it should find it, then you can send a factory reset to go back to NMEA, see the tutorial on the first page for that.
_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer? |
|
|
|
dantexas
3 Posts |
Posted - 18 mai 2006 : 06:40:48
|
I've done what you suggested: connected with Sirf Demo, Action/Synchronize (it stopped at COM5:57600). Then Action/Switch to NMEA, then Action/Initialize-Data-Source (reset to factory settings).
However it does not seem to have any effect: no data appears in any window in SirfDemo, the "Switch to NMEA" option is still available and "Switch to Sirf mode" still unavailable.
How can I be sure the receiver has is really connected?
P.s. The red LED is now blinking, meaning that it got a fix, but the receiver is still not recognized.
|
|
|
|
Russel
Australia
49 Posts |
Posted - 18 mai 2006 : 12:38:44
|
Is there someone who can give the definitive explanation regarding baud rates, bluetooth and Sirf versions?
I have a BT318 and SirfDemo 3.18 . When I first tried out the unit it was emitting data, but garbled data. It looked rather like the kind of data you would get from a serial port but set to the wrong baud rate.
Pull battery out, wait, put back in. Fixed.
But that was just the start of the fun :-) I tried out SirfDemo. Works fine until you try to change to Sirf Binary mode. Then the same thing happens. I eventually figured out I had to manually submit the 'PSRF100' message to switch it to binary mode. I used 38400 baud. Ok, so now we are in binary mode. But, what exact command does SirfDemo send to the receiver to switch it? I'm guessing it's trying to send a switch plus change baud to 57600. However, I don't have a serial port logger (any reccomendations?) so I only see the ouptut messages.
Again, switching back to NMEA works but only if I tell SirfDemo to select 38400 baud. Any other rate and another battery out reset. So far, so weird.
Finally, When I try to use SirfDemo to send commands like for instance, initialise data source, same problem. It seems like SirfDemo is privately trying to send a baud rate change, but again, I don't get to see what it acutally sends.
Yeesh. Anyhow this raises issues I can't figure (and I design embedded systems for a living). It just feels like the receiver just doesn't take a liking to be told to change to a particular baud rate (my guess 57600). But that's just plain silly. Bluetooth should be transparent to baud rate. The virtual serial port should be forgiving.. and the UART in the ARM chip should support higher baud rates anyhow.
Btw, I get no grief from SirfTech with the same unit.
What *precisely* is happening? Is SirfDemo decidedly broken? Is it a firmware thing? And if so what versions does it affect?
-sleepdeprived |
|
|
|
gpspassion
93427 Posts |
Posted - 18 mai 2006 : 13:03:32
|
No, it's just that the BT-318 can't cope with concurrent baudrate/protocol changes, as the BT/GPS link is hard-coded on 38400 if memory serves, that was fixed on the BT-338
_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer? |
|
|
|
saimhe
Lithuania
134 Posts |
Posted - 18 mai 2006 : 13:50:54
|
quote:
Originally posted by Russel
I have a BT318 and SirfDemo 3.18 . When I first tried out the unit it was emitting data, but garbled data. It looked rather like the kind of data you would get from a serial port but set to the wrong baud rate.
It looked garbled at every baud rate available? (Did you try all rates in Hyperterminal or similar software?)
quote:
I eventually figured out I had to manually submit the 'PSRF100' message to switch it to binary mode.
Looks like yet another buggy firmware. What version is it?
quote:
I don't have a serial port logger (any reccomendations?)
A non-straightforward (but more flexible) solution: any serial port splitter together with any terminal application. |
|
|
|
Russel
Australia
49 Posts |
Posted - 18 mai 2006 : 14:27:17
|
Yes, on my initial inspection of the BT-318 I tried GPSInfo, Zeus Data Logger and Hyperterminal in all available baud rates. It looks like something seriously screwed up in the ARMs UART. (best guess)
As for the version I get:
SW Version 2.4.13.03-XTrac2.0.2-C3PROD1.0
The point remains, I can switch this device into Sirf Binary with SirfTech, but the way SirfDemo does the same thing, the problem reappears. It's only on SirfDemo that I have to issue the manual PSRF100 command.
Had a serial port spliter.. alas the danger of lending to freinds :) I thought I saw someone was coding a virtual serial port splitter somewhere (for multiple devices listening to the same unit) I lost the url.
In response to gpspassion. The problem occurs also when SirfDemo Issues message 128 initialise data source. Sending the same command manuall is fine. Also Im fairly sure it dies when I manually send a set main serial port command with 57600 as the rate.
One other thing I just noticed. It seems the BT-318 comes in two versions. the BT-318 SirfII/LP and the BT-318x SirfTrac version. Of course the 'x' doesn't feature on the sticker on the back or the packaging :-) (I really gotta wonder if a former customer didn't send this unit back after messing with it's flash :-; ) |
Edited by - Russel on 18 mai 2006 14:30:36 |
|
|
|
gpspassion
93427 Posts |
Posted - 18 mai 2006 : 14:53:38
|
Yes, that's xtrac indeed, but a rather oldish version (check the FW version thread).
You should be fine if you first connect at 57600 with SiRFdemo and then switch to SiRF, what the BT-318 doesn't like is baudrate+protocol change. In fact the first version of the BT-308 even crashed completely when you did that, had to take out the battery for 3 days !
_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer? |
|
|
|
Russel
Australia
49 Posts |
Posted - 18 mai 2006 : 16:54:49
|
| Setting the 'data source' of SirfDemo to 57600 *guarantees* it will go splat. Only baudrate that works in any context is 38400 :-) |
|
|
|
Topic |
|
|
|
| This page was generated in 4,22 seconds. |
 |
|
- 
- 
SiRFdemo tutorial (static navigation)
