Torch Error

Hello,

After setting up the point perfect wifi settings, I went to test in SWmaps, no bluetooth connection, could not see the torch at all. When I rebooted and tried to put in wifi config mode with 2 quick beeps, nothing, wotn enter cofig mode. I used the serial cable and got the following message in the terminal program. Thats where i’m at now,

it worked a few days ago, not point perfect accuracy but bluetooth in SWmaps. Is there a master reset that can be done?

Doc attached , even if point perfect subscription ended, which it didnt , why would I not be able to enter config in terminal program?

The torch has 1-month PP included, maybe that has expired?

Do any of the config methods work? https://docs.sparkfun.com/SparkFun_RTK_ … with_wifi/

Also try using another cable/usb port just to rule those out as suspects

Tim,

It looks like you have two separate issues.

The PointPerfect issue is on our end I believe; I’m working on it right now. If your corrections just magically start working, let me know because it’s probably in response to me changing the provisioning details of the device.

Not being able to see Bluetooth is really weird, and I haven’t come across that with the Torch (or any of our RTK products actually). As long as it has power, Bluetooth is one of the first things to start up. Procedure for a factory reset can be found here: https://docs.sparkfun.com/SparkFun_RTK_ … tory-reset

Also, my apologies for the slow reply, I was travelling last week and wasn’t able to do any tech support. Please let me know how it goes!

Its now connected via bluetooth to SWmaps. I dont get a flashing green satellite on the face, flashes orange so I’m guessing no point perfect fix?

BTW I was at 37mm lat/long and 60mm verticle .

3 questions? So is the point perfect working on your end? I was at 37mm lat/long and 60mm vertical, Is that what I would normally get from point perfect? I saw guys getting 14mm. Will the GPS light flash green when point perfect is fixed? Thanks for the reply’s

Tim,

SW Maps will show the fix type under the GNSS Status menu just above the PDOP value. The LED’s will indicate information about the fix quality, but the way it does that depends on whether you purchased a beta version Torch, and which firmware you are running (we made quite a few adjustments early on). I’d say the cleanest way is to look at it in SW Maps, since that gets rid of any guesswork. 37mm indicates to me that you were in RTK Float, or you were getting Galileo E6 corrections; worst RTK Fix I’ve seen was at 24mm with PointPerfect / IP.

Tim, not sure if you are still running into that issue, but either way we have [updated our firmware to v1.2 with some fixes that improve connection stability; please give that a try!](SparkFun_RTK_Everywhere_Firmware_Binaries/RTK_Everywhere_Firmware_v1_2.bin at main · sparkfun/SparkFun_RTK_Everywhere_Firmware_Binaries · GitHub)

I updated to firmware v1.2 then did a factory reset. My bluetooth connection stabilized on my iPhone 11 Pro via SWMAPs. I still have not seen point perfect give me anything but RTK float at around 1.6 inches (horizontal). I assume I am getting my corrections via sparkfun zero touch but maybe not?

1 Like

The Torch has quite a few correction source options; there is a priority list that you can adjust to change which option is used first, if available. You can also disable each correction source individually.

40mm is more what I expect from E6 HAS, not from PointPerfect/IP. Can you try using an NTRIP service (RTK2Go for example), verify that the PointPerfect corrections are the issue, not the device itself? You can also send me a direct message with your Device ID if you’d like, and I can look it up on Thingstream and verify that your device is connecting correctly.

Ok found my thread in the new discord system. I am still unable to get Pointperfect corrections. I can’t get past “rtk Float level). I have tried to resolve this in both the Seattle And the eastern Washington Areas.

I am using Swmaps via a Bluetooth connection set to apple BLE for my IPhone. I have also confirmed Ntrip option via rtk2go. I receive correction data from Ntrip or Bluetooth. System will not fix,

I did create some issues trying to set up my own thing stream account instead of using zero touch provisioning via sparkfun.
I had ublox delete all things in my thing stream account. That released my torch so I could use ZTP from sparkfun. I with the help of everyone I was finally able to connect and confirm ZTP via sparkfun account.

I still cannot get a “fix” best I do is a “float”. If i can’t get a fix, then I can’t activate the torches tilt compensation system. My goal is a single rover torch device with sub 2 inch lateral accuracy in under 3 minutes.

I updated the firmware to 1.3x. I have factory reset at least 6 times. I have tried WiFi, Bluetooth and WiFi hotspots. I have adjusted the configurations via terminal/serial port, rover wifi capture.

I have unavaco, ublox/thingstream/point perfect, rtk2go and several other systems for corrections. I think the best one I used was ‘point one nav” except it was barely in the coverage zone.

I am new to these devices but it should not be this hard to get an IP based fix on this torch.

Welcome to the new forum!

You have a choice:

  • You can obtain RTCM from a service such as PointOne Nav, over the cellular network (Torch connects to the phone over WiFi, then uses NTRIP to connect to PointOne Nav)
  • You can obtain SPARTN corrections from a service such as PointPerfect (Torch connects to the phone over WiFi, uses MQTT to get corrections from PointPerfect).

These two services are OSR vs SSR and behave differently. If you’re looking for a quick lock, use PointOne Nav or Syklark. PointPerfect works but it’s not as quick or as accurate (but it’s way cheaper).

Thanks I think it is all working as designed.

I would use point one nav for a quick and accurate fix but it has holes in the service area in my exact location. So I will go with point perfect for now.

It’s definitely slower, never gives me a fix just a float so I can’t use the tilt compensation feature of the torch. So this is disappointing.

I disabled the E6 HAS corrections and that increased my speed and accuracy to ~1.4 inches after 5 min. I also turned on the localization in pointperfect. ( not sure it helped, but the idea of it makes since) .

Bluetooth and hotspot connections are stable most of the time.

It’s time to put it out in the field and see how it does. I like the torch device it has been good for the most part. I just needed to manage my expectations on getting accuracy and a fix in my rural location without an OSR service plan or base station.