Issue with bootstrapping

[targonn]

Hello,

I already spent numerous hours trying to configure FMS with no luck.
I am attaching the log, where you can see successful flashes of both the scoring box and field station, what seems like successful bootstrapping, but failing reconciliation.

session3.log

The corresponding ethernet port LED is flashing between green and red on the scoring box. Gizmos fail to pair.

I already tried wiping both mikrotiks using Netinstall and reflashing, redownloading k400 image, and starting over, changing SD cards.
Both routers can be accessed via network after bootstrapping with IP addresses (can't log in because I don't know the password).

I laso tried following both GUI and command line instructions, but both are failing. Command line instructions are from these videos: https://bestedu.bestrobotics.org/courses/gizmo-fms-for-hubs/

Many commands in the GUI are failing due to permission errors and have very little feedback, so I ended up using video tutorials.

Thank you for helping,

Nick

[the-maldridge]

This looks like at some point you touched /var/lib/gizmo as root, and now the directory is no longer writable to the service user. Verify that the permissions on /var/lib/gizmo and /var/lib/gizmo/.netstate are 0755 and the owner is _gizmo on all but the .htgroup and .htpasswd files.

EDIT:

Re-reading your logs this is exactly what happened. If you want to run things via the CLI, you must do so as the appropriate user. BEST's documentation appears to have drifted somewhat substantially from the reality of the currently released versions, so I'll refer you to the upstream documentation. If you really really want to use the command line workflow you can, but the general recommendation for most users is the graphical workflow.

[targonn]

Michael,

I did touch it in this iteration, but I had tried it before using a purely graphical workflow. I will try to reimage my SD card for the 10th time and start over.
The problem is that there is no feedback on errors, and gizmos don't bind. There are also no logs to see...

Nick

[targonn]

Same story using a graphical workflow on a new image.
There seems to be a connection error between the field box and the scoring box. Gizmos won't bind.
Gizmo binds well to the driver station.

[the-maldridge]

Binding has nothing to do with bootstrapping, so I think we're solving two different problems here. Your bootstrap workflow completed successfully and looks like you have a ready to run field setup. Binding is now the issue you're running into.

While the console workflow is available and can be used, if you can wait another day or so the mid-season update will ship which contains the web-based bind experience that provides more detailed feedback on what is going on. It is also the recommended workflow to use for all competitions as it is self-service for a team to bind to the field, rather than requiring direct access to the FMS workstation.

[plurt97]

Curious as to what the status is on this. Is the FMS functional? We were hoping that our hub would have the router and FMS set up during practice day for systems test and maybe a go/no-go decision on it being used for our hub tournament. Is that feasible?

[the-maldridge]

The FMS has been functional for some time now. You're welcome to do your own setup and testing. Note that competitions are not supported outside of FMS enabled wireless modes.

[plurt97]

Ah, ok. Just reading the above post and a statement about a new version being pushed out. I'm all for the FMS capable tournament, it's just that there wasn't one last year, so I was hoping we'd all get a chance to see it in action before the tournament - the practice day would be a great option. Unfortunately, we don't have the time/resources that we did last year when we were working on getting the Gizmo working, so sadly we can't test out the FMS this year - which was a bummer because, again, would love to see it in action. So. Many. Future. Opportunities! :-) Thanks for the info!

[the-maldridge]

The 0.2.0 build was released in ~August for general availability, and is the approved release train for BEST competitions. The 0.2.1 and 0.2.2 releases that have gone out in the last few days are related to the new web-binding kiosk feature which allows a competition to designate a different machine from the FMS workstation to be used as a self-service kiosk for binding to the field. If you have been to an FRC competition before this functionality is similar to the robot radio programming kiosk. It is not required, but is strongly recommended due to the logistics streamlining that it unlocks.

[targonn]

Michael,

I'm testing version 0.2.2 and again running into the binding issue.
Bootstrapping completed successfully.
Next, I received an error regarding Webserial feature set missing in the built in browser.

I installed a Webserial extension from the extension store in the browser

Gizmo is still failing to bind. Two lights are flashing with no activity on the screen. Gizmo binds fine to the driver stations. It is flashed with the recent firmware.

Please assist. Our demo day is this Sunday and the main game is next weekend.

Thanks,

Nick

[the-maldridge]

I would be very surprised if the WebSerial extension works for Firefox. That is certainly not something my team has tested as it requires installing some sketchy 3rd party daemons on the host to make it work. The Web Bind feature is designed to be used in a chromium-based browser only, and really its designed to be used on another computer distinct from the FMS workstation.

What you've described above is consistent with the Gizmo searching for the bind endpoint, but not finding it. Given that the console buffer in your last photo is completely blank, I think the firefox extension is just not working. If you really want to run the web bind on the Gizmo FMS, you can install chromium by launching a terminal window from the IceWM window in the lower left hand corner and running this command:

sudo xbps-install -Syu xbps && sudo xbps-install -y chromium

I have not personally tested this yet, but will add it to the docket for this weekend. Chromium tends to be the same everywhere either working or failing without any in-betweens, so I would expect this to work if it installs at all.

[shannonsjones]

I installed chromium on my pi400 for this very reason. I was able to bind gizmos on it fine, but it did some strange things to stage mapping in Firefox. That is stage mapping would never see a gizmo plugged in unless I opened chromium and then it would show up in Firefox after that. Never got to the bottom of why it was behaving that way and I have since removed chromium and am using a separate laptop for the binding operations.

[shannonsjones]

And windows seems to create a new serial connection for every Gizmo plugged in, rather than selecting it the first time and it being persistent. I plan on taking a separate Linux powered laptop to our game day next Friday/Saturday for binding gizmos to the FMS.