ESP-StepperMotor-Server: Limit switches not working
Hi, a simple limit switch does nothing. When triggering the switch using ‘ll=3’ gives:
[DEBUG] Limit switch 's1oben' has been triggered (IO pin statGuru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout on CPU1).
Core 1 register dump:
PC : 0x40091eb2 PS : 0x00060035 A0 : 0x80090b56 A1 : 0x3ffbee3c
A2 : 0x3ffb9068 A3 : 0x3ffdd710 A4 : 0x00000004 A5 : 0x00060023
A6 : 0x00060023 A7 : 0x00000001 A8 : 0x3ffdd710 A9 : 0x00000017
A10 : 0x3ffdd710 A11 : 0x00000017 A12 : 0x3ffc4c64 A13 : 0x00060023
A14 : 0x007bf518 A15 : 0x003fffff SAR : 0x00000013 EXCCAUSE: 0x00000006
EXCVADDR: 0x00000000 LBEG : 0x4008bd41 LEND : 0x4008bd51 LCOUNT : 0xfffffff0
Core 1 was running in ISR context:
EPC1 : 0x4010303f EPC2 : 0x00000000 EPC3 : 0x00000000 EPC4 : 0x00000000
Backtrace: 0x40091eaf:0x3ffbee3c |<-CORRUPTED
#0 0x40091eaf:0x3ffbee3c in vListInsert at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf public/components/freertos/list.c:183
Core 0 register dump:
PC : 0x40092047 PS : 0x00060035 A0 : 0x80090778 A1 : 0x3ffbec3c
A2 : 0x3ffbf518 A3 : 0x00000001 A4 : 0xe67fc000 A5 : 0x00060023
A6 : 0x00060021 A7 : 0x0000cdcd A8 : 0x0000ab63 A9 : 0xffffffff
A10 : 0x00000000 A11 : 0x00000001 A12 : 0x667fc000 A13 : 0x00000007
A14 : 0x007bf518 A15 : 0x003fffff SAR : 0x0000001a EXCCAUSE: 0x00000006
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0xe67fc000 LCOUNT : 0x3f40b296
Backtrace: 0x40092044:0x3ffbec3c |<-CORRUPTED
#0 0x40092044:0x3ffbec3c in esp_ptr_external_ram at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/soc/include/soc/soc_memory_types.h:97
(inlined by) spinlock_acquire at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_hw_support/include/soc/spinlock.h:99
(inlined by) xPortEnterCriticalTimeout at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/freertos/port/xtensa/port.c:288
Here is the config:
{
"serverConfiguration": {
"port": 80,
"wififMode": 2,
"wifiSsid": "wifissid",
"wifiPassword": "*****",
"apName": "����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������?���������������������������������������������,[�?���������������������������������_\b@�<\b@0",
"apPassword": "*****",
"motionControllerCpuCore": 0
},
"stepperConfigurations": [
{
"id": 0,
"name": "motor1",
"stepPin": 23,
"directionPin": 22,
"stepsPerRev": 200,
"stepsPerMM": 0,
"microsteppingDivisor": 8,
"rpmLimit": 1200,
"breakPin": 255,
"breakPinActiveState": 1,
"breakEngageDelay": 0,
"breakReleaseDelay": -1
}
],
"switchConfigurations": [
{
"id": 0,
"name": "s1oben",
"ioPin": 19,
"stepperIndex": 0,
"switchType": 6,
"switchPosition": -1
}
],
"rotaryEncoderConfigurations": []
}
I also noticed every time after reboot and after motor movement I get the following line:
E (1441) gpio: gpio_set_level(226): GPIO output gpio_num error
The motor is working, though.
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- remove debug output in ISR As reported in Limit switches not working #39 the degbug log output causes a WDT timeout resulting in kernel panic — committed to pkerspe/ESP-StepperMotor-Server by pkerspe a year ago
- remove debug output in ISR As reported in Limit switches not working #39 the degbug log output causes a WDT timeout resulting in kernel panic — committed to pkerspe/ESP-StepperMotor-Server by pkerspe a year ago
please open a new issue ticket for UI stuff
will check on the direction switch interaction problem in a bit.