I am attempting to update a few R8 2s to supplement our static fleet. TIM won't connect. Anyone know of an alternative digital hammer?
I believe you need to use winflash for the R8's.?ÿ?ÿ
I second winflash. ?ÿAnd it can be finicky getting it to connect sometimes. I would often have to do a good reboot on receiver to get it to work . It has been a while but hold power key on when receiver is off. Wait till all lights flash keep holding they will go off and keep holding and at some point they all come on solid then release.?ÿ
i am trying to remember the best baud rate and settings. ?ÿOnce you get it working. Hook up the receiver once i. A while and clear the error log files it always kept me from having issues that many seemed to have with everyday work. ?ÿLike Bluetooth and i initialization ?ÿtimes etc . ?ÿOnce a month I would check mine if not weekly when downloading static data. Hope this helps.?ÿ
Thanks for the tips. The units all hook to the old TSC2 fine. I cannot get them to hook to the computer or Trimble DL. I'll be fiddling with them a bit this afternoon...
I didn't have any luck with winflash but I was able to connect with Bluetooth to the web interface on my R8-4 to upgrade the firmware.?ÿ I watched a YouTube video and followed the instructions to install a Bluetooth modem connection in windows and dial in to the R8. there were a few steps but it worked nicely
@sean-r-m That may be the trick. My newer devices puke fairly fast. The units do track Anerican and Russian sats fine and download through the TSC. I prefer to use a phone for convenience.
Thanks again, Tom
So I cleared a few errors from my brain and was able to recover limited memory. I uninstalled the default drivers for the usb cable and ran tge trimble usb utility. All receivers hook up to winflash flawless. We went from two to seven working R8s in a matter of hours.
The big lesson is to look for myself when units are considered dead. One was tagged as bad bluetooth but the BT FW was version 1.0 1. We had just paid to have it cleaned and updated. The error codes I just found went back to 2018. Bluetooth is flawless now. I never should have stopped doing my own maintenance...