And for those of you following along at home, here's how to use my crummy technique to temporarily fix your 4000SSe/SSi:
Download the firmware update package from Trimble, and from a DOS prompt run this:
loader.exe -M
4000SE/SSE/SSi & 7400MSi REMOTE MONITOR, V4.32
Initializing COM1
Finding receiver baud setting. Trying: 38400 baud, odd parity
Establishing link at 38400 baud, odd parity
PPU Version = 3.34
Receiver type=05
Link established. Defaulting to 9600 baud, no parity
SE/SSE/SSi H/W target receiver detected.
enter command: d 1cace 1 08
download data to target memory
starting address:byte count:Byte[0]:
enter command: d 3fe 2 c0 de
download data to target memory
starting address:byte count:Byte[0]:Byte[1]:
enter command: r
Wait for the receive to reboot, once it gets a satellite fix it will have the correct time.
If the receiver is rebooted again, it will warn that it found an error in the firmware, then correct the "error".
Okay, so that was easier than I thought. Details coming soon, but in the meantime, the Trimble 4000 Version 7.32 firmware corrected for WNRO until 2038ish is available here:
there?ÿ is bit that will rechecksum the whole firmware for you 🙂
@robots I saw it in there, but I couldn't figure out how to trigger it. I ended up just writing a piece of code to recalculate the checksum from the .X image.
@robots Awesome, that means the WRNO bug can be fixed from the monitor without having to completely reload the firmware. Thanks for this.
@keelan it could , but its easier for people to upload complete firmware. Less error prone.
I 'm interested,
I may need your hand with that...?ÿ
Have you already found the solution for the trimble 4000 rollover?
