[feat] wifi ap+sta mode for esp32

[jangshik]

What feature

for esp32 variant can wifi ap+sta mode added?

Why

some will use a router inside the car for whitelist, it will be convenient to access web dashboard

Known CAN ID / signal name (if any)

No response

Where it fits in the roadmap

No response

Anything else

No response

[vrs11]

What a coincidence, I've been working on this thing recently.
#102

P/S: The main issue is to identify the device IP, but thats another problem to solve

[jangshik]

What a coincidence, I've been working on this thing recently. #102

P/S: The main issue is to identify the device IP, but thats another problem to solve

i was actually looking into your repository
just fit for my needs, using t2can for veh and chassis.
i'm moving from ev-open-can-tools to this, is there a way to just 1021 mux1 bit19 to 0, just to remove ecer79?

[hypery11]

@jangshik welcome — glad it fits your T-2CAN (vehicle + chassis) setup.

Good news: that's already what the app does. On every 0x3FD mux1 frame the autopilot handler clears bit 19 (the hands-on / ECE-R79 request) — fsd_handle_autopilot_frame(), set_bit(frame, 19, false) on mux1. It runs automatically whenever injection is Active on a detected HW3/HW4 car, so there's no separate toggle to flip for that bit.

The Nag Killer toggle is the complementary half: it echoes 0x370 EPAS3P with counter+1 and handsOnLevel spoofed, which covers the EPAS-side nag. So set Mode = Active and you get both.

And thanks for #102 — merged. The STA WiFi you added also helps the "identify the device IP" P/S, since the board can join your phone hotspot / existing network instead of only hosting its own AP.

[jangshik]

@jangshik welcome — glad it fits your T-2CAN (vehicle + chassis) setup.

Good news: that's already what the app does. On every 0x3FD mux1 frame the autopilot handler clears bit 19 (the hands-on / ECE-R79 request) — fsd_handle_autopilot_frame(), set_bit(frame, 19, false) on mux1. It runs automatically whenever injection is Active on a detected HW3/HW4 car, so there's no separate toggle to flip for that bit.

The Nag Killer toggle is the complementary half: it echoes 0x370 EPAS3P with counter+1 and handsOnLevel spoofed, which covers the EPAS-side nag. So set Mode = Active and you get both.

And thanks for #102 — merged. The STA WiFi you added also helps the "identify the device IP" P/S, since the board can join your phone hotspot / existing network instead of only hosting its own AP.

i already am nag killing on private can to epas. so on my chassis can i only set ecer79 to 0

[hypery11]

Right — on the bus that carries 0x3FD, clearing bit 19 on mux1 is the ECE-R79 / hands-on request, and that's the only bit needed for that piece. The app does it automatically whenever it's injecting on 0x3FD (Mode = Active, HW3/HW4 detected) — nothing extra to set. Just make sure injection is running on whichever bus actually carries 0x3FD for your car (normally the vehicle/party CAN, not chassis). Your 0x370 EPAS nag-kill on the private CAN is the complementary half — together that's both sides covered.