Autosport Labs

Had a working config for a '99 Spec Miata, OEM ECU. Loaded 2.13 beta firmware. Loaded saved config from 2.12. Running the app on a Fire 6 as it will easily fit on my existing Traqmate dash mount. First thing I saw was that the ODB2 links weren't working. Started messing around with them, got bored and tried to setup the wifi client so that the Fire 6 would automatically connect as this unit is destined for my very non-tech buddy's car. The less buttons to push the better. Used a free app called WIFI Hotspot. Got it to connect and then had some trouble reconnecting. Connected the track via USB to remove the client wifi. App said it was gone but couldn't get wifi back. The unit was sending out a signal but nothing would connect to it. Status said Not Initialized. Reloaded 2.13 firmware, no change. Cycled power after just about every attempt. Reloaded 2.12 firmware and old config and everything is perfect again. Anyone else having these issues?

Hi,

Thanks for this report.

When you have a moment, can you load 2.13.0 back to the unit and do a check for the WiFi functionality?

No need to load a saved config, just check with the default config.

Right after powering up via USB, grab the RaceCapture log using the instructions here:
https://wiki.autosportlabs.com/RaceCapt ... apture_Log

This should show some information about the firmware initializing the Wifi sub-system - paste the log as a reply here.

Thanks!

Hi,

I think we found the issue. In some cases, the WiFi module we use inside RaceCapture/Track takes a bit longer to initialize, and we may start trying to communicate with it too early.

I've attached potential fix; could you try it out and report back?

Thanks!

Sorry Brent, just saw your response. Reflashed 2.13 and got the same thing, Wifi not initialized. Here's the startup log. Should I download the 2.13 flash again and retry? EDIT - Couldn't see your attachment as I hadn't logged in. Will try it now.

*** Start! ***
[watchdog] Initializing...
[watchdog] Detected watchdog reset!
sizeof

LoggerConfig: 3116
[CAN device] Initializing CAN0 with baud rate 500000
[CAN

device] CAN init success!
IMU: init res=0
GPS: Initializing...
[OBD2] Init current

values
timebase/logging/telemetry sample rate: 50/25/25
[wifi] Initializing...
GPS:

provisioning attempt
GPS: probing baud rate: 921600
[ESP8266 Driver] Client config

unchanged by update
[main] Setup Task complete!
[ESP8266 Driver] Checking WiFi

Device...
[ESP8266 Driver] Initializing Wifi
[USB] Starting telem stream on USB
GPS:

probing baud rate: 115200
GPS: Using baud rate: 115200
GPS: module detected at:

115200
GPS: detected current update rate: 10
GPS: Configuring NMEA messages
GPS:

Message was successfully received.
GPS: Successfully configured NMEA
GPS: configure

message type: win
GPS: configure navigation data message interval: win
GPS:

Configuring Gnss Navigation Mode: win
GPS: Disabling NMEA messages
GPS: Message was

successfully received.
GPS: Successfully disabled NMEA messages
GPS: provisioned
[at] Command timed out
[esp8266] Init failed with msg: Soft reset failed.
[ESP8266

Driver] Initialization failed
[ESP8266 Driver] Checking WiFi Device...
[ESP8266

Driver] Initializing Wifi
[at] Command timed out
[esp8266] Init failed with msg:

Soft reset failed.
[ESP8266 Driver] Initialization failed
[ESP8266 Driver] Checking

WiFi Device...
[ESP8266 Driver] Initializing Wifi
[at] Command timed out
[esp8266]

Init failed with msg: Soft reset failed.
[ESP8266 Driver] Too many failures.

Resetting...
[ESP8266 Driver] Initialization failed
[ESP8266 Driver] Checking WiFi

Device...
[ESP8266 Driver] Initializing Wifi

Now it communicates just fine. But when I try to write the working config file from the 2.12 setup I get 3/4 of the way through it and then get an error "Timeout waiting for setTrackCfg".

Is the config file I made under 21.12 not compatible with 2.13?

[Edit] Tried setting up a config under 2.13. Can't get any of the legacy ODB2 inputs to work. Had IAT, TPS and RPM working fine under 2.12.

Hi,

Not following you 100%. Let's go 1 at a time.

The test firmware I attached, is it working now with your WiFi?

Yes.

Great! For OBDII, try removing all of your channels and then add them back in one at a time, testing in-between.

Also make sure your CAN baud rate is set to 500K.

Can Bus on, 500k baud, Can Mapping off, ODB2 on. Loaded IAT, TPS & RPM

Nothing.
Shut everything down, rebooted, still nothing.

Thanks. Can you save your configuration to a file and attach it here? We'll try to reproduce it on our end.

Also, after saving your configuration, you might as well peek at the RaceCapture Log to see what kind of messages it's outputting right after power up and attempting to read OBDII channels. https://wiki.autosportlabs.com/RaceCapt ... apture_Log

OK, will do first thing tomorrow. Gotta run.

Brent -

Attached is a copy of my config file and the startup log.
I've removed the .rcp and made it a .txt file as the forum software won't let me upload an rcp file.
The logs show it just keeps trying to poll the ODB2 modes.

hannel 0
[ESP8266 Driver] Connected on comm channel 0
[OBD2] Trying OBDII bit mode 11
GPS: probing baud rate: 115200
GPS: Using baud rate: 115200
GPS: module detected at: 115200
GPS: detected current update rate: 10
GPS: Configuring NMEA messages
GPS: Message was successfully received.
GPS: Successfully configured NMEA
GPS: configure message type: win
GPS: configure navigation data message interval: win
GPS: Configuring Gnss Navigation Mode: win
GPS: Disabling NMEA messages
GPS: Message was successfully received.
GPS: Successfully disabled NMEA messages
GPS: provisioned
[OBD2] Trying OBDII bit mode 29
[OBD2] Trying OBDII bit mode 11
[OBD2] Trying OBDII bit mode 29
[OBD2] Trying OBDII bit mode 11
[OBD2] Trying OBDII bit mode 29
[OBD2] Trying OBDII bit mode 11
[OBD2] Trying OBDII bit mode 29
[OBD2] Trying OBDII bit mode 11
[ESP8266 Driver] Socket connected on channel 1
[wifi] New external connection: Wifi Chan 1
[wifi] Starting telem stream on Wifi Chan 1
[lapstats] Using track config 0

Thanks, looking at it right now.

What year/make/model is the car you're testing on?

1999 Mazda Miata

Thanks. So, if you revert back to 2.12.0 firmware, does OBDII immediately start working properly?