USGlobalSat GPS Forums

Please login or register.

Login with username, password and session length
Advanced search  


Pages: [1] 2 3 ... 10
 on: Today at 04:45:42 pm 
Started by sausalitosailor - Last post by USG_Tech12
We've currently finished our testing of the Mac OS 10.10 (Yosemite) and our latest 10.6 OSX USB to Serial drivers. The tested drivers have been added to our driver link on our website here:

The testing has validated that the drivers are working properly on the latest Mac 10.10 (Yosemite) update.

Note: Click on the link under the picture to view in a larger format,


 on: October 20, 2014, 10:42:13 pm 
Started by Dmac - Last post by Dmac
I downloaded my hike into google map and noticed a big difference between the watch reading on cumulative altitude and that in the google map. My hike yesterday registered 937 metres in the watch but in google maps it was only 342 in elevation gain/loss. Something I did not do correct? Is the watch correct or that in google map? However the distance was about the same at 5.2 km.
Any help?

 on: October 17, 2014, 01:43:42 pm 
Started by sausalitosailor - Last post by sausalitosailor
Thanks for welcoming me onto the board.

I performed a clean install of OS 10.10 on a MacBookPro last night with no issues. 

The USB BU-353S4 is no longer visible in the system report and the only options when running the GPS utility are Bluetooth.  The LED status lights do not illuminate. 
I have removed prolificusbserial and re-installed PL2303_1.5.1_20130822

Thanks for looking into this.

// John

 on: October 16, 2014, 06:13:27 pm 
Started by USG_Tech12 - Last post by USG_Tech12
1.) Q: Is this device WAAS enable?
1.) A: Yes…

2.) Q: What datum is used?
2.) A: WGS 84

3.) Q: Is this device waterproof?
3.) A: Yes.

4.) Q: What's the refresh rate?
4.) A: GGA(1sec), GSA(5sec), GSV(5sec), RMC(1sec),VTG(1sec)

5.) Q: How many satellites are needed for 3-D positioning?
5.) A: A minimum of 4 satellites.

6.) Q: Can I reconfigure receiver? If so, what program?
6.) A: Yes, SirfDemo programming utility.

7.) Q: Can I reconfigure receiver's Baud-Rate? If so, what program?
7.) A: Yes, SirfDemo programming utility.

8.) Q: Can I reconfigure receiver's NMEA data? If so, what program?
8.) A: Yes. SirfDemo programming utility.

9.) Q: What platforms are supported?
9.) A: Windows/ Pocket PC/ Mac OS X/ Linux

10.) Q: Once set. Is SiRF Binary Protocol a permanent configuration?
10.) A: These settings are temporary until the receiver's internal Super-Cap back-up power supply. Then the receiver will revert back to its original default settings.

11.) Q: Does the current USB driver support Mac OS X Tiger?
11.) A: Yes it does…

12.) Q: How does the "20 channel" affect performance? Both: MR350 and BT-338 have "20 channel" in the specs.
12.) A: The sensitivity numbers like the TTFF numbers don't really mean much either as they're hard to tie into real life observations.

13.) Q: How much more is the SiRF Star IV power consumption compare to SiRF Star IV/LP?
13.) A: About 15% more power hungry than SiRF Star IIe/LP it seems then.

14.) Q: Is SiRF Star IV quicker in signal acquisition?
14.) A: Yes, SiRFStarIV can acquire much faster than IIe/XT2 in difficult environments thanks to the added correlating power and that is not reflected in the dB number.

15.) Q: Can I disable the auto-off feature?
15.) A: Unfortunately, it’s a standard programmed feature to conserve battery energy. Therefore, to disable this feature(s) only OEM requests will be taken into consideration.

16.) Q: How much accuracy is comprised without utilizing WAAS?
16.) A: Since Selective Availability (SA) was removed in May 2000, the residual GPS error of approximately 10 meters is mostly due to GPS signal deflection that the SBAS system can only marginally correct (I have never been able to measure any improvement from EGNOS but others have seen 1/2 meters with WAAS). On the other hand SBAS is crucial for critical use such as flying a plane as it allows for near real time GPS signal integrity checking.

17.) Q: What is the biggest benefit of the SiRF Star III chipset?
17.) A: Correlation power, the action of analyzing the signal received from the satellites and making sense out of it to compute a position. Sounds simple enough, but the signals are very weak (sent from 20,000 kms above our heads) and generally very degraded by our immediate environment, so the more correlation power you have the better your chances are of getting a "fix". In addition, TTFF is less dependent on the environment and once you get a lock you rarely lose it, even indoors. With SiRFIII, GPS requires less "work", for instance, you no longer need to choose between waiting 2 minutes when you leave a parking garage in the morning to get a fix or risk driving around for 10 minutes without one, now you'll generally get a fix in 45 seconds in both situations .

