AMAZING!!! I think a TORCH ORDER goes in tomorrow… WOW !!!
Ignorant question again, the Deltas are in Meters? so 0.09m, 0.266m, 0.238m (23.8 centimeters) - that definitely cannot be your iPhone GPS!!!
Meters are my assumption. This app is neat, but hard to figure out.
This is using the $8 PP Subscription w/ the Torch over the iPhone Personal Hotspot.
I performed a factory reset this morning, so basically default settings in the Torch; but turn ON TCP Server, and a few personal adjustments (PP Tile Level #5, etc).
The IP acts like it’s Static, but I’ve only connected a few times.
Point Perfect MQTT results from a Cold Start are: 2cm, 2cm, 6cm “reported” in X,Y,Z.
2 Likes
Yes, I have given them some feedback but their website doesn’t currently have contact information. They said in an email to me big upgrades coming to their app, their website. I was in e-mail contact for a few messages but that has gone silent… maybe on a European vacation, they do have more holidays that we do.
I received my Torch on Saturday but was hauling logs. Got it out of the box, turned it on and did the SW MAPS test. No firmware upgrades yet, just the basic test and was successful with Bluetooth and SW MAPS Off to a good start, this accurate with no correction service turned on yet 16.4ft height because it’s on my second story patio railing.
1 Like
You are getting some form of correction. That might be HAS E6 since no baseline length is noted.
Age: 6.5 Seconds
ID: 9901
[Edit] Just checked my notes from my Torch Testing, E6 seems to be Ref Station ID: 9901
1 Like
I know you said one some other threads about accuracy, that when the devices are proclaiming their accuracy it may not be trustable (Paraphrase) So when SW MAPS is saying 4.5 inches of accuracy, is that realistic without the correction service setup?
I also haven’t updated any of the firmware, or checked to see what it is. I just turned it on and tried it to confirm it was working… worked for about 10 minutes before battery died. I will start my measurement accuracy without a paid for correction service tomorrow. And I will look into how to confirm firmware and update if necessary… well learn how to check and upgrade. Thanks again for all your support
(ESP32, UM980, STM32)
1 Like
That’s coming from the GNSS chip, not actually SW Maps… and it means very little.
@ChrisO , Here’s what I do for an “easy way” to measure GNSS repeatability using SW Maps on iOS:
- Establish a semi permanent place to mount the GNSS. Can be as simple as attaching a Rod to a fence post, etc.
- Store Points in SW Maps over some period of time. You can store single epochs or average 30 seconds, etc…
- Keep adding stored positions to that Project in SW Maps, over days, weeks, etc.
- You can Export the Project anytime to check on the repeatability.
- The Trick is to Export to Spreadsheet AND select UTM as shown below:
If you don’t know your UTM Zone, it’s easy to find with Google.
With UTM added to the Spreadsheet Export, you get X, Y, Z in Meters in addition to Lat/Long/Z and all the Metadata 
On your iPhone, Open the FILES App and navigate to SW Maps/Export Folder
(I create a shortcut for quick access).
Then you can quickly email the Spreadsheet to yourself from the phone.
A few calculations in Excel and you have real results on the actual repeatability of the GNSS/Antenna/Correction Combination over an extended period of time.
Once you gather lots of data for your permanent position, you can notice when HAS E6 produces a 2’ error, but the GNSS thinks/reports it’s within a few inches. The same goes for any correction source.
Long term testing gets easy if you can establish a permanent location within Bluetooth range of your living room, office, etc. Leave the Torch operating outside and you can store points every 5-10 minutes on your phone from your couch while watching TV at night
Or even have the kids do it from a cheap Android Tablet, etc.
1 Like
I tried the same but failed to connect.
I set iPhone to 2.4Ghz wifi via the “Maximize Compatibility” = ON
I used a USB cable to verify Torch got an IP ADDR, it did 172.20.10.9 from my iPhone. (my home wifi 2.4ghz different SSID, but did get Torch connected to that to confirm it could WiFi Ok, and it did, then deleted home network info
Turned on TCP Server, set port 2948 but APGLOS doesn’t seem to see the Torch. I see it in in BLE mode "Torch Rover -Mac addr, but connecting to that doesn’t pass data to APGLOS either.
I upgraded the Firmware to 2.1 and repeated and still got same results.
Any other setting you may have set?
I tried with options 1 & 2 off and blank too
Menu: TCP/UDP
- TCP Client: Enabled
- Host for TCP Client: 172.20.1.1
- TCP Client Port: 2948
- TCP Server: Enabled
- TCP Server Port: 2948
- UDP Server: Disabled
- Enable NTRIP Caster: Disabled
m) MDNS: Enabled
n) MDNS host name: rtk
x) Exit
@ChrisO , I don’t have the Torch with me right this minute, but I did check APGLOS and there are 2 Expert Settings that I have no idea of their function. You might want to check those?
I’ll be back at my office later today and will get it connected and let you know if I see anything else.
Thanks, I did have those two Functionality’s off, but that doesn’t seem to have fixed it either. The Lat/log & H fields remain blank, so at least I know it’s not the iPhone GPS feeding it. I can turn iPhone back on , and then it reports 30ft Deltas.
The only difference is my PointPerfect isn’t activated yet.
My two settings below [Functionality] for accepted accuracy are FIX TYPE and RTK
I was able to use my Edge Browser and Safari to use WEB Configuration via iPhone to torch so it has IP Connectivity.
I have Torch WIFI setting to WiFi, not AP
I’m meeting USDA/NRCS Forester at the farm today so won’t be able to test further until tonight (Feb 26)
I just confirmed APGLOS is working with Torch in normal AP Mode (not really related…I don’t think) and TCP Server ON. My iPhone Personal Hotspot is in Max Compatibility Mode.
I do have some NMEA sentences turned off, but that shouldn’t be causing a problem for you.
Menu: Message NMEA
1) Message GPDTM: 0
2) Message GPGBS: 0
3) Message GPGGA: 1
4) Message GPGLL: 0
5) Message GPGNS: 0
6) Message GPGRS: 0
7) Message GPGSA: 0
8) Message GPGST: 4
9) Message GPGSV: 9
10) Message GPRMC: 1
11) Message GPROT: 0
12) Message GPTHS: 0
13) Message GPVTG: 0
14) Message GPZDA: 0
[Edit] I was using a Development V2.1 RTK Firmware.
I’m flashing to the V2.1 Final now.
@ChrisO , Just for Giggles - I connected the Android version of Apglos App to the Torch and PostCard with no issues…using an El-Cheapo Samsung 8" Tablet.
The App was obviously written for Android and performs Much Better vs the iOS version.
I’m probably going to learn Apglos when I have some spare time… but the Android version 
Yes, I think I will need to make a bit more of an investment in Android, I will just need to clear it with the farm CEO. (Wife). 
Chris
1 Like
I’m still out in the field but I’ll try AP just in case. Thanks again
Chris
I changed WiFi back to (AP) mode. And I had to turn on ROVER Mode Again
IT IS WORKING NOW, but of course changed several things and don’t want to experiment breaking it tonight…
I will study each setting in the morning to see what each one means but here’s what my settings are in full
IN APGLOS on iOS
Main Settings
- Predefined
- USA Tennessee
- NAD83(2011)
- Tennessee / AAVD 88-GEOID18
- US Survey Feet
Display
- Lat/lon(west)/alt
- Map
- USA Style
Functionality
- GIS Off
- ? Off
Phone GPS NO
Expert Settings (ha are they kidding me?)
- Position shift = No
Functionality
[[[[[[[[[[ ON
2nd option ON
Accepted Accuracy
X? = Fix Type
FIX = RTK.
And under the Chain-Link which APGLOS call the CONNECT Menu
Wi-FI
Other
ON
Height 1.5 (assuming meters)
Wrench symbol off, but this toggles to on to set IP Address and Port and Antenna for NTRIP
Wrench = Off
IP= 172.20.10.9 (assigned by my iPhone HOT SPOT) discovered via using serial port
PORT = 2948
NTRIP = Antenna
One change, on [Accepted Accuracy] I had to change FIX TYPE to DISTANCE and (x) to 1.5 feet since I don’t have Corrections turned on yet, it was something like 0.016.
AGPLOS felt that the reported DELTA by the TORCH was too “wrong” When I tried to add a POINT it said data was too inaccurate.
Setting Accuracy to DISTANCE and setting to 1.5 I can add a point even if it was inaccurate. Once I have correction data turned I I will either change it back or reduce to 0.1 or some thing smaller
Just an Android clarification, Did the Torch actually join the HOT SPOT from the Android Tablet, or was the Torch and Android tablet connected via BLE, and the Android Tablet was connected to the HOT SPOT of your iPhone or to another phone? I am just trying to avoid buying a Table with a monthly Service fee. I really don’t like subscriptions if I can avoid them, so an Android Tablet connected to TORCH via BLE, and that Android Tablet connected to my HOT SPOT on iPhone would be acceptable, as long as the corrections finally make it all the way through all the devices…