new build - gyro functionality seems opposite of intended

[BouncyLlama]

I've just completed an Alpakka, following the manual. The gyro behavior is exactly the opposite of how it is described; touching the hexagon DISABLES the mouse....I'm guessing the solution is to do a custom firmware build with that setting inverted? Everything else seems great. Is this a common mistake perhaps? Feels like I must have done something wrong, although no idea what. Had JLCPCB do the surface-mount assembly per the BOM, if that matters.

[marcos-diaz]

We never had that problem before, so thanks for letting us know.

So the gyro is enabled all the time?

Can you check is the behavior is the same with the PCB out of the case, without any touch surface connected?

Also which conductive filament did you use?

Thanks.

[BouncyLlama]

It is the same out of the case, yes. I actually removed it completely and then touched the hexagon to it like that to verify it behaved the same way. Hexagon printed in Protopasta's conductive PLA. The rest of the controller is Polymaker's PolyTerra PLA

[marcos-diaz]

No idea what could be wrong, but yes, a firmware build changing profiles from GYRO_MODE_TOUCH_ON to GYRO_MODE_TOUCH_OFF should revert the behavior.

If you cannot compile the firmware yourself, join Discord and someone will compile it for you.

[BouncyLlama]

Something is very wrong...I feel like my board about has to be defective. configuration --> behavior

• TOUCH_ON --> TOUCH_OFF
• TOUCH_OFF --> ALWAYS_ON
• ALWAYS_OFF --> ALWAYS_OFF
• ALWAYS_ON --> ALWAYS_ON

Additionally, sometimes upon flashing specifically the TOUCH_ON configuration, sometimes it behaves as if it were ALWAYS_OFF for a bit, and then suddenly starts acting like TOUCH_OFF

I'll try and get the debugger up and running tomorrow. Maybe attach a Pi to the 2nd pre-assembled board and see if it behaves the same way. I'll report back what I figure out. Have to say, thank you for making it so easy/quick to flash...makes this kind of thing a lot less frustrating than it'd be otherwise.

[BouncyLlama]

Setting CFG_TOUCH_THRESHOLD to 3 rather than 4 resolved the issue! I can only assume something is off with my hardware that made this necessary, but it seems in working order with this change.

[marcos-diaz]

Interesting, thanks for figuring it out.

Could be bad soldering connection or a defective resistor?

We will keep an eye on the issue, or we may change the default threshold value just in case.

Thanks!