Skip to content

Setup button doesn't work if powered on in Base Mode (Facet, v2.0 firmware) #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tonycanike opened this issue Jun 1, 2022 · 5 comments

Comments

@tonycanike
Copy link
Contributor

tonycanike commented Jun 1, 2022

Subject of the issue

The Facet setup button is unresponsive to short pushes if the Facet is powered on when configured to be a Base unit.

Your workbench

SparkFun RTK Facet v2.0-May 26 2022
ZED-F9P firmware: HPG 1.32

Steps to reproduce

  1. Start with device powered on in Rover mode.
  2. Use the setup button (short pushes) to select Base mode. Wait for "Base Started" display.
  3. Long push to power off.
  4. Long push to power on.
  5. Unit powers up in Base mode,
  6. Short pushes of Power/Setup button do not allow change of mode. Can not enter WiFi config.
  7. Long pushes still work to power off and on.

Expected behavior

Short pushes should allow change of mode.

Actual behavior

Short pushes are unresponsive.
Can not be put into WiFi config mode to enter fixed base coordinates.
Can not be switched to Rover mode via the button.
Serial mode can be used to switch the Rover mode, Short pushes work in Rover mode.

Note you must select Base mode, power off, and power back on. Simply switching from Rover to Base via the button does not disable the short pushes of the button.

This is especially problematic when out in the field and unable to use serial configuration. Problem was discovered after base was setup over known point and I attempted to put the Facet into WiFi config mode to enter fixed coordinates.

Problem subsequently replicated multiple times on two different units.

I have two Facets and both exhibit this behavior.
I've used serial configuration to reset to factory defaults, problem still exists.
Problem did not exist with V1.12 firmware.
Problem started immediately after upgrading to V2.0 firmware.

@nseidle
Copy link
Member

nseidle commented Jun 1, 2022

Thanks for reporting! Can confirm. We'll get it fixed shortly.

nseidle added a commit that referenced this issue Jun 1, 2022
@nseidle
Copy link
Member

nseidle commented Jun 1, 2022

I think I've got it. I'll get an RC up shortly.

@nseidle
Copy link
Member

nseidle commented Jun 2, 2022

Ok - RC June1 with the fix is on the release page. This was a bad bug; sorry for messing up your unit in the field.

Please re-open if you continue to have problems.

@Firefishy
Copy link

I have a unit stuck in base mode. Would appreciate instructions on how to fix this? How do connect via serial mode?

@nseidle
Copy link
Member

nseidle commented Jun 3, 2022

Sorry about that! See this issue #151

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants