| Versions |
  |
|
| Author |
 Topic  |
|
3950hh
China
4 Posts |
 Posted - 18 oct. 2006 : 01:42:13
|
Dear Carl@SiRF,
I'd bought a SiRF III Bluetooth GPS in China with the firmware version "GSW3.1.1-SDK3.1.00.07-C23P1.00", but I am not sure about it's type (it's named in Chinese "Fenghuo No.5", the agency told me it's a product of YTEC in Taiwan, but I can't found anything useful on there website, just estimate from the picture, it's similar with YTEC GPS-1200. On the rear of my unit (under the battery), I also found some words read:
Model: GPS-1200
P/N: TGA0A0010
S/N: 07050001437
My problems came out when I trying to disable SN:
1. After change to SiRF mode, I can't get any message via Bluetooth; I had to shortcut the backup battery at that time. I had tried several programs on both of PC and PPC. The problem is same.
2. Then I bought a cable and tried every baud rate to switch it to SiRF mode with several versions of SiRFdemo, I found under SiRF mode, Bluetooth will not give out any byte! Believe me, I'd read this topic throughly and tried every baudrate, I can connect it via bluetooth, just no output. Of cause the serial port(via cable) is OK.
3. BUT, after I disabled SN and test, I believe SN had been disabled, but just after a hot start, SN is enabled by itself!! I had tried this for several times and can't found a way to keep SN disabled after a hot/warm/cold start or out of power. This means if I want to use it with SN disabled, I have to disable it by PC, keep the power on and use it by PDA.
Would you please give me some information on this problem? Is this problem came from the firmware? Is it possible to solve it via firmware update/reflash? Can I use the firmware got from other manufacture? I can't found any other ways to get support!
Thanks!
|
Edited by - 3950hh on 18 oct. 2006 01:51:14 |
 |
|
|
Carl@SiRF
USA
158 Posts |
Posted - 18 oct. 2006 : 02:10:34
|
What you appear to be seeing with static nav is the way that unit was built. It appears that when power is removed that the battery backed-up memory is lost, or becomes corrupted. Unfortunately, that is not something that can be fixed by programming.
If you can talk to the unit over the serial cable, including switching it to SiRF binary, but can't get that to work over Bluetooth, I would suspect your problem is that you are relying on SiRFDemo to do your programming. When in NMEA mode, if you tell SiRFDemo to switch the unit to SiRF binary, SiRFDemo will select the baud rate for you, and in your case it selects a baud rate that does not match the Bluetooth modem. Find out what baud rate the modem uses, then compose your own NMEA command to switch to binary. Here is the format: $PSRF100,0,<baud rate>,8,1,0<CR><LF>. In this case, <baud rate> is where you put in 38400 or 19200 or whatever rate the modem uses. To compose this command using SiRFDemo, go to the Action menu and select Send Serial Message. In the message composer, click on the NMEA radio button in the bottom left corner of the menu. Then compose your message without using the $ or <CR><LF> -- SiRFDemo will put those in for you. See if that works for you. |
Carl - SiRF Customer Support |
|
|
|
3950hh
China
4 Posts |
Posted - 18 oct. 2006 : 11:12:46
|
Thanks for your quickly answer, Dear Carl!
Currently I believe the backup battery is not empty, because after switch to Sirfmode, I can still turn it back by shortcut the backup battery. Sure this is a problem of the way that unit was built, even I keep the main battery inside and charger connected, the SN will change by itself after a warm start.
For the problem of Bluetooth under Sirfmode, I had tried several programs under both PC and PPC, also tried the method you mentioned, I had also tried to change the speed under SiRFmode, Bluetooth never send out a byte under Sirfmode.
I am not sure it's a problem of the Bluetooth modem, because after switch back to NMEA mode with any one of the speed from 4800 to 57600, the Bluetooth port acts normal with every speed. i.e., I switch it back to NMEA with speed of 4800 and connect to the Bluetooth port with speed of 57600, the messages come out without any problem.
Any further suggestion? Thanks for your help again.
|
|
|
|
andreju
Slovenia
5 Posts |
Posted - 18 oct. 2006 : 17:00:32
|
Hi folks,
I have another problem. I'm trying to use the BT-313T from Navilock (the bluetooth receiver with TMC), I have actually a couple of them here. When I connect it to the PC or PDA and try to access the port, the navi SW freezes for some time, then reports that it can't open the port. Also if I try to access it with SIRFDemo (when I shoot 'open data port'), it freezes for a while and then reports that the port is somehow busy (cannot create UART handle. comm port is not available or may be in use). What's the problem here, anybody got a clue? Both receivers act the same. |
|
|
|
vettedude
USA
18 Posts |
Posted - 19 oct. 2006 : 23:55:34
|
| I have a US GlobalSat BT359 with the SiRF III. I tried to enable SBAS augmnentation, but the signal from the WAAS bird is too low, and the BT359 does not get lock. I also have a i-Blue 737 with the MTK chipset. The 737 sees PRN (SV) 122 loud and clear and operates in SBAS mode. I note that PRN 122 was recently moved. Does the SiRF III need a fimrware update to recognize the move of PRN 122? If not, why can't the BT359 pick up the WAAS signal? |
Clock + Sextant + Charts = GPS System |
|
|
|
gpspassion
93389 Posts |
Posted - 21 oct. 2006 : 03:27:11
|
erm...a friendly reminder that this is a discussion thread, not a hotline, so don't ignore the mesages posted above the one you're typing, at least acknowledge them if you can't help.
@andreju - is that the GNS5843 ? Due to the way it's designed with an extra port for TMC, I seem to remember you can't switch them to SiRF, hence the freezing.
@vettedude - I had the same problem in my SBAS testing I linked for you yesterday, you should probably catch up with that thread, no firmware upgrades have been made available for that.
@3950hh - actually was sent that receiver for testing the other day, haven't any time to do it yet. Looks like it resets all its setting if you send a reset command, not much you can do about that, but since you appear to have an iPaq 3950, you should be able to run either MMSiRFsetup or APLSirf linked from the first message here, if you have problems using them, post a message in their dedicated thread. |
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer? |
|
|
|
3950hh
China
4 Posts |
Posted - 23 oct. 2006 : 05:00:51
|
Hi gpspassion,
anyhow, this is a great thread, although it's not a hotline:-)
Currently I am using a dell x51v, and my id just show my memory of my 1st pda--iPaq 3950.
in fact, I had tried MMSiRFsetup and APLSirf and SiRFTech serveral times on x51v, since iPaq3950 doesn't have bluetooth it's not used with GPS.
I think my problem come from SiRF3 chipset and the program inside my unit (the firmware), not from the softwares on PPC/PC.
Problem 1 is no output via bluetooth under SiRF binarry mode.
Problem 2 is SN will be enabled by itself after Battery change/power off and on again/hot restart. |
|
|
|
andreju
Slovenia
5 Posts |
Posted - 24 oct. 2006 : 10:59:20
|
| @gpspassion: this seems to be exactly the same thing, yes. I don't really mind if I can't switch it to sirf, the problem I'm having is that I can't even connect to it in NMEA mode - the port doesn't seem to be prepared to be opened. When I connect to it with my bluetooth manager, I see only one outgoing port - is there something special one must do to reach the second port? I, apparently, don't know enough about TMC receivers, well, I'm a noob, what can I do :) |
|
|
|
gpspassion
93389 Posts |
Posted - 25 oct. 2006 : 02:10:26
|
Looks like it could be defective then, you should check with Navilock, not a SiRFdemo related problem in any case ;-)
@3950hh - yes, looks like the unit is not memorizing the settings, you'll have to change them when you need them. |
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer? |
|
|
|
GPS student
2 Posts |
Posted - 20 nov. 2006 : 11:11:57
|
I am working on understanding the Sirf demo SW. I have got some log files which are quite confusing to undestand.
I have seen the TTFF running from 35sec to 120sec. The test was conducted using a SiRFIII chipset, Patch of 40x40mm and the test was stationary. The position of the satellites did not change in respect to the antenna. So why did the receiver take so long to get a FIX?
quote:
Originally posted by gpspassion
Right, I was walking slowly, my point is that in these simultaneous recordings SiRFIII benefits from SN being disabled, not XT2 that produces pretty poor results regardless of SN.
_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer?
|
|
|
|
GPS student
2 Posts |
Posted - 20 nov. 2006 : 11:25:25
|
I am working with the SIRFIII demo and trying to understand the log files that the Sirf Demo spit out. I am quite confused that when the antenna is stationary (antenna used is 40x40mm), the satellites position has not changed after running the device in cold starts with respect to the antenna, I am not sure why the TTFF timing are so different. I have seen TTFF running from 30sec to 120sec. Could it be the receiver taking up some time to initialize?
quote:
Originally posted by Carl@SiRF
Xtrac 2.1 software was recently released, and specifically addresses the dynamics issues. I believe testing has shown a significant improvement.
Carl - SiRF Customer Support
|
|
|
|
IIB
8 Posts |
Posted - 23 nov. 2006 : 23:46:14
|
Hi Carl,
I'm sure you're the only one here with an answer to this one:
A friend and I (a couple of GPS receiver/system engineers since the late '70's) are using pseudo-range and carrier phases to determine the azimuth (relative to true North) of a line between 2 antennas input into a single receiver's carrier & code tracking loops. This of course takes ALLOT of complex post-processing of data.
I've got a Holux GPSlim 236 (S/W ver GSW3.1.1_3.1.00.07-C23B1.00), SiRF Demo 3.81, 2 MMCX connector patch antennas and SiRF Binary Protocol Reference Manual Ver 1.6, April 2005.
Q1. I realize from your previous posts that the carrier phase output in Test Mode 4 message #55 costs extra, but we were wondering if it would be possible to get a fairly accurate approximation of phase by interpolated differences of pseudo-range down to the delta range interval word in message #28? ... or something like that.
a) btw: how much would it cost to get carrier phase in message #55 and how would I go about it - new receiver?, SDK?, firmware flash?
b) btw: In "Test Mode 4" of SiRF demo 3.81, what does the "Period(s)" window selection and the "Use all 12 channels to track SV _ number window selection actually do?
The next is more of a question to Holux, but feel free :-)
1 antenna claims to draw only 6 ma at 3V with 26dB of gain and an unstated NF while the other claims 18ma at 3V with 32 dB of gain and a <1.5 dB NF.
Q2. I'm thinking about Y'ing the 2 antennas together as inputs to the receiver, but am wondering if the 3V load may be to much and burn out something in the receiver or the antenna gain may overload the front end. -- any ideas?
Thanks |
|
|
|
admin_0
1 Posts |
Posted - 04 déc. 2006 : 05:44:15
|
I am having a similar problem as whats described here but trying the suggested remedies did not seem to work, I am using the EM-406 module and a demo board provided by sparkfun.com, here is a list of the symptoms
*GPS originaly worked using hyperterminal 4800 baud, you would get the standard NMEA data out.
*I tried switching to the SiRF modes using the SirfDEMO software just to tinker and see what features it could offer.
*I get CE_Break and CE_Frame errors when I try connecting, I have tried several different baud settings all of which result in the same error.
*The GPS is still locking on a position(LED flashing) so I dont think anything is fried.
The supercap is drained...what is the best procedure for doing a factory reset since I can never seem to get the device to connect using the original settings that once worked (4800 baud) to do the "initialize device" command in the sirfdemo software.
Thanks,
John |
|
|
|
sprog
83 Posts |
Posted - 06 déc. 2006 : 05:58:55
|
Hi Carl@SiRF,
I recently came across this thread from a reply from my post in the Mionav forums. I recently purchased the Mio C310X that went on sale in the US. I had two versions of the unit, a 2GB unit and a 1GB with newer ROM. The newer 1GB unit seemed to never track below 3mph, and the older 2GB unit seemed to display random speeds when stationary (though usually always less than 1mph with good satellite reception, and position drift within a few feet).
After seeing your thread, 1.4m/s works out to about 3mph by my calculations. Can you confirm that the older 2GB units have SN disabled and the newer 1GB ones have it enabled?
Also, for pedestrian use, I don't really like how the 1GB unit doesn't track below 3mph (since I find that 3mph is just about the slow/fast walk threshhold), but for car use, I don't like how the 2GB unit is always tracking. Since the 2GB unit seems to report speeds below 1 to 1.5mph when still, and I normally walk faster than 1mph, I'd think a good SN threshhold would be around 1 to 1.5mph. Can the tools mentioned in this thread be used to adjust the SN threshhold, or can we only enable or disable it? Also, can the tool be used with USB, or do I need a USB-to-serial converter?
Thanks for the help. |
|
|
|
cavalierseul
3 Posts |
Posted - 15 déc. 2006 : 00:45:43
|
I have run into trouble trying to switch off "static navigation" on my E-TEN Glofiish X500 (on which "static navigation" is enabled by default). I've used SirfTech, and followed these steps:
- Click Comm
- Set Comm. 2 and 5760 Baud
- Click open
- Click OK
- Click NMEA – Switch to SIRF
- Click SIRF / 57600 Set
- Click OK
- Click SIRF – Static Navigation
- Click twice Static Navigation (That there is no mark anymore)
- Click Set
- Click OK
- Click SIRF / Switch to NMEA Protocol
- Click Set
- Click OK
- Click Comm
- Click close
- Click OK
- Click Exit
Everything went well until I tried to return from the Sirf to the NMEA protocol. In doing so, I think I changed the baud rate to 4800 - a stupid mistake, as a result of which my GPS receiver now recognizes neither protocol anymore. I suspect it just can't handle baud rate changes when switching between different protocols.
Anyway, while looking for a solution, I found some useful advice in this thread. Carl@SiRF writes:
"Removing the battery is the right way to try to get this back. If it doesn't work immediately, try shorting between the battery terminals after you remove the battery. There may be some capacitors holding up the voltage. It is also possible that the manufacturer put a 'SuperCap' (large capacitor on the order of 1 f) on the battery backup terminal that may take much longer to discharge, and which won't be affected by shorting the battery terminals since there is a regulator in between the battery and the SuperCap. In that case, time is the only way out. One other possibility is that the manufacturer may have put a small button-cell battery inside to hold the battery backup, and that would have to be removed to get things back to normal. But try these in order -- short between battery terminals, then wait a couple days, then finally open the unit up and look around for a backup battery."
I'd be happy to wait for, say, 2 or 3 days, but if the X500 has a backup battery, I might have to wait forever or send it back for repair. Does anyone have any information about whether the X500 has a backup battery? I've already asked the manufacturer, but I don't expect to hear from them as their support is notoriously poor. Any other advice on how to get the receiver working again would also be much appreciated. Thanks in advance. |
Edited by - cavalierseul on 15 déc. 2006 00:46:58 |
|
|
|
Topic |
|
|
|
| This page was generated in 3,78 seconds. |
 |
|
- 
- 
SiRFdemo tutorial (static navigation)
