Al,
The light pattern on the Hiper Pro is slightly different than other Hipers but it sounds like you are seeing the correct pattern. The radio port on a Hiper is C and the baud rate is typically 38400 though most radios support other baud rates. There is no advantage to using a higher baud rate. There are three separate baud rates that come into play on a Topcon receiver. The first is the controller to receiver baud rate, running Bluetooth, you are connected to the B port of the receiver at 115200, the radio board connects to the receiver board on port C at 38400. The radio broadcasts at a baud rate of 9600 or 19200.
Danny,
Thanks for your further explanation of the various baud rates involved. It is now clear to me why the baud rate must be set to 38400 in SurvCE. I appreciate your assistance.
Al
Hello all,
I have a similar problem as Big Al, but it's a little bit different!
I have a HiperPro GNSS receiver whit internal Satel SATELLINE-3AS radio modem. For data controller I use TDS Ranger 2 (Trimble TSC2) whit Carlson SurvCE 2.62 whit full functionality - so far, so good. In a Modem-tps software I set up the communication port to C and baud rate to 38400. The problem comes in a Carlson SurvCE, when I try to start the radio communication in the RTK module. So when I try to use Internal Statel, Satel 3AS or Satel Satelline and hit the software button in the right sight of the bar to set up the Protocol, Power, Channel and so on, the software connects with the modem and allows me to make changes but after that, when I hit the green button to save changes the software provides an error message Device returned NAK :-@ and doesn't save the changes I made. Of course after that the radio does not transmit or receive and I can't fix my solution. Does anybody have an idea what can I do!?
Thanks in advance and best regards!
I noticed that you're setting the baud rate to 38,400 bps in the modem-tps software. I believe I made this setting directly in SurvCE, not in the modem-tps software.
It's been a long while since I did it, but I think you can set the Hiper units to factory defaults using modem-tps. Maybe give that a try, and follow the steps outlined in this thread, focusing on the settings in SurvCE? There are several baud rates involved, one for the transceiver, another for the bluetooth, and if I remember correctly, a third which is internal to the receiver.
Good luck.
Al
OK guys I'm having trouble. I have topcon gr3 receivers, carlson serv ce2.0. It has been working fine. I got all set up boothtoothed everything up the other day everything hooked up fine communicating well with the base and rover, the data collector got turned off on the way to my next point, now It won't connect with either base or rover. I search bluetooth devices and nothing. I thought a com port issue, but I think I have hard reset everything. What do you guys think?
Thanks.
Sounds like a Bluetooth issue to me. Is Bluetooth on? Can you connect (does the DC see) other Bluetooth devices?
I have checked. The bluetooth see my rover inst. but it doesn't seem to see my base inst.
The base uses far more power than the rover, because it is transmitting corrections. Can you plug in to an external power source, or otherwise make sure that the batteries are fully charged on your base? Try connecting to the base using a laptop as a test to see if this is a DC issue or a Bluetooth issue?
Big Al,
I can get this thing to set the base using the cable connected from the inst. to the data collector. And the bluetooth seems to be connecting to the rover. But, its like the bluetooth is not connecting with the base.
If BT is working between DC and rover, then I think you can conclude that BT is operational on the DC and on the rover. However, sounds as if BT is not working on base. Could be a problem with the BT on the base. Could be a settings issue on the base or in the DC. Have you checked to confirm that BT settings for base are same as for rover in SurvCE? Can you connect a different BT device besides your DC to the base?
@@@@User 1234.
I have the same problem with my topcon hiper pro an Carlson survce. It show NACK not acknowledge and I cannot fix position
and the delay time shows 999.
Thanks
Simplest fix. Put on TRU (Topcon Receiver Utility) on your DC. Connect to the modem, and see what the radio type is on the first page. Then, go to settings and make sure that everything matches EXCEPT Setting the base as (radio type) transmitter, and rover as (radio type) receiver. GMSK, 38400 baud rate are recomended. Make sure those settings correspond in SurvCe, and you can reset the NVRam. If that doesn't work, might be a service issue.
Woah... Thread revived... I have the best solution throw them in the trash. I have three sets and I can't stand them working when they want to. They sit and collect dust in the corner.
I'm looking at getting some Hiper Pro's myself and have Carlson SurvCE v.4.07.3, does anyone know if I can connect to the pro's w/this version? I'm currently running a pair of Hiper Lites on them w/the internal spread spectrum radio.
The radio port in Topcon HiPer class receivers (and all other model families I am aware of) is always Port C for an internal radio modem. That is the only selection that works because that is the port an internal radio modem is always connected to.
Additionally, the expected baud rate of the radio modems in the HiPer+, HiPer Lite+, the HiPer Pro and the HiPer XT and the HiPer Ga/Gb units is 38,400.
If the modem in the HiPer Ga was upgraded to the Digital UHFII firmware, it will run at 115,200
hlbennettpls, post: 453170, member: 10049 wrote: I'm looking at getting some Hiper Pro's myself and have Carlson SurvCE v.4.07.3, does anyone know if I can connect to the pro's w/this version? I'm currently running a pair of Hiper Lites on them w/the internal spread spectrum radio.
I have SurvPC on my laptop at work and it lists several models of the HiPers but not the HiPer Pro. That should not be an issue if you set the RTK modem to Cable or Generic Device. This is true because the main difference in any of the versions of the HiPer receivers is what radio modem was installed and the stardard option set included in the OAF. The settings I describe expects the radios to be properly configured and is only going to send the correction information to the modem on the base or look for it from the modem on the rover.
What about some of the settings? I noticed the radio was set to 10mW. I thought these were supposed to be 1 watt. When I go to change them I get "the device returned NAK". Not sure what that means. Also noticed the squelch was set to medium. Any ideas on what the optimal settings are? I used them today & was able to get up to 1.8 miles from base before losing radio contact. The manual says 4 miles. I'm sure this is treestand dependant but I'm in pretty flat & fairly open territory. Any ideas?
Sent from my SM-G930P using Tapatalk