Triumph2/TriumphLS/HPT435

Kelly Bellis

ME PLS 2099
5PLS
Do the red items in the base config box mean they didn't get sent to the radio? I had the power set at 400mW in the UHF config screen.
Yes, that is my understanding. In the case of the ID, the number you've chosen is outside of the industry I defined range for RTCM 3.x

In regards to the output power display, from my last tests earlier this month, these values were still not reflective of the output power from the base's modem.
 

Matt Johnson

Well-Known Member
5PLS
Is the 2D delta showing a valid distance?
I have been able to transmit a position and receive corrections when the base coordinate is more than 50 miles away from its actual position. I don't think there is anything that prevents corrections from being sent and received when the 2D Delta is high.

Do the red items in the base config box mean they didn't get sent to the radio? I had the power set at 400mW in the UHF config screen.
Yes in this case they do. Your problem is that you selected a Base ID that is not valid for RTCM 3.0. This is why it is not working. From page 119 in the manual:


upload_2014-12-14_9-19-48.png


If the BT and RX light are flashing, the radio was paired and it is not a problem with the Bluetooth connection.

I have requested that Base ID be modified to accept only valid entries.
 
Last edited:

Shawn Billings

Shawn Billings
5PLS
I agree. Flashing Tx light indicates the base and modem are connected. Current alpha versions are reporting output power reliably.
 

Jim Frame

Well-Known Member
That's why I broached this, Jim. It is not the case from my experience and from what I've been told. The user must manually unpair the previously paired radio before pairing the new radio all done using NetView.
When I connect my T2 and HPT401BT up and run NetView, and hit the External Modem via Bluetooth button, I get this:

Modem Unpair 1.jpg


Doesn't this indicate that this modem is already unpaired?
 

Jim Frame

Well-Known Member
[QUOTE="Matt Johnson, post: 4340, member: 10"Your problem is that you selected a Base ID that is not valid for RTCM 3.0. [/QUOTE]

Okay, I deserve a dope-slap for that one, because I've run into it before and just forgot when I set up the new radio. (5435 is my LS number, so I figured that'd be a logical base ID number.)

I changed the base ID to a legit setting, stopped the base and disconnected from the T2. I then reconnected to the T2, hit To Base, then Start Base, but still no joy. (Note that the output power indicator is still red.)

temp.jpg


When I go to the UHF status screen, I see this:

temp.jpg
 

Matt Johnson

Well-Known Member
5PLS
The red value for the output power indicates this setting is not being applied correctly. What happens if you press From Base? What power output is displayed? You could also connect the radio to ModemVU to check the power output.

My suspicion is that it is still outputting 35 watts and you are not receiving corrections because you are too close. Also try other output powers and see if any of them aren't red after you press To Base.
 

Shawn Billings

Shawn Billings
5PLS
Just to be clear did you power off the UHF in the Triumph LS and power it back up again? It's in configuration in the UHF status screen.
 

Matthew D. Sibole

Well-Known Member
5PLS
Doug Carter had a similar issue. I walked him through the setup and he had everything set up correctly. The only difference between when I walked him through it and when he did it was he walked away from the base and radio. Once he walked away from the base and radio it started working. No rhyme or reason that we could think of. It just worked.
 

Matt Johnson

Well-Known Member
5PLS
Shawn do you know if there is any danger of damaging the UHF board in the LS if they radio is outputting 35 watts and the LS is too close?
 

Jim Frame

Well-Known Member
My suspicion is that it is still outputting 35 watts and you are not receiving corrections because you are too close. Also try other output powers and see if any of them aren't red after you press To Base.
It seems to be correctly set at 400mW (0.400W).

MODEMVU4.jpg


I'll try walking away with the T-LS and seeing if that makes a difference. I'll also turn UHF off and on again, though I'm pretty sure I did this before. (Plus I've power-cycled everything multiple times in this effort.)
 

Matt Johnson

Well-Known Member
5PLS
I just noticed that your screenshot of the UHF status pages shows "err, ?ERR?" for the UHF State. Have you tried doing a hard restart of the LS by holding the On/Off button down?
 

Jim Frame

Well-Known Member
Getting closer now. Walking the T-LS away from the transmitter made the difference, I started getting an OK on both the transmit and receive side of the radio box above the base config box, and the UHF config screen started showing everything good except for received/lost stats. I'm getting long receive delays, but I think that's because the T2 is sitting on a windowsill in my office, with only a little sliver of sky visible.
 

Jim Frame

Well-Known Member
Jim - Did you ever get an answer to this question? And did you overtly unpair your 401-T2 pairing?
As to the larger question -- getting the HPT435BT to work with my system -- I'll give it a definitive test today in the field if the weather permits. Regarding actively unpairing one radio before pairing another, my conclusion is that pairing a radio via NetView effectively unpairs any other radios that may have been paired with the receiver. After I did the NetView pairing of the HPT435BT, I tried to unpair the the HPT401BT and was unsuccessful, presumably because it had already been unpaired.
 

Matt Johnson

Well-Known Member
5PLS
Are you keeping the 401? If so we believe you can use both and have them both paired by asigning them both the same Bluetooth address with the radio configuration utility.
 

Jim Frame

Well-Known Member
Update: In the field today (fortunately, with no client watching) I went through a similar hair-pulling exercise trying to get everything working. The T2 and the radio appeared to be talking, but To Base wasn't working, as evidenced by the radio call sign change not getting to the radio (i.e. make changes, press To Base, wait for completion, press From Base and see that the changes didn't stick). After an hour or so of getting nowhere I finally called Shawn, and a combination of his Texas drawl and a hard reset on the T-LS made everything sing. Soon I was reaching out 4 miles and hitting points in my network within a few hundredths H and a tenth or less V.

Well, almost. When I staked out the network points I was actually missing them by over 4 feet horizontally. I figured it was a datum issue, but I was tired of not getting anything done and I didn't have to do any stakeout, so I just kept going. When I got back to the office, I saw that the base point broadcasting reference frame was set to WGS84, while my network is NAD83(2011). I know I had set the base point frame to NAD83 at some point, but I guess in all the setup iterations it had reverted somehow. (I'll have to keep an eye on that in the future.) The gfile export allowed me to fix it all in Star*Net, so no loss.

P.S. It looks like the T2 or J-Field isn't able to read the power output setting of the HPT435BT, because the T-LS never did show anything more than "---mW" in the display, even when I was getting corrections.
 
Top