32 posts / 0 new
Last post
inf0mike
inf0mike's picture
Modem not starting

I have recently bought an OVMS 3 module and an EU modem add on. When the vehicle module is booted, there is only limited chance that the modem module will also start up. This behaviour was seen when the unit was powered by usb during initial set up but I assumed that the external power requirements for the module were exceeding my USB supply however, the behaviour is exactly the same when powered from the OBD port after installation in the car.

Rebooting the unit will not cause it to start up.

I have also discovered that pressing the button on the modem module will cause it to start up correctly. Clearly pressing the button when the unit is installed in the car is not very convenient and I am sure this is not the expected behaviour.

Power cycling the vehicle module can also result in a correct startup but as noted earlier, it can take multiple tries to get it all up and running.

Has anyone experienced any startup issues with the modem module?

Any help would be appreciated.

dexter
dexter's picture
Modem not starting

Which firmware version is this?
Did you try updating the firmware?

Regards,
Michael

inf0mike
inf0mike's picture
I’m running 3.2.008-101

I’m running 3.2.008-101-ga8361db5/ota_0/main (build idf v3.3-beta3-774-g6652269e1 Dec 14 2019 12:02:50)

I think this is the latest released version.

I know there may be early access / bleeding edge versions but I thought I would try to keep to released versions wherever possible.

Do you know what function the button on the modem module performs?
Thanks,
Mike.

dexter
dexter's picture
Modem not starting

That's the current main release.

The button switches the modem on/off.

Please post a boot log (via USB terminal) with log level verbose for component "simcom".

inf0mike
inf0mike's picture
Thanks for taking an interest

Thanks for taking an interest. I will get set up for usb console and try to grab the boot logs as soon as I can.

inf0mike
inf0mike's picture
I finally got some time to

I finally got some time to investigate my modem startup issues. Here is the log as requested.

This was a soft reboot from when the unit was all working fine but the issue is the same on cold boot as well as soft reboot.

I think the modem has a timeout (simcom: State timeout, transition to 2) and then it gets power cycled and his power cycling continues indefinitely.

Sorry about all the CAN errors, the unit was out of the car while I was testing.

Thanks again,

Mike.

=== Log ===

