Template reverts to default when configuring modbr tx/rx

[martin072]

I have this Kincony KC868-A6 module and used Blakadders template which works fine. I would like to use the modbus bridge function, and so tried to configure IO27 as ModBR TX and IO14 as ModBR RX (according their schematics).

When done so the device reverts to the basic ESP32-Devkit module type (module 1). Trying to activate "module 0" does not work, it reboots again in the default ESP32-Devkit. The KC868-A6 template is there and show as module 0. when change these pin to the set Serial Tx/Rx it works fine..

Is there something I've missed or need to do specifically to get the Modbus pins configured?

[sfromis]

Tasmota reverting to default settings is a deliberate recovery scheme in case your config results in a boot loop, then Tasmota may "scale back" features until able to boot without quickly crashing again. What to do about it depends on why it crashes. It can be useful to follow the serial console during the process.

[martin072]

It indeed crashes. When set one GPIO to Modbr Tx it boots fine, then when changing the second GPIO to Modbr RX it reboots and crashes on boot a few times.

Some settings have been reset (6)

With a stack trace. I do have the .elf file (custom compile) attached.

Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

Core  1 register dump:
PC      : 0x401cae8b  PS      : 0x00060830  A0      : 0x801baeb1  A1      : 0x3ffb63b0  
A2      : 0x3ffcbe68  A3      : 0x3ffb63e0  A4      : 0x00000000  A5      : 0x3ffaea08  
A6      : 0x00000000  A7      : 0x00000000  A8      : 0x00000000  A9      : 0x3ffb63b0  
A10     : 0x00000002  A11     : 0x3ffb63b0  A12     : 0xffffffff  A13     : 0x00000000  
A14     : 0x00000000  A15     : 0x00000001  SAR     : 0x00000017  EXCCAUSE: 0x0000001c  
EXCVADDR: 0x00000000  LBEG    : 0x4008cb7c  LEND    : 0x4008cb87  LCOUNT  : 0x00000000  


Backtrace: 0x401cae88:0x3ffb63b0 0x401baeae:0x3ffb63e0 0x401cb175:0x3ffb6410 0x401cb1d3:0x3ffb6430 0x401ba741:0x3ffb6480 0x4014582f:0x3ffb64a0 0x4011cd3e:0x3ffb64e0 0x4013e7f1:0x3ffb6590 0x400df15c:0x3ffb65b0 0x400d86ea:0x3ffb65d0 0x4018796e:0x3ffb6710




ELF file SHA256: a37be7bc3

Rebooting...
ets Jul 29 2019 12:21:46

firmware.elf.zip

[martin072]

Ok, update, I also had defined USE_MODBUS_BRIDGE_TCP when removed that it seems to work fine now.

Crashing during boot:

#define USE_MODBUS_BRIDGE                       
 #define USE_MODBUS_BRIDGE_TCP     
 #define MODBUS_BRIDGE_TCP_DEFAULT_PORT 502       

Working:

#define USE_MODBUS_BRIDGE                       
 //#define USE_MODBUS_BRIDGE_TCP     
 //#define MODBUS_BRIDGE_TCP_DEFAULT_PORT 502       

[martin072]

I would also like to use the modbus tcp functionality. Any chance one could have a look into the crash info to see where it could come from?