Jim Frame, post: 358999, member: 10 wrote: Some interesting information from the teqc documentation:
This begs a question for John H: what does your FixWeek application use to determine the correct week number?
That is correct. An observation record has only GPS seconds of the week. The processing program must get the actual week number from somewhere else. As i mentioned, it is present in several places. If you were to have a dat file consisting of nothing but observation records, it would be unusable. I have a program that scans a dat file and lists the records. Here are the first 30 records, 17 is the actual observation record...
[pre]RECORD TYPE:05 SUBTYPE: 6 LENGTH: 24 FILE OFFSET: 1 Hex:1
RECORD TYPE:05 SUBTYPE: 0 LENGTH: 98 FILE OFFSET: 25 Hex:19
RECORD TYPE:05 SUBTYPE: 1 LENGTH: 65 FILE OFFSET: 123 Hex:7B
RECORD TYPE:05 SUBTYPE: 2 LENGTH: 64 FILE OFFSET: 188 Hex:BC
RECORD TYPE:05 SUBTYPE: 3 LENGTH:110 FILE OFFSET: 252 Hex:FC
RECORD TYPE:15 LENGTH:124 FILE OFFSET: 362 Hex:16A
RECORD TYPE:16 SUBTYPE:199 LENGTH: 17 FILE OFFSET: 486 Hex:1E6
RECORD TYPE:16 SUBTYPE:199 LENGTH: 15 FILE OFFSET: 503 Hex:1F7
RECORD TYPE:19 SUBTYPE: 5 LENGTH: 14 FILE OFFSET: 518 Hex:206
RECORD TYPE:16 SUBTYPE:199 LENGTH: 19 FILE OFFSET: 532 Hex:214
RECORD TYPE:16 SUBTYPE:124 LENGTH: 6 FILE OFFSET: 551 Hex:227
RECORD TYPE:16 SUBTYPE:124 LENGTH: 6 FILE OFFSET: 557 Hex:22D
RECORD TYPE:21 LENGTH:190 FILE OFFSET: 563 Hex:233
RECORD TYPE:21 LENGTH:190 FILE OFFSET: 753 Hex:2F1
RECORD TYPE:21 LENGTH:190 FILE OFFSET: 943 Hex:3AF
RECORD TYPE:21 LENGTH:190 FILE OFFSET: 1133 Hex:46D
RECORD TYPE:12 LENGTH: 68 FILE OFFSET: 1323 Hex:52B
RECORD TYPE:16 SUBTYPE: 27 LENGTH: 20 FILE OFFSET: 1391 Hex:56F
RECORD TYPE:16 SUBTYPE:199 LENGTH: 24 FILE OFFSET: 1411 Hex:583
RECORD TYPE:16 SUBTYPE:199 LENGTH: 23 FILE OFFSET: 1435 Hex:59B
RECORD TYPE:16 SUBTYPE: 43 LENGTH: 13 FILE OFFSET: 1458 Hex:5B2
RECORD TYPE:11 LENGTH: 92 FILE OFFSET: 1471 Hex:5BF
RECORD TYPE:16 SUBTYPE: 3 LENGTH: 87 FILE OFFSET: 1563 Hex:61B
RECORD TYPE:17 LENGTH: 53 FILE OFFSET: 1650 Hex:672
RECORD TYPE:21 LENGTH:190 FILE OFFSET: 1959 Hex:7A7
RECORD TYPE:21 LENGTH:190 FILE OFFSET: 2149 Hex:865
RECORD TYPE:17 LENGTH:197 FILE OFFSET: 2339 Hex:923
RECORD TYPE:17 LENGTH:197 FILE OFFSET: 2792 Hex:AE8
RECORD TYPE:17 LENGTH:197 FILE OFFSET: 3245 Hex:CAD
RECORD TYPE:17 LENGTH:197 FILE OFFSET: 3698 Hex:E72
[/pre]
As you can see, there are a lot of records before the first observation that have things like point number, HI, antenna info, receiver info, ephemeris, ion/utc, etc. After the observations start there are a few times where records are inserted, like position, ephemeris updates, etc.
There is a week number in the file, which currently corresponds to June 1996. My program simply adds 1024 to the week number in the "bad" dat file. I think that after another week rollover in April of 2019 I will have to update the program to add 2048. Please remind me then.
Thanks John, you're a good egg.
I started to install John's program on my XP machine where I have the other tools for working with an old Trimble receiver, and it wanted to update some system files. Is that safe for all versions of Windows, or only for a particular one?
Bill93, post: 359027, member: 87 wrote: I started to install John's program on my XP machine where I have the other tools for working with an old Trimble receiver, and it wanted to update some system files. Is that safe for all versions of Windows, or only for a particular one?
I believe it should be fine, there are some controls (list boxes, etc) that are probably newer versions than what is on XP. I do have an XP box running at home, but I am in CO and it has probably already been updated. If I get a chance later on i will try it.
Uncorrected RINEX
96 7 7 12 47 15.0000000 0 4G05G07G13G30 -0.000132837
21408411.93817 -1608.90617 70668.05217 34067.94659 21408408.36359
48.000 44.000
21399796.79717 -3058.46917 125101.22617 68675.47159 21399792.59459
49.500 42.500
22337363.32817 1790.21917 -74348.25517 -46678.30658 22337359.93458
50.000 36.000
20250430.43017 -1626.15617 68099.73617 34577.15159 20250428.14859
52.000 45.250
Corrected RINEX
16 2 21 12 47 15.0000000 0 4G05G07G13G30 -0.000132837
21408411.93817 -1608.90617 70668.05217 34067.94659 21408408.36359
48.000 44.000
21399796.79717 -3058.46917 125101.22617 68675.47159 21399792.59459
49.500 42.500
22337363.32817 1790.21917 -74348.25517 -46678.30658 22337359.93458
50.000 36.000
20250430.43017 -1626.15617 68099.73617 34577.15159 20250428.14859
52.000 45.250
Just one for the header
1996 7 7 12 47 15.0000000 GPS TIME OF FIRST OBS
1996 7 7 13 54 35.0000000 GPS TIME OF LAST OBS
into
2016 2 21 12 47 15.0000000 GPS TIME OF FIRST OBS
2016 2 21 13 54 35.0000000 GPS TIME OF LAST OBS
96 7 7 12 47 15.0000000 -> 16 2 21 12 47 15.0000000 (for al records)
Is this the only transformation?
I'll build a function to read info from file .... transform timestamp into seconds ... add the (1024*7*24*3600) ... reverse seconds to timestamp ... write to file
GEO_XXL
I think you have to check also the navigation file ...
from my RinexDates doc.
Christof.
As far as the 5700 receivers, does anyone know if the firmware can be updated to solve this problem? I've been scouring the house looking for the CD that came with the unit when I purchased it second hand. I haven't been able to find it, but I'm not sure if the firmware update procedure should even require the disc. Any help?
According to Trimble's website, the latest firmware for the 5700 (same as R7?) is v5.00 dated March 2015. Whether or not it addresses the GPS week issue, I don't know. It also appears to require a firmware support agreement dated May 2014 or later. See this page for details.
Jim Frame, post: 359151, member: 10 wrote: According to Trimble's website, the latest firmware for the 5700 (same as R7?) is v5.00 dated March 2015. Whether or not it addresses the GPS week issue, I don't know. It also appears to require a firmware support agreement dated May 2014 or later. See this page for details.
Jim,
That's not for 5700's. The last version for 5700's and the only one which doesn't have this issue is 2.32. Requires a firmware support date of Dec 2004. I think you can check this using winflash.
There's a list of all firmware versions for current and end of life gear at this Trimble link. 5700's are on Page 3
Jim Frame, post: 359151, member: 10 wrote: According to Trimble's website, the latest firmware for the 5700 (same as R7?) is v5.00 dated March 2015. Whether or not it addresses the GPS week issue, I don't know. It also appears to require a firmware support agreement dated May 2014 or later. See this page for details.
The 5700 is not supported in that version 5.00. I think the most current is 4.01, but I could be wrong. I have one 5700, I did not think to check it. We rarely use it, sometimes it does not recognize the flash card.
In The Sandpit, post: 359167, member: 99 wrote: That's not for 5700's. The last version for 5700's and the only one which doesn't have this issue is 2.32.
I found that reference on the UNAVCO site, so I guess that needs to be updated.
So if it says this on my registration page that means I need a new receiver?
Hardware Warranty Expiry Date: Friday, June 27, 2003
Firmware Warranty Expiry Date: Friday, September 27, 2002
Software Maintenance Expiry Date: Friday, September 27, 2002
Dan Patterson, post: 359184, member: 1179 wrote: So if it says this on my registration page that means I need a new receiver?
Hardware Warranty Expiry Date: Friday, June 27, 2003
Firmware Warranty Expiry Date: Friday, September 27, 2002
Software Maintenance Expiry Date: Friday, September 27, 2002
I don't have a 5700 but if you download into a data logger like the TSC-2 the current date in the data logger may eliminate the problem.
MISSOURIMULE, post: 359225, member: 9473 wrote: I don't have a 5700 but if you download into a data logger like the TSC-2 the current date in the data logger may eliminate the problem.
I have a recon that I never use, but I think it only has the Total station functions on it.
Just ordered a CHC X-90 OPUS from iGage. I just need something very simple to run OPUS & OPUS-RS as network RTN checks
Dan Patterson, post: 359294, member: 1179 wrote: Just ordered a CHC X-90 OPUS from iGage. I just need something very simple to run OPUS & OPUS-RS as network RTN checks
Congratulations. You will be pleased. Mine is still making me money two years later.
The last R8 from Trimble is better
I do not know what kind of agreement they have with Trimble regarding technical support for the MOBO. Anyone read EULA????
