at the end of my rope. I retrieved this logger from my daughter's car where it had been logging for a year and attempted to re-program for different variables. No luck at all, tried v5 datalogger, never connects to OBD or makes any files on SD (used to work well on this car, 2005 explorer)
currently trying the SD_test.ino and result is always "card mount failed". the SD card works in my cpu, it's formatted as FAT16, 4G in size.
SD_test.ino periodically sends messages that the watchdog timer timed out too, not sure if it's related.
I'm almost thinking that there is a hardware issue at this point.
E (134) psram: PSRAM ID read error: 0xffffffff
E (134) spiram: SPI RAM enabled but initialization failed. Bailing out.
Card Mount Failed
E (66547) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (66547) task_wdt: - IDLE (CPU 1)
E (66547) task_wdt: Tasks currently running:
E (66547) task_wdt: CPU 0: IDLE
E (66547) task_wdt: CPU 1: loopTask
E (66547) task_wdt: Print CPU 0 (current core) backtrace
Backtrace:0x400DF3A3:0x3FFBE1D00x40082401:0x3FFBE200 0x400F843F:0x3FFBD400 0x400DF13F:0x3FFBD420 0x4008C263:0x3FFBD440
One+ model A will not mount SD or see OBDii
Re: One+ model A will not mount SD or see OBDii
FAT16 is not supported. Please use FAT32.
Re: One+ model A will not mount SD or see OBDii
FAT32 was the original SD, back to FAT32...
I have 2 SD cards freshly created and formatted as FAT32 with Diskpart, but they are not recognized by the ESP32
E (151) psram: PSRAM ID read error: 0xffffffff
E (151) spiram: SPI RAM enabled but initialization failed. Bailing out.
ESP32 80MHz 4MB Flash
MEMS:MPU-9250
SD:NO
OBD:NO
Standby
ACC Bias:-0.07/0.00/1.00
Port closed
I have 2 SD cards freshly created and formatted as FAT32 with Diskpart, but they are not recognized by the ESP32
E (151) psram: PSRAM ID read error: 0xffffffff
E (151) spiram: SPI RAM enabled but initialization failed. Bailing out.
ESP32 80MHz 4MB Flash
MEMS:MPU-9250
SD:NO
OBD:NO
Standby
ACC Bias:-0.07/0.00/1.00
Port closed
Re: One+ model A will not mount SD or see OBDii
Latest code? Did you re-compile libraries?
Re: One+ model A will not mount SD or see OBDii
got it from github, just a few days ago with Git GUI
trying v5 datalogger, and telelogger also in v5
builder ver is 1.2.1
tried lots of stuff, just rebuilt libs, (used default clock and 160MHZ clock) Rebuilt core also.
same result.
compiles, writes, but will not mount SD.
I was able to get the WIFI to connect to my CPU's hotspot with telelogger, but still no OBD or SD. is that a shared SPI bus?
trying v5 datalogger, and telelogger also in v5
builder ver is 1.2.1
tried lots of stuff, just rebuilt libs, (used default clock and 160MHZ clock) Rebuilt core also.
same result.
compiles, writes, but will not mount SD.
I was able to get the WIFI to connect to my CPU's hotspot with telelogger, but still no OBD or SD. is that a shared SPI bus?
Re: One+ model A will not mount SD or see OBDii
yes recompiled Libraries from these apps in v5.
datalogger
telelogger
I assume latest code since it came from github this week. cloned from here,
https://github.com/stanleyhuangyc/Freematics
looks like 3 months ago datalogger was updated.
datalogger
telelogger
I assume latest code since it came from github this week. cloned from here,
https://github.com/stanleyhuangyc/Freematics
looks like 3 months ago datalogger was updated.