v2.2 has this bug which I’ve confirmed also manifests through the User Profile’s menu via serial config. If you’re doing anything with profiles on a Torch, it will fail communication with the GNSS receiver and everything goes downhill from there. If you’re using only one profile, all should be fine.
We need to get you onto d2.3. Can you attempt to load the attached binary onto your Torch via the GUI uploader and let us know how it goes?
OK d2.3 installed, I can login via web config, I switched from AP to WiFi and I can access it, I created 5 Profiles, 4 without any data Profile 2, Profile 3, Profile 4 and Profile 8, whereas Profile 1 has my wifi info.
The only thing I lost was the Beep, I tried resetting it in the serial connection and I tried in web config but sadly no beep.
And while selecting the HAS/E6 the PPP field is blank and the program insists on data in this field, luckily it show what is the default, but it must be typed in every time a change is made in web config.
I tried this on my rover unit, not my base.
Mike
I can’t select a different profile in web config.
Now LoRa radio failed to enter command mode, I see,
AT+V?
+++
No command mode
AT+V?
+++
No command mode
LoRa radio failed to enter command mode
This is a major set back.
Rolled the base back to v2.2, radio shows v2.0.2 firmware. LoRa connection made.
This is intentional. Because we reset devices with development firmware on them dozens of times a day, the startup beep is disabled on release candidates for our sanity.
And while selecting the HAS/E6 the PPP field is blank and the program insists on data in this field, luckily it show what is the default,
This is a known bug and a fix will roll out today.
Now LoRa radio failed to enter command mode,
I’ll look at these shortly.
You are hitting edges of the firmware we’ve tested, but not in the combinations you’re using them. This is good! As always, thanks for reporting these.
The LoRa radio fix will roll out today.
Went out this morning to capture some test points, Rover d2.3 Base v2.2, using only LoRa corrections Base placed on OPUS solution ECEF. The base unit started in Rover mode so I had to use the usb cable to set the unit to Base Caster mode. Seems shutting down and restarting the unit changes the mode to Rover?
I needed to restart both devices after I stopped taking points, the LoRa would not connect and the Rover just said connecting until it timed out, I had to restart the iPhone.
This image below is a test I did the other evening both Rover and Base on v2.2.
Red line is a track using my wifi connection which gets out about 75 feet, the blue line is the Base and Rover using LoRa only for corrections.
The next image is from this morning using the Base v2.2 and the Rover d2.3. I had to use Serial Terminal to jump start the unit into Base with Caster. Point #20 is after I had restarted both Base and Rover, in addition to having to restart the iPhone multiple times.
I can’t select a different profile in web config.
This has been fixed, and LoRa radio config, and web config was greatly improved, and profiles should be working. Please find the attached binary (this binary is release candidate from today or RC-Nov 4).
Base v2.2. Seems shutting down and restarting the unit changes the mode to Rover?
This is not normal behavior. A device should return to the last state before power-off. v2.2 has severe problems with Profiles and I do not recommend running it on a Torch. Please let us know how d2.3 works.
Rover just said connecting until it timed out, I had to restart the iPhone.
It is good to know you are using iOS. I will do some additional testing.
I’ve installed d2.3 on both Base and Rover, I’ve created Profiles 1 and 2 on both units, I had an RTK-Fix and now without any correction source other the H6 PPP-GAL, add my caster mount point for NTRIP, stylin. I’ve connected one unit via wifi config to add a profile the other I used serial config as it is faster that using a phone. Only thing I noticed is I have to change phones iPhone to Android and back to force a RTK-Fix or PPP-GAL. I have the Base running ECEF coordinates and the Rover receiving LoRa corrections only, good fix so far, last test I got about 3 miles in a suburban area.
Looks good so far.
Mike
Ok I can use the wifi config on the Rover unit but the Base is doing the same as before, showing 2 profiles, Profile 1 and 12345678901234567890, selecting any profile and saving will corrupt the current profile. The d version of the firmware does not enumerate the Base - Rover part of the Torch name.
Spent a little time this evening testing the LoRa, again the Base is on an ECEF OPUS solution casting to two servers, I did a similar test a few months ago using the telemetry radios using my Facets, I got about half the distance and lost radio connection.
Running into a small problem, the USB connector on one of my Torches is loose, if I wiggle it around I loose connection to Tera Term, is there a way tighten it?
Thanks,
Mike
A little bit of wifi testing this morning, the Base will not connect via wifi when the data in the profile is robust, I created a second profile, using only the LoRa connection, no wifi and the Torch name shows up in the wifi list and goes straight to the webpage with all the correct data, where I can do simple edits. I tested the wifi instead of the AP function and it did not connect in either profile.
Another issue, wifi is on all the time, so I see the Base unit number in the network details. I try to access it in the Chrome browser, site can’t be reached. I hit the power button twice to start the web config, it turns on but it shows some data then goes to can’t be reached. Back to Serial Connect.
I spent some time working with the rover in wifi config, I could only connect using AP mode as WIFI would not connect using the browser accessing profiles 3 and 4. The wifi mode works with profiles 1 and 2 but not with profiles 3 and 4. I switched 3 and 4 back to AP mode and I can connect and make changes to the profiles. The base is another story as it does not connect to the wifi config either WIFI or AP mode.
