FABI3

[benjaminaigner]

Dear all,

we have finished FABI3 hardware & case (v3.1, with RJ25 as extension connector; v3.0 is with a jack plug, but is testing only).

As this version uses a RPi PicoW with an RP2040 core, this hardware is more similar to the FLipMouse instead of FABI2.

Following changes are necessary in the webgui:

• Change number of external buttons, using 5pcs now.
• We have strongsip / strongpuff now
• Infrared is included
• Joystick actions are possible
• I decided (for now, maybe room for discussion) to use StrongSip/Puff + Button 2/3/4/5 as action (instead of StrongSip/Puff + Up/Down/Left/right as in the FM3).
• As the Bluetooth firmware is included in the FABI3 firmware, no update is possible/necessary without updating the RP2040
• FABI3 updates are with .UF2 files like FM3

AT BM assignment can be seen here: https://github.com/asterics/FABI/blob/SRC_v3.0/FabiWare/modes.h

These points need further discussion (for WebGUI AND the firmware itself):

• How to handle the longpress, which is not included in FM firmware?
• The same for anti-tremor settings
• How should we transfer FABI2 presets to FABI3? AT BM mapping is changed because of various things (button count, ...).
• @klues suggested the possibility to change the configuration of this device similar to AsTeRICS Grid, where you first select something to do (press key, click, Joystick,...) and then assign an action to it (single button press, double/triple press, sip / puff, ...)

[deinhofer]

Have you already implemented and released the changes? Seems that the UI is already new regarding short press/long press trigger:

Suggestion for terminology change

I would like to suggest a change of the terminology. I think there was some feedback already that the name "slot" is not really descriptive, maybe "profile" or "configuration profile" would be better.

also on the left side I would change "Bezeichnung" to "Ereignis" (trigger) or "Auslöseaktion" because that's the point! Then the trigger action would be

• button short press (single)
• button short press (double)
• button long press
• sip
• puff
• ...

[benjaminaigner]

Seems that the UI is already new regarding short press/long press trigger:

I think this different view is not changed, but a little bit different in demo mode. If you have a FABI connected, the long press actions are mutual exclusive with buttons 6-8 and are shown only if the long press time is set.

Suggestion for terminology change

We brought up the suggestion "mode" / "Modus" instead of slots. I like "trigger" / "Ereignis" as well and "action"/"Aktion" for the right column.