rst:0xc (SW_CPU_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4796
load:0x40078000,len:0
load:0x40078000,len:14896
entry 0x40078d74
I (906) psram: This chip is ESP32-D0WD
I (906) spiram: Found 64MBit SPI RAM device
I (906) spiram: SPI RAM mode: flash 40m sram 40m
I (909) spiram: PSRAM initialized, cache is in low/high (2-core) mode.
I (916) cpu_start: Pro cpu up.
I (920) cpu_start: Application information:
I (925) cpu_start: Project name: ovms3
I (930) cpu_start: App version: 3.2.008-101-ga8361db5
I (936) cpu_start: Compile time: Dec 14 2019 12:02:47
I (942) cpu_start: ELF file SHA256: 156cd929e9fbd1e3...
I (948) cpu_start: ESP-IDF: v3.3-beta3-774-g6652269e1
I (955) cpu_start: Starting app cpu, entry point is 0x40081820
I (947) cpu_start: App cpu up.
I (1830) spiram: SPI SRAM memory test OK
I (1830) heap_init: Initializing. RAM available for dynamic allocation:
I (1830) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (1837) heap_init: At 3FFBED58 len 000212A8 (132 KiB): DRAM
I (1843) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (1849) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (1857) heap_init: At 4009918C len 00006E74 (27 KiB): IRAM
I (1862) cpu_start: Pro cpu start user code
I (1867) spiram: Adding pool of 4096K of external SPI memory to heap allocator
I (213) ovms_main: Set default logging level for * to INFO
I (214) command: Initialising COMMAND (1000)
I (215) boot: Initialising BOOT (1100)
I (218) boot: Boot #687280531 reasons for CPU0=12 and CPU1=12
I (225) boot: Reset reason Unknown reset reason (137425616)
I (231) boot: Soft reset by user
I (235) events: Initialising EVENTS (1200)
I (240) config: Initialising CONFIG (1400)
I (245) time: Initialising TIME (1500)
I (250) script: Initialising SCRIPTS (1600)
I (254) script: Using DUKTAPE javascript engine
I (260) metrics: Initialising METRICS (1810)
I (264) metrics: Expanding DUKTAPE javascript engine
I (274) notify: Initialising NOTIFICATIONS (1820)
I (276) notify: Registered notification type info
I (280) notify: Registered notification type error
I (286) notify: Registered notification type alert
I (291) notify: Registered notification type data
I (296) notify: Registered notification type stream
I (302) notify: Expanding DUKTAPE javascript engine
I (308) location: Initialising LOCATIONS (1900)
I (315) location: Expanding DUKTAPE javascript engine
I (319) vehicle: Initialising VEHICLE Factory (2000)
I (326) pcp: Initialising POWER (4000)
I (329) max7317: Initialising MAX7317 EGPIO (4200)
I (334) sdcard: Initialising SD CARD (4400)
I (339) ota: Initialising OTA (4400)
I (344) canformat: Initialising CAN Format Factory (4500)
I (349) canformat-crtd: Registering CAN Format: CRTD (4505)
I (356) canformat-gvret: Registering CAN Format: GVRET (4505)
I (362) canformat-lawricel: Registering CAN Format: LAWRICEL (4505)
I (369) canformat-pcap: Registering CAN Format: PCAP (4505)
I (375) canformat-raw: Registering CAN Format: RAW (4505)
I (381) can: Initialising CAN (4510)
I (388) dbc-app: Initialising DBC (4520)
I (391) canlog: Initialising CAN logging (4550)
I (396) canlog-monitor: Initialising CAN logging to MONITOR (4560)
I (402) canlog-tcpclient: Initialising CAN logging as TCP client (4560)
I (411) canlog-tcpserver: Initialising CAN logging as TCP server (4560)
I (418) canlog-vfs: Initialising CAN logging to VFS (4560)
I (423) canplay: Initialising CAN play framework (4570)
I (429) canplay-vfs: Initialising CAN playing from VFS (4580)
I (435) simcom: Initialising SIMCOM (4600)
I (441) test: Initialising TEST (5000)
I (445) module: Initialising MODULE (5100)
I (450) vfs: Initialising VFS (5200)
I (454) ovms-server: Initialising OVMS Server (6000)
I (459) ovms-server-v2: Initialising OVMS V2 Server (6100)
I (466) ovms-server-v3: Initialising OVMS V3 Server (6200)
I (472) obd2ecu: Initialising OBD2ECU (7000)
I (477) canopen: Initialising CANopen (7000)
I (483) esp32wifi: Initialising ESP32WIFI (8000)
I (487) ovms-mdns: Initialising MDNS (8100)
I (492) webserver: Initialising WEBSERVER (8200)
I (500) ssh: Initialising SSH (8300)
I (502) powermgmt: Initialising POWERMGMT (8500)
I (507) re: Initialising RE Tools (8800)
I (512) pushover: Initialising Pushover client (8800)
I (517) netmanager: Initialising NETMANAGER (8999)
I (526) v-zeva: Registering Vehicle: ZEVA (9000)
I (527) v-voltampera: Registering Vehicle: Volt/Ampera (9000)
I (534) v-track: Registering Vehicle: TRACK (9000)
I (539) v-thinkcity: Registering Vehicle: THINK CITY (9000)
I (546) v-teslaroadster: Registering Vehicle: Tesla Roadster (9000)
I (553) v-teslamodels: Registering Vehicle: Tesla Model S (9000)
I (559) v-teslamodel3: Registering Vehicle: Tesla Model 3 (9000)
I (566) v-smarteq: Registering Vehicle: SMART EQ (9000)
I (572) v-smarted: Registering Vehicle: SMART ED (9000)
I (578) v-zoe: Registering Vehicle: Renault Zoe (9000)
I (583) v-twizy: Registering Vehicle: Renault Twizy (9000)
I (590) v-obdii: Registering Vehicle: OBDII (9000)
I (595) v-none: Registering Vehicle: NONE (9000)
I (600) v-nissanleaf: Registering Vehicle: Nissan Leaf (9000)
I (607) v-mitsubishi: Registering Vehicle: Mitsubishi iMiEV, Citroen C-Zero, Peugeot iOn (9000)
I (616) v-kiasoulev: Registering Vehicle: Kia Soul EV (9000)
I (623) v-kianiroev: Registering Vehicle: Kia Niro / Hyundai Kona EV (9000)
I (630) v-fiat500e: Registering Vehicle: FIAT 500e (9000)
I (636) v-demo: Registering Vehicle: DEMO (9000)
I (642) vehicle_dbc: Registering Vehicle: DBC based vehicle (9000)
I (648) version: Initialising Versioning (9900)
I (658) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (0) script: Duktape: Scripting task is running
I (744) ovms_main: Executing on CPU core 0
I (744) ovms_main: Mounting CONFIG...
I (804) ovms_main: Configure logging...
I (814) ovms_main: Registering default configs...
I (844) ovms_main: Starting HOUSEKEEPING...
I (844) housekeeping: Initialising HOUSEKEEPING Framework...
I (1104) housekeeping: Executing on CPU core 1
I (1104) housekeeping: reset_reason: cpu0=12, cpu1=12
I (1104) housekeeping: Initialising WATCHDOG...
I (1114) housekeeping: Starting PERIPHERALS...
I (1114) peripherals: Initialising OVMS Peripherals...
I (1124) peripherals: TCP/IP Adaptor
I (1134) peripherals: ESP32 system
I (1134) peripherals: SPI bus
I (1134) peripherals: MAX7317 I/O Expander
I (1144) peripherals: ESP32 CAN
I (1144) peripherals: ESP32 WIFI
I (1154) peripherals: ESP32 ADC
I (1154) peripherals: MCP2515 CAN 1/2
I (1154) mcp2515: can2: SetPowerMode off
I (1244) peripherals: MCP2515 CAN 2/2
I (1244) mcp2515: can3: SetPowerMode off
I (1324) peripherals: SD CARD
I (1324) peripherals: SIMCOM MODEM
I (1324) gpio: GPIO[13]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (1334) gpio: GPIO[4]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (1344) uart: queue free spaces: 50
I (1344) ext12v: Powering off external 12V devices
I (1354) housekeeping: Auto init max7317 (free: 182264 bytes)
I (1354) housekeeping: Auto init ext12v (free: 182264 bytes)
I (1364) housekeeping: Auto init dbc (free: 182264 bytes)
I (1364) housekeeping: Auto init wifi (free: 182264 bytes)
I (1374) esp32wifi: Powering up WIFI driver
I (1394) wifi: wifi driver task: 3ffd45d0, prio:23, stack:3584, core=0
I (1394) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (1404) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (1424) wifi: wifi firmware version: aeed694
I (1424) wifi: config NVS flash: enabled
I (1424) wifi: config nano formating: disabled
I (1424) wifi: Init dynamic tx buffer num: 16
I (1434) wifi: Init data frame dynamic rx buffer num: 16
I (1434) wifi: Init management frame dynamic rx buffer num: 16
I (1444) wifi: Init management short buffer num: 32
I (1444) wifi: Init static rx buffer size: 2212
I (1454) wifi: Init static rx buffer num: 16
I (1454) wifi: Init dynamic rx buffer num: 16
I (2264) phy: phy_version: 4102, 2fa7a43, Jul 15 2019, 13:06:06, 0, 0
I (2264) wifi: mode : softAP (bc:dd:c2:d7:20:d9)
I (2264) wifi: Total power save buffer number: 8
I (2264) wifi: Init max length of beacon: 752/752
I (2274) wifi: Init max length of beacon: 752/752
I (2274) housekeeping: Auto init modem (free: 133312 bytes)
I (2284) simcom: State: Enter PoweringOn state
I (2284) simcom: Power Cycle
I (3294) housekeeping: Auto init vehicle (free: 132628 bytes)
I (3294) v-kianiroev: Kia Niro / Hyundai Kona EV v1.0 vehicle module
I (3304) housekeeping: Auto init obd2ecu (free: 121532 bytes)
I (3304) housekeeping: Auto init server v2 (free: 121532 bytes)
I (3314) ovms-server-v2: OVMS Server V2 registered metric modifier is #1
I (3314) ovms-server-v2: Status: Server has been started
I (3324) ovms-server-v2: OVMS Server v2 running
I (3334) housekeeping: Auto init server v3 (free: 121424 bytes)
I (3334) housekeeping: Auto init javascript (free: 121424 bytes)
I (3344) housekeeping: Auto init done (free: 121424 bytes)
I (3344) housekeeping: Starting USB console...
I (3354) uart: queue free spaces: 100

Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console
Firmware: 3.2.008-101-ga8361db5/ota_0/main
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1

OVMS> I (3374) script: Duktape: Creating heap
I (3374) script: Duktape: Initialising module system
OVMS> E (3644) can: can1: intr=5 rxpkt=0 txpkt=0 errflags=0x8000a2 rxerr=37 txerr=0 rxovr=0 txovr=0 txdelay=0 wdgreset=0 errreset=0
E (3644) can: can1: intr=29 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=0 wdgreset=0 errreset=0
I (3654) simcom: State: Enter PoweredOn state
I (3674) netmanager: WIFI access point is up
I (3684) esp32wifi: AP started with SSID: G4CPU, MAC: bc:dd:c2:d7:20:d9, IP: 192.168.4.1
E (3704) can: can1: intr=772 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=1 wdgreset=0 errreset=0
I (3744) ovms-mdns: Starting MDNS
I (3774) webserver: Launching Web Server
I (3784) ssh: Launching SSH Server
OVMS> E (4104) can: can1: intr=6644 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=2 wdgreset=0 errreset=0
OVMS> E (5104) can: can1: intr=21343 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=3 wdgreset=0 errreset=0
OVMS> I (6104) sdcard: SD CARD has been inserted
I (6144) sdcard: mount done
E (6144) can: can1: intr=36666 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=4 wdgreset=0 errreset=0
OVMS> E (7104) can: can1: intr=50753 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=5 wdgreset=0 errreset=0
OVMS> E (8104) can: can1: intr=65462 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=6 wdgreset=0 errreset=0
OVMS> E (9104) can: can1: intr=80165 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=7 wdgreset=0 errreset=0
OVMS> E (10104) can: can1: intr=94871 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=8 wdgreset=0 errreset=0
OVMS> E (11104) can: can1: intr=109577 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=9 wdgreset=0 errreset=0
I (11104) housekeeping: System considered stable (RAM: 8b=81844-82404 32b=27560)
OVMS> E (12104) can: can1: intr=124301 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=10 wdgreset=0 errreset=0
OVMS> E (13104) can: can1: intr=138988 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=11 wdgreset=0 errreset=0
OVMS> E (14104) can: can1: intr=153702 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=12 wdgreset=0 errreset=0
OVMS> E (15104) can: can1: intr=168399 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=13 wdgreset=0 errreset=0
OVMS> E (16104) can: can1: intr=183103 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=14 wdgreset=0 errreset=0
OVMS> E (17104) can: can1: intr=197819 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=15 wdgreset=0 errreset=0
OVMS> E (18104) can: can1: intr=212525 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=16 wdgreset=0 errreset=0
OVMS> E (19104) can: can1: intr=227232 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=17 wdgreset=0 errreset=0
OVMS> E (20104) can: can1: intr=241940 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=18 wdgreset=0 errreset=0
OVMS> E (21104) can: can1: intr=256645 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=19 wdgreset=0 errreset=0
OVMS> E (22104) can: can1: intr=271349 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=0 txdelay=20 wdgreset=0 errreset=0
OVMS> E (23104) can: can1: intr=286045 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=1 txdelay=20 wdgreset=0 errreset=0
OVMS> E (31104) can: can1: intr=403690 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=2 txdelay=20 wdgreset=0 errreset=0
OVMS> I (32104) simcom: State timeout, transition to 2
I (32104) simcom: State: Enter PoweringOn state
I (32104) simcom: Power Cycle
OVMS> E (33104) can: can1: intr=433161 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=3 txdelay=20 wdgreset=0 errreset=0
E (33124) can: can1: intr=433454 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=4 txdelay=20 wdgreset=0 errreset=0
I (33134) simcom: State: Enter PoweredOn state
OVMS> E (36104) can: can1: intr=477216 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=5 txdelay=20 wdgreset=0 errreset=0
OVMS> E (37104) can: can1: intr=491924 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=6 txdelay=20 wdgreset=0 errreset=0
OVMS> E (39104) can: can1: intr=521336 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=7 txdelay=20 wdgreset=0 errreset=0
OVMS> E (40104) can: can1: intr=536041 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=8 txdelay=20 wdgreset=0 errreset=0
OVMS> E (42104) can: can1: intr=565453 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=9 txdelay=20 wdgreset=0 errreset=0
OVMS> E (43104) can: can1: intr=580178 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=10 txdelay=20 wdgreset=0 errreset=0
OVMS> E (46104) can: can1: intr=624277 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=11 txdelay=20 wdgreset=0 errreset=0
OVMS> E (47104) can: can1: intr=638983 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=12 txdelay=20 wdgreset=0 errreset=0
OVMS> E (49104) can: can1: intr=668406 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=13 txdelay=20 wdgreset=0 errreset=0
OVMS> E (50104) can: can1: intr=683121 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=14 txdelay=20 wdgreset=0 errreset=0
OVMS> E (51104) can: can1: intr=697819 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=15 txdelay=20 wdgreset=0 errreset=0
OVMS> E (56104) can: can1: intr=771333 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=16 txdelay=20 wdgreset=0 errreset=0
OVMS> E (57104) can: can1: intr=786041 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=17 txdelay=20 wdgreset=0 errreset=0
OVMS> E (59104) can: can1: intr=815453 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=18 txdelay=20 wdgreset=0 errreset=0
OVMS> E (61104) can: can1: intr=844864 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=19 txdelay=20 wdgreset=0 errreset=0
I (61124) script: Duktape: Compacting DukTape memory
OVMS> E (62104) can: can1: intr=859582 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=20 txdelay=20 wdgreset=0 errreset=0
I (62104) v-kianiroev: NO CLIENTS. Turning off polling.
OVMS> I (63104) simcom: State timeout, transition to 2
I (63104) simcom: State: Enter PoweringOn state
I (63104) simcom: Power Cycle
OVMS> E (64104) can: can1: intr=889036 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=21 txdelay=20 wdgreset=0 errreset=0
E (64124) can: can1: intr=889270 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=22 txdelay=20 wdgreset=0 errreset=0
I (64134) simcom: State: Enter PoweredOn state
OVMS> I (68524) wifi: new:<1,1>, old:<1,0>, ap:<1,1>, sta:<255,255>, prof:1
I (68524) wifi: station: 24:77:03:25:02:44 join, AID=1, bgn, 40U
I (68564) esp32wifi: AP station connected: id: 1, MAC: 24:77:03:25:02:44
I (68574) tcpip_adapter: softAP assign IP to station,IP is: 192.168.4.2
I (68654) webserver: HTTP GET /
OVMS> I (68984) webserver: HTTP GET /status
OVMS> E (72104) can: can1: intr=1006619 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=23 txdelay=20 wdgreset=0 errreset=0
OVMS> E (75104) can: can1: intr=1050735 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=24 txdelay=20 wdgreset=0 errreset=0
OVMS> E (81104) can: can1: intr=1138977 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=25 txdelay=20 wdgreset=0 errreset=0
OVMS> I (81444) webserver: HTTP POST /status
I (81444) webserver: HandleLogin: 'admin' logged in, sid ddb5a86375860088
I (81474) webserver: HTTP GET /menu
I (81494) webserver: HTTP GET /status
OVMS> E (86104) can: can1: intr=1212499 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=26 txdelay=20 wdgreset=0 errreset=0
OVMS> E (90104) can: can1: intr=1271322 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=27 txdelay=20 wdgreset=0 errreset=0
OVMS> I (92494) webserver: HTTP GET /cfg/modem
OVMS> I (94104) simcom: State timeout, transition to 2
I (94104) simcom: State: Enter PoweringOn state
I (94104) simcom: Power Cycle
OVMS> I (95134) simcom: State: Enter PoweredOn state
OVMS> E (97104) can: can1: intr=1374255 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=28 txdelay=20 wdgreset=0 errreset=0
OVMS> E (99104) can: can1: intr=1403666 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=29 txdelay=20 wdgreset=0 errreset=0
OVMS> E (107104) can: can1: intr=1521320 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=30 txdelay=20 wdgreset=0 errreset=0
OVMS> E (109104) can: can1: intr=1550720 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=31 txdelay=20 wdgreset=0 errreset=0
OVMS> I (113594) webserver: HTTP POST /api/execute
I (113604) webcommand: HttpCommandStream[0x3f82b660]: 4063096 bytes free, executing: power simcom on
OVMS> E (116104) can: can1: intr=1653657 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=32 txdelay=20 wdgreset=0 errreset=0
OVMS> E (120104) can: can1: intr=1712477 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=33 txdelay=20 wdgreset=0 errreset=0
OVMS> I (121114) script: Duktape: Compacting DukTape memory
OVMS> I (125104) simcom: State timeout, transition to 2
I (125104) simcom: State: Enter PoweringOn state
I (125104) simcom: Power Cycle
OVMS> E (126104) can: can1: intr=1800765 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=34 txdelay=20 wdgreset=0 errreset=0
I (126134) simcom: State: Enter PoweredOn state
OVMS> E (131104) can: can1: intr=1874246 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=35 txdelay=20 wdgreset=0 errreset=0
OVMS> E (134104) can: can1: intr=1918354 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=36 txdelay=20 wdgreset=0 errreset=0
OVMS> E (142104) can: can1: intr=2036009 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=37 txdelay=20 wdgreset=0 errreset=0
OVMS> E (143104) can: can1: intr=2050715 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=38 txdelay=20 wdgreset=0 errreset=0
OVMS> E (151104) can: can1: intr=2168346 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=39 txdelay=20 wdgreset=0 errreset=0
OVMS> E (154104) can: can1: intr=2212464 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=40 txdelay=20 wdgreset=0 errreset=0
OVMS> I (156104) simcom: State timeout, transition to 2
I (156104) simcom: State: Enter PoweringOn state
I (156104) simcom: Power Cycle
OVMS> I (157144) simcom: State: Enter PoweredOn state
OVMS> I (158434) webserver: HTTP GET /cfg/modem
OVMS> E (160104) can: can1: intr=2300692 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=41 txdelay=20 wdgreset=0 errreset=0
OVMS> I (161544) webserver: HTTP GET /cfg/password
OVMS> I (163234) webserver: HTTP GET /cfg/modem
OVMS> E (165104) can: can1: intr=2374223 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=42 txdelay=20 wdgreset=0 errreset=0
OVMS> I (167064) webserver: HTTP GET /status
OVMS> E (169104) can: can1: intr=2433049 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=43 txdelay=20 wdgreset=0 errreset=0
OVMS> E (176104) can: can1: intr=2535990 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=44 txdelay=20 wdgreset=0 errreset=0
OVMS> E (178104) can: can1: intr=2565388 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=45 txdelay=20 wdgreset=0 errreset=0
OVMS> I (181114) script: Duktape: Compacting DukTape memory
OVMS> E (186104) can: can1: intr=2683033 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=46 txdelay=20 wdgreset=0 errreset=0
OVMS> I (187104) simcom: State timeout, transition to 2
I (187104) simcom: State: Enter PoweringOn state
I (187104) simcom: Power Cycle
OVMS> E (188124) can: can1: intr=2712709 rxpkt=0 txpkt=0 errflags=0x8040a2 rxerr=135 txerr=0 rxovr=0 txovr=47 txdelay=20 wdgreset=0 errreset=0
I (188124) simcom: State: Enter PoweredOn state
OVMS> I (188354) webserver: HTTP POST /api/execute
I (188354) webcommand: HttpCommandStream[0x3f82b570]: 4087168 bytes free, executing: simcom status
I (188374) webserver: HTTP POST /api/execute
I (188384) webcommand: HttpCommandStream[0x3f8284a0]: 4076620 bytes free, executing: simcom status

dexter
dexter's picture
Modem not starting

Almost.

You forgot this: …with log level verbose for component "simcom".

You can also set the vehicle type to "Track" to avoid the CAN errors.

dexter
dexter's picture
Modem not starting

Btw, as this only affects your module, you can open a support ticket to also easily & securely upload logs.

inf0mike
inf0mike's picture
For reasons that I cannot

For reasons that I cannot explain, I am no longer experiencing any issues with the modem startup.

I have regularly powered down the unit over the last week and each time it is powered on again, the modem is starting up every time. I will continue to monitor the situation.

green_fox
Apparently I am having the

Apparently I am having the same issues. Modem was working fine when connected to USB, but it won't start when the power comes from the car. The blue led does blink slowly though. Dexter already mentioned that this might be an issue with the 12V converter, are there measuring points on the mainboard where this can be checked?

Kiaeniro
I have the same problem, has

I have the same problem, has it resolved for you?

Lucko
Same or similar problem...

I'm also having problems with modem(EU). It is also problem if the car connects to wireless. It happens also when I get out of range of Wireless signal car will no connect. Not sure if modem is turn of when you are connected to wireless. But then again it could be just modem stop working... It happens to. And even clicking on Start Modem will not turn it on every time. Sometimes I just have to unplug it and then it might work or it might not. When I installed it about 40 days ago I did update firmware to the latest... It looks like this is not isolated problem. It could be a problem with new batch.

rtobler
Same problem here...

I installed the module a few days ago with no issues, modem was connected fine. Module was off for a few days and when I wanted to install today the modem did not start. Could anyone resolve it yet?

I'm also on the newest firmware installed few days ago (v3.3-beta3-774-g6652269e1

rtobler
Same problem here...

I installed the module a few days ago with no issues, modem was connected fine. Module was off for a few days and when I wanted to install today the modem did not start. Could anyone resolve it yet?

I'm also on the newest firmware installed few days ago (v3.3-beta3-774-g6652269e1

Shambalic
Shambalic's picture
Same problem here..

Same problem here..

rtobler
I fixed it for me: I reset

I fixed it for me: I reset the module to factory settings. As soon as i activated power management features issues started. Reset again and did not activate power management: fixed!

tyrons
I have the same issue. it

I have the same issue. it seemed happen after last update or maybe because cars are sitting for longer without been plugged in. modem starts up correctly when plugged into usb. I disabled power management but did not resolve it

 

tyrons
I have the same issue.

I have the same issue. it seemed to happen after last update or maybe because cars are sitting for longer without been plugged in. modem starts up correctly when plugged into usb. I disabled power management and reboot but did not resolve it. going to reset and start again without power management nissan leaf 2011 gen1

 

tyrons
modem not working stuck on powering up

I did a factory reset and did not activate battery management. eu modem only starts up on usb not while conencted to car. stuck on powering up

 

dexter
dexter's picture
Modem not starting

The power management module has been designed to shut down the modem if you don't charge the car for the time configured.
So you need to set this to some reasonable time for your charging routine.

Is this potentially the reason for the other users here as well?

rtobler
Thanks dexter, would that

Thanks dexter, would that also mean than when its sitting on my desk with USB power that it would not enable the modem?

dexter
dexter's picture
Modem not starting

No. If you cannot start the modem from USB power, the USB port probably is too weak. Use a powered hub.

JMK2020
Similar situation for me.

Similar situation for me.

I discussed this direct with Marc as i also had some issues with the soldering and fall off of the USB connector. I checked the behavior before with strong USB supply working. Power via obd not working. It seems to me the power supply produce some noise. Maybe if there is a peak load. I just had the thought of a caused issue by the SDFlash card. Could you check it with and without? My HW is on the way back to Hongkong for repair.:-(

i will check when the HW is back.

 

In my view the timeout or more brownout of voltage is not the reason. But I donnot have the time to check it with my equipment in the lab by corona :-(

I also will dig in deeper. Yesterday I installed the ESP32 Tool chain for programming.

I hope to start to support Thomas on the Smart ED3 version. I had some nice ideas ;-)

JMK

green_fox
I ran into the same problem

I ran into the same problem today, no modem and no gps fix, last time I replaced the OVMS (since I broke off the usb port) and everything was fine until today. It might be though that the modem went to sleep since the power management might have activated, my last charge was a few days ago since I was on holiday. I will recharge the Twizy tonight and see if I can get the modem back online, a soft reboot and unplugging and replugging did not help so far though. 

Edit: I just saw that Power Management is disabled, I will charge the Twizy anyway though and see what will happen. If this won't help I'll do a factory reset and see what will happen then. 

SteveDSD (not verified)
Yeah I'm having the same

Yeah I'm having the same issue since the last release - 

W (3128036) simcom: UART hw fifo overflow

W (3140886) gsm-mux: Frame overflow (2048 bytes)

beewatcherwatcher
Similar modem problem

I'm experiencing a similar problem with the US version of the modem.  It has worked, but currently seems to be stuck in an endless repeat of the log output below.  Firmware is 3.2.014/ota_1/main (build idf v3.3.2-881-g22d636b Aug  4 2020 16:26:20)

D (1838078) simcom: tx scmd ch=0 len=4   : AT
V (1839078) simcom: tx: 41 54 0d 0a                                     | AT..            
D (1839078) simcom: tx scmd ch=0 len=4   : AT
V (1840078) simcom: tx: 41 54 0d 0a                                     | AT..            
D (1840078) simcom: tx scmd ch=0 len=4   : AT
V (1841078) simcom: tx: 41 54 0d 0a                                     | AT..            
D (1841078) simcom: tx scmd ch=0 len=4   : AT
I (1841078) simcom: State timeout, transition to 2
I (1841078) simcom: State: Enter PoweringOn state
I (1841078) simcom: Power Cycle
D (1841078) max7317: egpio.output.0.high
D (1842078) max7317: egpio.output.0.low
D (1842098) events: Signal(system.modem.poweringon)
D (1842098) events: Signal(egpio.output.0.high)
V (1842108) simcom: tx: 41 54 0d 0a                                     | AT..            
D (1842108) simcom: tx scmd ch=0 len=4   : AT
D (1842118) events: Signal(egpio.output.0.low)
V (1843078) simcom: tx: 41 54 0d 0a                                     | AT..            
D (1843078) simcom: tx scmd ch=0 len=4   : AT

markwj
markwj's picture
Just to re-enforce the point:

Just to re-enforce the point: laptop/computer USB 2.0 ports will typically not supply enough power to run the OVMS module and modem.

We suggest to try with a powered USB hub, USB 3.0 port, a wall plug style USB power adaptor, or 12V in the car.

beewatcherwatcher
Modem stuck in PoweringOn regardless of power source

I've tried powering the OVMS board + US Modem through a variety of USB hubs and chargers, as well as the vehicle's OBDII port, and I have never been able to get the modem to function.  It appears to start with a "simcom setstate PowerOn" command, then after a minute transitions to a "PoweringOn" state indefinitely.  Firmware: 3.2.015/ota_0/main (build idf v3.3.2-881-g22d636b7b Sep 2 2020 08:32:35).  Verbose log output follows:

I (117941) webcommand: HttpCommandStream[0x3f84ffa8]: 3947636 bytes free, executing: simcom setstate PoweredOff
I (117941) simcom: State: Enter PoweredOff state
D (117951) events: Signal(system.modem.poweredoff)
I (117951) gsm-mux: Stop MUX
D (121091) script: Duktape: Compacting DukTape memory
V (123081) esp32wifi: StartConnect: scan started
D (125531) events: Signal(system.event)
D (125531) events: Signal(system.wifi.scan.done)
V (125531) esp32wifi: EventWifiScanDone: no access points found
V (133081) esp32wifi: StartConnect: scan started
I (134411) webserver: HTTP POST /api/execute
I (134431) webcommand: HttpCommandStream[0x3f840350]: 3977512 bytes free, executing: simcom setstate PoweredOn
OVMS# simcom setstate PoweredOn
I (134431) simcom: State: Enter PoweredOn state
D (134431) events: Signal(system.modem.poweredon)
D (135531) events: Signal(system.event)
D (135531) events: Signal(system.wifi.scan.done)
V (135531) esp32wifi: EventWifiScanDone: no access points found
V (143081) esp32wifi: StartConnect: scan started
V (144081) simcom: tx: 41 54 2b 43 50 49 4e 3f 3b 2b 43 52 45 47 3d 31 | AT+CPIN?;+CREG=1
V (144081) simcom: tx: 3b 2b 43 54 5a 55 3d 31 3b 2b 43 54 5a 52 3d 31 | ;+CTZU=1;+CTZR=1
V (144081) simcom: tx: 3b 2b 43 4c 49 50 3d 31 3b 2b 43 4d 47 46 3d 31 | ;+CLIP=1;+CMGF=1
V (144081) simcom: tx: 3b 2b 43 4e 4d 49 3d 31 2c 32 2c 30 2c 30 2c 30 | ;+CNMI=1,2,0,0,0
V (144081) simcom: tx: 3b 2b 43 53 44 48 3d 31 3b 2b 43 4d 45 45 3d 32 | ;+CSDH=1;+CMEE=2
V (144081) simcom: tx: 3b 2b 43 53 51 3b 2b 41 55 54 4f 43 53 51 3d 31 | ;+CSQ;+AUTOCSQ=1
V (144081) simcom: tx: 2c 31 3b 45 30 3b 53 30 3d 30 0d 0a             | ,1;E0;S0=0..    
D (144081) simcom: tx scmd ch=0 len=108 : AT+CPIN?;+CREG=1;+CTZU=1;+CTZR=1;+CLIP=1;+CMGF=1;+CNMI=1,2,0,0,0;+CSDH=1;+CMEE=2;+CSQ;+AUTOCSQ=1,1;E0;S0=0
D (145531) events: Signal(system.event)
D (145531) events: Signal(system.wifi.scan.done)
V (145531) esp32wifi: EventWifiScanDone: no access points found
V (146081) simcom: tx: 41 54 2b 43 47 4d 52 3b 2b 49 43 43 49 44 0d 0a | AT+CGMR;+ICCID..
D (146081) simcom: tx scmd ch=0 len=16  : AT+CGMR;+ICCID
V (149081) simcom: tx: 41 54 2b 43 4f 50 53 3f                         | AT+COPS?        
D (149081) simcom: tx scmd ch=0 len=8   : AT+COPS?
V (150081) simcom: tx: 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 33 | AT+CMUXSRVPORT=3
V (150081) simcom: tx: 2c 31 0d 0a                                     | ,1..            
D (150081) simcom: tx scmd ch=0 len=20  : AT+CMUXSRVPORT=3,1
V (151081) simcom: tx: 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 32 | AT+CMUXSRVPORT=2
V (151081) simcom: tx: 2c 31 0d 0a                                     | ,1..            
D (151081) simcom: tx scmd ch=0 len=20  : AT+CMUXSRVPORT=2,1
V (152081) simcom: tx: 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 31 | AT+CMUXSRVPORT=1
V (152081) simcom: tx: 2c 31 0d 0a                                     | ,1..            
D (152081) simcom: tx scmd ch=0 len=20  : AT+CMUXSRVPORT=1,1
V (153081) esp32wifi: StartConnect: scan started
V (153081) simcom: tx: 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 30 | AT+CMUXSRVPORT=0
V (153081) simcom: tx: 2c 35 0d 0a                                     | ,5..            
D (153081) simcom: tx scmd ch=0 len=20  : AT+CMUXSRVPORT=0,5
V (154081) simcom: tx: 41 54 2b 43 4d 55 58 3d 30 0d 0a                | AT+CMUX=0..     
D (154081) simcom: tx scmd ch=0 len=11  : AT+CMUX=0
D (155531) events: Signal(system.event)
D (155531) events: Signal(system.wifi.scan.done)
V (155531) esp32wifi: EventWifiScanDone: no access points found
V (163081) esp32wifi: StartConnect: scan started
I (164081) simcom: State timeout, transition to 2
I (164081) simcom: State: Enter PoweringOn state
I (164081) simcom: Power Cycle
D (164081) max7317: egpio.output.0.high
D (165081) max7317: egpio.output.0.low
D (165081) events: Signal(system.modem.poweringon)
D (165091) events: Signal(egpio.output.0.high)
V (165091) simcom: tx: 41 54 0d 0a                                     | AT..            
D (165091) simcom: tx scmd ch=0 len=4   : AT
D (165091) events: Signal(egpio.output.0.low)
D (165531) events: Signal(system.event)
D (165531) events: Signal(system.wifi.scan.done)
V (165531) esp32wifi: EventWifiScanDone: no access points found
V (166081) simcom: tx: 41 54 0d 0a                                     | AT..            
D (166081) simcom: tx scmd ch=0 len=4   : AT
V (167081) simcom: tx: 41 54 0d 0a                                     | AT..            

dexter
dexter's picture
Modem stuck in PoweringOn regardless of power source

This looks like a hardware issue to me.

Setting the state to "PoweredOn" isn't meant to power on the modem, so your actual power on sequence only begins at timestamp 164081.

To power on the modem normally, do "power simcom on" or "simcom setstate PoweringOn".

Do this with an open case so you can see if the blue LED on the modem shows activity.

You might try removing and reinserting the modem board to check for contact issues. Be gentle, ask an electronics guy/gal for help if in doubt.

Regards,
Michael

beewatcherwatcher
Hardware issue with power delivery to modem?

Thanks for your guidance Michael.  And I apologize for my ham-handed approach to powering on and off the modem -- I was hoping some of that initial log output meant something.

I opened the case and cannot see a blue light on the modem when powered on.  I removed and re-seated the modem and still cannot see a blue light or any activity from the modem.  Indeed, I see exactly the same errors in the log output whether the modem is installed or removed, just as you'd expect if it was not getting power.

You are likely correct about there being a hardware issue.  The modem did work for me once when I first used it, but has not functioned since that first fleeting success.  Is there a way to troubleshoot the hardware or should I resign myself to getting a new board?

Xrigcd357ffs
simcom: Modem not responding after PoweringOn state

I have a quite similar issue.

The modem apparently not responding after powering on. It stays at tx "AT..." .

This occures only if the powersupply is the 12VDC. Powering from USB it is working properly.

Unfortunetelly this lead to drain the 12VDC battery in the car.

I measured on the board the power for the modem itself is OK.  egpio.output.0 is also OK.


1970-01-01 01:04:35 CET V (199820) simcom: tx: 41 54 0d 0a                                     | AT..            
1970-01-01 01:04:35 CET D (199820) simcom: tx scmd ch=0 len=4   : AT
1970-01-01 01:04:35 CET I (199820) simcom: State timeout, transition to 2
1970-01-01 01:04:35 CET I (199820) simcom: State: Enter PoweringOn state
1970-01-01 01:04:35 CET I (199820) simcom: Power Cycle
1970-01-01 01:04:35 CET D (199820) max7317: egpio.output.0.high
1970-01-01 01:04:36 CET D (200820) max7317: egpio.output.0.low
1970-01-01 01:04:36 CET D (200820) events: Signal(system.modem.poweringon)
1970-01-01 01:04:36 CET D (200830) events: Signal(egpio.output.0.high)
1970-01-01 01:04:36 CET V (200830) simcom: tx: 41 54 0d 0a                                     | AT..            
1970-01-01 01:04:36 CET D (200830) simcom: tx scmd ch=0 len=4   : AT
1970-01-01 01:04:36 CET V (200830) v-nissanleaf: Range: ideal=0 km, est=0 km, full=170 km
1970-01-01 01:04:36 CET D (200830) v-nissanleaf: Poll state: 0
1970-01-01 01:04:36 CET D (200840) events: Signal(egpio.output.0.low)
1970-01-01 01:04:37 CET I (201100) webserver: HTTP POST /api/execute
1970-01-01 01:04:37 CET I (201140) webcommand: HttpCommandStream[0x3f845b60]: 3972476 bytes free, executing: simcom status
1970-01-01 01:04:37 CET V (201820) simcom: tx: 41 54 0d 0a                                     | AT..            
1970-01-01 01:04:37 CET D (201820) simcom: tx scmd ch=0 len=4   : AT
1970-01-01 01:04:38 CET V (202820) simcom: tx: 41 54 0d 0a                                     | AT..            
1970-01-01 01:04:38 CET D (202820) simcom: tx scmd ch=0 len=4   : AT
1970-01-01 01:04:39 CET V (203820) simcom: tx: 41 54 0d 0a                                     | AT..            
1970-01-01 01:04:39 CET D (203820) simcom: tx scmd ch=0 len=4   : AT
 

 

Regards:

Jeno

smetana.przemys...
I also have a problem with

I also have a problem with the modem.
I solved it as follows:
1. I have set OVMS to AP + client
2. I connected OVMS via WI-FI to a mobile router, making the internet available to OVMS
3. I connected the mobile router to the powerbank and then the powerbank to the cigarette lighter socket.

In this way, I bypassed the nerves associated with the modem at no cost.

So far everything works fine.

Log in or register to post comments