2 or 5 Hz Base Transmission

Matt Johnson

Well-Known Member
5PLS
I thought the danger of running the radio without an antenna connected was due to overheating as a result of the transmitter not having an outlet for the generated RF power. Does the update process engage the transmitter? I did an update without the antenna connected, and didn't notice any heating.

Jim you are correct that the danger is when the transmission does not have an outlet. Without an antenna I would image that the internal boards could overheat very rapidly before the enclosure gets hot. I always connect an antenna whenever I have the radio powered on to be safe. I checked to see what the manual said about this:

upload_2015-10-8_11-29-11.png
 

Matt Johnson

Well-Known Member
5PLS
The new versions of firmware for UHF radios (except TRIUMPH-1M internal UHF radio) are available here:

http://www.javad.com/jgnss/support/update.html

The issue with the call sign is fixed.

Also some improvement in handling of D8PSK and D16QAM modulations for transmitters is added.

Possibility to update radio firmware from J-FIELD is being added now, but this would take about 10 more days.

Please use ModemVU to update firmware for now.
 
Last edited:

Adam

Well-Known Member
5PLS
Matt, is the call sign issue fixed in this update or being fixed and will be in next update?
 

Jim Frame

Well-Known Member
I ran the update, but when I looked at the ID panel in ModemVU it still showed the old firmware revision number. I thought I might need to power-cycle the radio in order for it to display the new firmware rev, so I disconnected, closed ModemVU, power-cycled the radio, then launched ModemVU again. Now I can't connect to the radio.

I'm using the serial cable (25-pin to 9-pin), running ModemVU as admin, and using the same COM port (COM1) as before. ModemVU tries various baud rates, stepping down in speed from 115200 to 4800. I runs through the baud rates 3 or 4 times times -- which takes several minutes -- then tells me it "Can't find device." I've tried starting ModemVU then powering the radio, and the other way around.

Help, Mr. Wizard!
 

Matt Johnson

Well-Known Member
5PLS
I was able to successfully install it:

upload_2015-10-9_13-30-26.png


I always use Windows Device Manager to check what port I should be connecting to:

upload_2015-10-9_13-32-10.png
 

Adam

Well-Known Member
5PLS
Jim, I am curious if the update went thru okay for you. I was thinking I would see how it went for you before I tried it myself, I need mine to work tommorow, Please let me know when you are succesful and getting the 5 hz corrections. I think we are using the exact set-up.
 

Jim Frame

Well-Known Member
Jim, I am curious if the update went thru okay for you. I was thinking I would see how it went for you before I tried it myself, I need mine to work tommorow, Please let me know when you are succesful and getting the 5 hz corrections. I think we are using the exact set-up.
I haven't given it a field test yet, though a quick check in the office indicates that it's talking to the receivers via UHF and BT. I still haven't gotten ModemVU to connect again, but I haven't rebooted my computer yet, either. The COM connection failure is puzzling, though, because it worked fine when uploading the update, then failed when I tried to reconnect.
 

Jim Frame

Well-Known Member
The COM connection failure is puzzling, though, because it worked fine when uploading the update, then failed when I tried to reconnect.

Even more puzzling is the fact that I left the radio off for about 12 hours, and when I powered it up again and launched ModemVU, it connected. Go figure. I did verify that the firmware update was successful, though.
 

Jim Campi

Active Member
Jim, verify that another device is not using the same com port.

My LS and Nikon total station like the same port. There is probably a way around this however; when I connect my total station I must first disable the LS port communications in Windows Mobile on my PC.
 

Jim Frame

Well-Known Member
Jim, verify that another device is not using the same com port.

Although I have a number of devices that communicate via COM1, all use the same physical cable and 9-pin port on the motherboard. I do have an internal modem in the computer, but it's assigned to COM3.

The sequence of events in this instance was: connect the radio via ModemVU, upload new firmware, exit ModemVU, power-cycle radio, relaunch ModemVU, not able to connect. I didn't even unplug the serial cable, so no other devices had access to the physical port. Several attempts at connecting, which involved more power-cycling and ModemVU exit/launch, had the same effect. 12 hours later, the same sequence worked. Odd.

It occurs to me now that the one thing I did different on the final attempt was to first unplug the serial cable, then plug it in again. Is it possible that a capacitor in the radio kept a signal on the cable alive such that ModemVU thought the port was already in use? I don't know enough about serial communications or radio electronics to know if this is possible, but I do know that during the initial efforts to reconnect I didn't unplug the serial cable from the radio between attempts.
 

Adam

Well-Known Member
5PLS
You'll need ModemVU, available as a download from the main Javad site. Download the instructions, too (I don't remember if they're in the ModemVU zip file or not), and don't ignore the instruction to run ModemVU as Administrator -- I banged my head against that particular wall for about half an hour before finally paying attention.

You'll also need to download the latest firmware (though it sounds like you'll want to wait until they fix the shutoff bug first).

Once you get ModemVU talking to your radio, updating the firmware is pretty straightforward.
What is the com port # for the hpt35bt?
 
Top