Vaelatern
commented
3 months ago They are supposed to be forced into team number 0301. I forget where that forcing has to happen but team numbers are 4 digits, with leading zeroes as necessary.
Closed 3wheelok closed 3 months ago
Vaelatern
commented
3 months ago They are supposed to be forced into team number 0301. I forget where that forcing has to happen but team numbers are 4 digits, with leading zeroes as necessary.
3wheelok
commented
3 months ago I also tried a 6 digit team number of 123456, and it worked with no issue. I also tried a 6 digit team number of 012345 with a leading 0. The gizmo firmware build removed the leading 0. After that, it worked using team number 012345 and 12345 for the gizmo field practice command.
Using team number 123456 worked
.\gizmo firmware configure
? Team Number 123456
? Team Number 123456
? Use the driver's station No
? Use external network controller Yes
? Network SSID OKBEST
? Network SSID OKBEST
? Network PSK (Input will be obscured) ********
? Address of the driver station (can be an mDNS name) (192.168.0.164)
? Address of the driver station (can be an mDNS name) 192.168.0.164
PS C:\Users\Matt\Documents\OKBEST\GIZMO> .\gizmo firmware build
2024-05-13T14:56:30.563-0500 [INFO] firmware: Log level: level=info
2024-05-13T14:56:30.570-0500 [INFO] firmware.factory: Performing Step: team=123456 step=Unpack
2024-05-13T14:56:30.575-0500 [INFO] firmware.factory: Performing Step: team=123456 step=Configure
2024-05-13T14:56:30.576-0500 [INFO] firmware.factory: Performing Step: team=123456 step=Compile
2024-05-13T14:57:36.120-0500 [INFO] firmware.factory: Performing Step: team=123456 step=Export
2024-05-13T14:57:36.121-0500 [INFO] firmware.factory: Performing Step: team=123456 step=Cleanup
PS C:\Users\Matt\Documents\OKBEST\GIZMO> cp .\gss_123456.uf2 d:
PS C:\Users\Matt\Documents\OKBEST\GIZMO> .\gizmo field practice 123456
2024-05-13T15:07:11.397-0500 [INFO] field: Log level: level=info
2024-05-13T15:07:11.397-0500 [INFO] field.web: HTTP is starting
2024-05-13T15:07:11.398-0500 [INFO] field.mqtt: MQTT is starting
2024-05-13T15:07:12.409-0500 [INFO] field.pusher: Connected to broker
2024-05-13T15:07:12.409-0500 [INFO] field.metrics: Connected to broker
2024-05-13T15:07:12.409-0500 [INFO] field.tlm: Connected to broker
2024-05-13T15:07:12.410-0500 [INFO] field.pusher: Subscribed to topics
2024-05-13T15:07:12.411-0500 [INFO] field.metrics: Subscribed to topics
2024-05-13T15:07:15.107-0500 [INFO] field: Startup Complete!
2024-05-13T15:07:17.459-0500 [INFO] field.pusher.gamepad-controller: Successfully bound controller: jsid=0Using team number 012345 worked using team number 12345 after the build.
.\gizmo firmware configure
? Team Number 012345
? Team Number 012345
? Use the driver's station No
? Use external network controller Yes
? Network SSID OKBEST
? Network SSID OKBEST
? Network PSK (Input will be obscured) ********
? Address of the driver station (can be an mDNS name) (192.168.0.164)
? Address of the driver station (can be an mDNS name) 192.168.0.164
PS C:\Users\Matt\Documents\OKBEST\GIZMO> .\gizmo firmware build
2024-05-13T15:15:48.100-0500 [INFO] firmware: Log level: level=info
2024-05-13T15:15:48.101-0500 [INFO] firmware.factory: Performing Step: team=12345 step=Unpack
2024-05-13T15:15:48.114-0500 [INFO] firmware.factory: Performing Step: team=12345 step=Configure
2024-05-13T15:15:48.115-0500 [INFO] firmware.factory: Performing Step: team=12345 step=Compile
2024-05-13T15:16:59.353-0500 [INFO] firmware.factory: Performing Step: team=12345 step=Export
2024-05-13T15:16:59.355-0500 [INFO] firmware.factory: Performing Step: team=12345 step=Cleanup
cp .\gss_12345.uf2 d:
PS C:\Users\Matt\Documents\OKBEST\GIZMO> .\gizmo field practice 12345
2024-05-13T15:18:22.875-0500 [INFO] field: Log level: level=info
2024-05-13T15:18:22.876-0500 [INFO] field.mqtt: MQTT is starting
2024-05-13T15:18:22.876-0500 [INFO] field.web: HTTP is starting
2024-05-13T15:18:23.885-0500 [INFO] field.tlm: Connected to broker
2024-05-13T15:18:23.885-0500 [INFO] field.metrics: Connected to broker
2024-05-13T15:18:23.885-0500 [INFO] field.pusher: Connected to broker
2024-05-13T15:18:23.886-0500 [INFO] field.metrics: Subscribed to topics
2024-05-13T15:18:23.886-0500 [INFO] field.pusher: Subscribed to topics
2024-05-13T15:18:26.767-0500 [INFO] field: Startup Complete!
2024-05-13T15:18:28.923-0500 [INFO] field.pusher.gamepad-controller: Successfully bound controller: jsid=0Using team number 012345 worked using team number 012345 after the build and it worked.
.\gizmo field practice 012345
2024-05-13T15:26:15.606-0500 [INFO] field: Log level: level=info
2024-05-13T15:26:15.607-0500 [INFO] field.web: HTTP is starting
2024-05-13T15:26:15.609-0500 [INFO] field.mqtt: MQTT is starting
2024-05-13T15:26:16.613-0500 [INFO] field.tlm: Connected to broker
2024-05-13T15:26:16.614-0500 [INFO] field.pusher: Connected to broker
2024-05-13T15:26:16.614-0500 [INFO] field.metrics: Connected to broker
2024-05-13T15:26:16.615-0500 [INFO] field.pusher: Subscribed to topics
2024-05-13T15:26:16.616-0500 [INFO] field.metrics: Subscribed to topics
2024-05-13T15:26:19.568-0500 [INFO] field: Startup Complete!
2024-05-13T15:26:21.660-0500 [INFO] field.pusher.gamepad-controller: Successfully bound controller: jsid=0
the-maldridge
commented
3 months ago This has been resolved on current versions for a long time now which suggests that you're running a very old version of the Gizmo binary. The firmware submenu hasn't existed for a while due to the firmware becoming a generic build. Please re-validate on a current build and re-open if necessary.
3wheelok
commented
3 months ago Thanks!
On Thu, May 16, 2024 at 1:55 PM Michael Aldridge @.***> wrote:
This has been resolved on current versions for a long time now which suggests that you're running a very old version of the Gizmo binary. The firmware submenu hasn't existed for a while due to the firmware becoming a generic build. Please re-validate on a current build and re-open if necessary.
— Reply to this email directly, view it on GitHub https://github.com/gizmo-platform/gizmo/issues/11#issuecomment-2115976736, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7QMXESWCRBGMYHTHSMTRHLZCT6LXAVCNFSM6AAAAABHQQEAAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVHE3TMNZTGY . You are receiving this because you authored the thread.Message ID: @.***>
Bottom Line Up Front: At OKBEST our assigned Team Numbers are 301 to 350.
When using a pc to create firmware and as the driver's station, team numbers less than 4 digits, or with a preceding 0, do not allow the PC to connect to the gizmo on the robot.
For example, a team number of 301 will not work. Never get a green network light. Neither will team number 0301. But a team number of, 1301 will get a green network light.
Here is the more detailed proof of the issue.......
Followed by
cp .\gss_301.uf2 d:and ....
will result in a yellow network light and no connection.
Without changing anything else we add a leading 0 to the team number to make it 4 digits ....
creates a file, gss_301.uf2
followed by .....
cp .\gss_301.uf2 d:and .....
results in a yellow network light.
as does the team number without the leading 0 ...
But a team number like 1301 connects properly .....
and
cp .\gss_1301.uf2 d:and ....
does result in a green network light and a white blinking field light.