18.) Q: Will my receiver support older NMEA standards?
18.) A: Yes, NMEA 2.0 is backwards compatible with older versions of the protocol. NOTE: If your map software (such as Street Atlas 5) requires data
sentence GGA, and your GPS (such as the Magellan 3000) does not
output GGA, then they will NOT work together.

19.) Q: What to look for first to know which SiRF firmware version is oldest/newest?
19.) A: Here's a little insight into SiRF version numbers: 2.3.2-GSW2-2.05.024-C1PROD1.0_6A -- the GSW2 means standard SiRFStar II software, and 2.3.2 is the release version number. The 2.05.024 or similar numbers are internal numbers into the engineering data base. C1 is the build variant, a number that varies with each software type, but can relate to flash builds vs. RAM (debug) builds, builds with or without SBAS support (WAAS), builds with one or two serial port support, NMEA or binary protocol default, etc. Prod means this is a released rather than a beta (test) version. 1.00 means the release is without any post-release bug fixes. If there is a letter or letters after the Prod1.00, like Prod1.02b, this would mean that some specific "patches" have been added to provide interim fixes for known bugs. After that, anything on the line is likely added by the manufacturer for internal version control. A number like 0000003729 with XMitac2.0 means this is XTrac 2.0 customized by SiRF for Mitac. In general, an X in the number will imply XTrac software, while GSW2 or GSW3 will indicate standard code for SiRFStar II or SiRFStar III, respectively.

20.) Q: Can we upgrade our SiRF firmware? What' s needed for the process?
20.) A: SiRF provides the new versions to our direct customers, but it is up to them to determine if they want to provide an update mechanism to their end-user customers. While the process is relatively simple, unless there is a hardware way to put the receiver into flash upgrade mode (internal boot mode is our term) there is a chance to get things stuck so you have to send it back to the manufacturer or a repair depot to recover. Further, you must be supplied with a flash programming utility to do the job since you cannot access the flash directly -- you have to go through the ARM processor on the SiRF chipset."

21.) Q: What is the meaning of "baud rate"?
21.) A: Baud rate is really the rate of bit transitions on the serial data link. Since each byte of data adds a start and stop bit, it is 10 bits long, and 38400 baud is 3840 bytes per second. Faster bit rates transfer more bytes per second, i.e., greater bandwidth.

23.) Q: What is static navigation?
23.) A: Static navigation when enable, velocities lower than 1.2 m/s for 3 seconds we will freeze the position, and leave them frozen until velocity exceeds 1.4 m/s. Static navigation is a mode designed for motor vehicles, which causes the position to become pinned at one location when velocity is determined to be low enough. This is designed to make navigation systems operate more reasonably when the GPS Selective Availability (SA) signal degradation is turned on.

24.) Q: What is trickle mode?
24. )A: The Trickle mode allows for an increase in battery life by putting the GPS module in sleep mode for very short periods of time, such as 300ms per 1s cycle, which will result in a battery life increase of about 40% according to my testing. It can be useful for certain types of applications but there is a hit on performance as the receiver will have to get "back on its feet" when it wakes up. It is especially problematic in difficult reception conditions. Starting with FW 2.3, SiRF has added the "Adaptive Trickle" mode, which as its name implies will adapt the power savings to the conditions of reception. In optimal conditions, I found that the battery life increase amounts to about 30%.

25.) Q: How can I find whether my device is an X-Trac or STD model?
25.) A: There are several ways to check whether the device is X-Trac or not: 1. Serial number is X....., it's X-Trac 2. The bottom sticker with Red dot, it's X-Trac 3. Use GPSinfo to cold start the device, it shows Xtrac after $Version, it's X-Trac.

26.) Q: Are the ZDA's 1 second apart, so they are within  a small ms tolerance from each other (1 second apart).
26.) A: ZDA output is according to firmware settings, the supplier cannot provide the time error, it is possible that error might be over 400 ms.

27.) Q: Will ZDA's fail to come out?
27.) A:If the firmware is set to output ZDA, in theory ZDA will output.

28.) Q: Will a ZDA come out after the wrong PPS?  For example: A PPS is sent describing time 10, but the next ZDA is sent with time 9 information?
28.) A: ZDA and PPS do not have an absolute relationship, basically PPS will happen first, then ZDA output.

29.) Q:Consider this:  A PPS signal is set, a ZDA comes out 500ms after.  Then the sequence continues within a small tolerance.  Is this information available?
29:) A:ZDA and PPS do not have an absolute relationship.

 on: October 10, 2014, 01:27:41 pm 
Started by USG_Tech12 - Last post by USG_Tech12
Hello All,

We've currently added the ND-105C to our device registration list and also to our website.

You can now register your new ND-105C our support page here:

So now if needed you can start a support ticket on your newly purchased ND-105C.

Thank you.

 on: September 19, 2014, 09:25:45 am 
Started by MisterMagoo - Last post by jale
Well, I will try to wash it properly (I'm very bad at this).

Also, last trip I had, I adjusted the strap so it was very tight around my chest, and I had good readings for about an hour. The battery is almost new, so I don't think that's the issue right now.

Going for a trip now, and will clean the band properly.

I also have a Samsung galaxy S5, with an inbuilt ANT+ receiver, but the custom ROM (operating system) I'm using doesn't support ANT+ yet, but it will soon. Then I want to try it with the phone as well.

Well, just finished 1h 10m trip. Not once did the HR sensor show 240bpm, so it seems like it helped a lot to wash the band. For now the issue is resolved.

 on: September 18, 2014, 12:50:32 pm 
Started by USG_Tech12 - Last post by USG_Tech12
USGlobalSat has released the new ND-105C to Amazon. ND-105C features high GPS sensitivity, Micro USB interface, low power consumption and ultra small form factor. This product is powered by MTK GPS solution; it can provide you with superior sensitivity and performance even in urban canyon and dense foliage environment.

ND-105C supports up to 210 PRN channels. With 66 search channels and 22 simultaneous tracking channels, ND-105C acquires and tracks satellites in the shortest time even at indoor signal levels. Through ND-105C's excellent low-power consumption characteristic, while using power sensitive devices, especially portable applications.

ND-105C has a simple ID design is suitable for the following device accessory:Android 4.0 and above -Smart Phone -Tablet PC -Portable device.

Includes a Micro USB to USB connector allowing easy connectability with tablets, Laptops and PC.

It comes compatible with all major Windows versions including Windows 8 & 8.1 and above. Along with Mac OSX 10.0 and above.

Here is the link to Amazon where you can find it for yourself: 

We look forward to hearing your reviews on this product. 

 on: September 17, 2014, 03:04:33 pm 
Started by MisterMagoo - Last post by albert
I am using the sensors from the GB580 on a Garmin 810, they work fine except if the HR strip is not cleaned with water and soap or if the battery is not strong enough. Sometimes a battery looks OK but if you put load on it, it fails. On that you can easy get high readings and it won't come down. I am not saying this is the case in your situation, but have another look.

 on: September 16, 2014, 01:25:23 pm 
Started by USG_Tech12 - Last post by USG_Tech12
Recently we had a customer find a solution to pairing their Bluetooth device with their Nook tablet.

They found if they rooted their Nook to version Android 4.3.1 they could then enable "developer mode" in order to enable "mock locations" on the android rooted Nook.

They found that the basic Nook OS wasn't able to support an external GPS so they found their own solution to issue.

This is just an FYI for any other customers that are trying to pair a Bluetooth device with their own Nook device.

Thank you again to the customer that shared their solution to a problem they were having. Thank you!

 on: September 14, 2014, 10:11:11 am 
Started by MisterMagoo - Last post by jale
Want to bump this thread, as I have the same issue as MisterMagoo.

I'm on latest firmware (F-GGB-2O-1407041 from July 24th 2014).

Only using cadence and HR sensors (both the original that came with the GB-580).

I only have problem with the HR sensor. It spikes to 240 after maybe 25-30 minutes of use, and then stays at 240 for the rest of the workout. Sometimes it goes back to normal, but not for long.
I have changed the battery in the sensor, and re-paired it with the GB580 (turned HR off, then scanned for it again).

I imported the workout in SportTracks, and this is the graph of the HR. I highly doubt that I ever was above 190bpm. Also plotted cadence, so that you can see that this sensor is always working.
As the cadence sensor is working, I guess that it is the HR sensor that is messing up.

I also have the .gpx file (or any other file-type of the workout) if this will help.

Pages: [1] 2 3 ... 10

Page created in 0.189 seconds with 16 queries.