| Versions |
  |
|
| Author |
 Topic  |
|
Carl@SiRF
USA
158 Posts |
 Posted - 09 août 2005 : 18:47:49
|
That first message -- port in use -- meant that SiRFDemo was not able to take over the serial port because some other application already had it. You probably still had your original application in use.
As to the other problem, I suspect that is due to one of the quirks of Windows. I am not an expert here, but SiRFDemo is only designed to use a single port, not a pair. As a result, it probably can display the data when it is attached to the input port, but doesn't know to use a different port for outgoing messages. We'll need to rely on some of the Windows experts out there to assist you.
Carl - SiRF Customer Support |
 |
|
|
acemtp
5 Posts |
Posted - 14 août 2005 : 23:07:37
|
| Do you know a tool that work on pocketpc arm on windows mobile 2003 that can enable/disable the STATIC NAVIGATION? |
|
|
|
gpspassion
93402 Posts |
|
|
olivierroy
France
6 Posts |
Posted - 23 août 2005 : 17:31:46
|
Hi everybody,
I have used SirfDemo with my G-Space GS-232 BT GPS device and I think I set the wrong baud rate or protocol.
The consequence is that I cannot "talk" to it with any of my laptop or PDA. I would like to reset it to factory settings but I do not know how to do it. I have remove the battery overnight but it did not work so I am trying a whole week without battery.
Can someone help ?
Thanks in advance
Olivier
Olivier |
|
|
|
Carl@SiRF
USA
158 Posts |
Posted - 23 août 2005 : 18:21:47
|
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.
Carl - SiRF Customer Support |
|
|
|
olivierroy
France
6 Posts |
Posted - 24 août 2005 : 11:34:05
|
Thank you Carl,
I tried shorting the battery already + 1 night without battery and the settings remained.
Now it's been 4 days after shorting and I plan to wait another week before I try again.
If the problem remains, before opeing it, I will return it to the manufacturer (I bought it 1 month ago) to have it reset.
Thank you very much for your assistance. I am not yet GPS addicted but during the 2 weeks I used it in the car, I found it very useful and accurate. When my device works again, I will investigate on the possibilities it brings.
Olivier |
|
|
|
fcyron
3 Posts |
Posted - 24 août 2005 : 17:51:21
|
Hi,
I run into some serios problems with my Haicom 303S Card while using SiRFDemo. I switched to SiRF Mode and now I'm not able to switch back to NMEA no matter what I try. NMEA/38000 Baud doesn't work. "Initalize Data Source"->Factory Settings doesn't work either. Any ideas ?
kind regards,
Falk |
|
|
|
fcyron
3 Posts |
Posted - 24 août 2005 : 18:07:08
|
Oh, I just saw the ongoing discussion. But just how do I get my 303S back to factory defaults? I mean, I'm not able to remove the battery from a CF-Device, or am I?
Kind regards,
Falk |
|
|
|
paulkbiba
USA
5064 Posts |
Posted - 24 août 2005 : 20:25:12
|
The only way to do it is to leave it alone, and unplugged, until the battery or capacitor runs down.
Moderator
Don't forget the GPSPassion Club! |
|
|
|
olivierroy
France
6 Posts |
Posted - 05 sept. 2005 : 16:27:57
|
Hi All,
Just to let you know that for my GPS device (GS R232) it finally worked. I removed the battery, shorted the 3 pins of the device (to unload a possible capacity) and I waited 10 days.
I put back the battery and it can now give a position to my PDA (the baud speed, protocol.... have been reinitialized).
I hope it will work for you as well.
Olivier |
|
|
|
telocat
45 Posts |
Posted - 06 sept. 2005 : 16:13:46
|
quote:
Originally posted by fcyron
Hi,
I run into some serios problems with my Haicom 303S Card while using SiRFDemo. I switched to SiRF Mode and now I'm not able to switch back to NMEA no matter what I try. NMEA/38000 Baud doesn't work. "Initalize Data Source"->Factory Settings doesn't work either. Any ideas ?
kind regards,
Falk
Hi Falk,
Can you tell me how you connected your 303S card to your computer to use SiRFDemo? I have a HI-305iii card that I'm trying out but cannot connect to SiRFDemo through a PCMCIA card. I know the PCMCIA setup works because I use my GPS on my laptop wit MS S&T.
I'm apparently able to connect to SiRFDemo in NMEA mode because the Debug window is very active with GPS data, but I never see information in the Map, Signal or any other window.
When I try to switch to SiRF protocol, I see COMM: CE_BREAK message
repeatedly in the ERROR view.
I've tried all initial baud rate settings with no success.
I'm starting to wonder if my problem is with connecting through the PCMCIA card because I've had this same problem with my other GPS, Fortuna Pocket XTrack.
Thanks.
HP iPAQ 2215, Fortuna PocketXTrack, Mapopolis v4.6 |
|
|
|
Carl@SiRF
USA
158 Posts |
Posted - 07 sept. 2005 : 03:36:38
|
If you see the COMM: CE_BREAK or CE_FRAME errors, you are seeing the data from the receiver, but your baud rate is not set right. Try each baud rate in turn and see if you always get that error indication. If at any time you don't get it, make sure your DEBUG VIEW window is open and you'll probably see NMEA data coming out. If all else fails, use the Action menu, Synchronize Protocol and Baud Rate option. That should send you to SiRF Binary at 57600 baud.
Carl - SiRF Customer Support |
|
|
|
db2boy
United Kingdom
4 Posts |
Posted - 07 sept. 2005 : 10:04:04
|
Carl,
As you mention I have tried every baud rate - only 4800 worked. It works find at 4800 and I see NMEA messages. Whatever I do or try I cannot get it to switch to SiRF mode. The Sync Protocol and Baud rate makes no difference. When I switch to 34800 I dont get the SiRF data showing but I sometimes get the menu allowing me to switch back to NMEA mode, if I try and change the config here it never sends the changes to the unit.
Rgds
Ant |
|
|
|
telocat
45 Posts |
Posted - 07 sept. 2005 : 16:13:02
|
quote:
Originally posted by Carl@SiRF
If you see the COMM: CE_BREAK or CE_FRAME errors, you are seeing the data from the receiver, but your baud rate is not set right. Try each baud rate in turn and see if you always get that error indication. If at any time you don't get it, make sure your DEBUG VIEW window is open and you'll probably see NMEA data coming out. If all else fails, use the Action menu, Synchronize Protocol and Baud Rate option. That should send you to SiRF Binary at 57600 baud.
Carl - SiRF Customer Support
Hi Carl,
I've tried all settings with the following results:
1200 baud: Comm: <continuous> CE_FRAME in Error View
2400 baud: Comm: <continuous> CE_FRAME in Error View
4800 baud: GOOD DATA IN DEBUG VIEW!!!!!
9600 baud: Comm: <continuous and alternating> CE_BREAK...CE_FRAME...etc in Error view
19200 baud: Comm: <continuous and alternating> CE_BREAK...CE_FRAME...etc in Error view
38400 baud: Comm: <continuous> CE_BREAK in error view
57600 baud: Comm: <continuous> CE_BREAK and some CE_OVERRUN in Error view
115200 baud: Comm: <continuous> CE_BREAK
I'm assuming all of this is in NMEA mode at this point. That would explain the good DEBUG data in 4800 baud mode and no good handshake in other baud rates. Also I read somewhere on this or another forum that Map, Signal, and other views don't work in SiRFDemo in NMEA mode, so no worries there.
NOW here are my results when switching from NMEA to SiRF Protocol in different baud rates: (each time I switch to SiRF Protocol, the menu bar ends up showing 38400 baud)
1200: Comm: <changes from> CE_FRAME to CE_BREAK
2400: Comm: <changes from> CE_FRAME to CE_BREAK
4800: Comm: <changes from> good DEBUG data to Comm: CE_BREAK
9600: Comm: <changes from> CE_BREAK/CE_FRAME to CE_BREAK
19200: Comm: <changes from> CE_BREAK/CE_FRAME to CE_BREAK
38400: Comm: CE_BREAK <no changes>
57600: Comm: CE_BREAK <no change>
115200: Comm: CE_BREAK <no change>
Also I've tried Synchronize Baud rate and protocol. I can see SiRFDemo switching between (scanning) all baud rates in the menu bar (two cycles) until it stops on 38400 and Comm: CE_BREAK in the Error View.
So I've tried all possible combinations. Can you recommend anything else that I should try? I'm reluctant to do a Factory reset on my new unit, but would this be recommended to see if it clears anything up? Should I start with a Cold Reset?
Thx.
: Trying this on a HI-305iii
HP iPAQ 2215, Fortuna PocketXTrack, Mapopolis v4.6 |
|
|
|
Carl@SiRF
USA
158 Posts |
Posted - 07 sept. 2005 : 23:05:40
|
What version of SiRFDemo do you have? Older ones switched to 38400 baud while newer ones switch to 57600 baud. Most of the current software always switches to 57600 baud when you change to SiRF binary, so that probably explains why things are going away for you. Part of the reason things are happening is that SiRFDemo makes assumptions and does things that aren't always obvious. For example, when you issue the "switch to SiRF binary" command, it sends the command then changes itself to 38400 baud (in your version). Sometimes if you do things manually it works better for you. So, get things back to 4800 baud (factory default, get there by pulling the battery etc. -- see this thread earlier), then manually enter the command to switch to SiRF binary. You do that by using the Transmit Serial Message option on the Action menu. Compose the NMEA command in the large window (PSRF100,0,57600,8,1,0), then select the NMEA radio button and Send. SiRFDemo will fill in the $ at the start of the message and the *[checksum]<CR><LF> at the end and send it. That command will tell the receiver to go to 57600 baud binary. So you should then see CE_BREAK or CE_FRAME errors in the Error View. Switch your baud rate to 57600 and reconnect and you should be in business.
Carl - SiRF Customer Support |
|
|
|
Topic |
|
|
|
| This page was generated in 1,45 seconds. |
 |
|
- 
- 
SiRFdemo tutorial (static navigation)
