Autosport Labs

I just solved this myself. It's likely that you need to add your user to the dialout group to get access to the serial port.

Looks like it was a permissions issue, even though my user is in the dialout group.
This fixed it for me and now I can talk to the RCP!

Edit, adding my user to the dialout group did work, I just forgot to log out and back in after.

Due to a series of events, and a serious ass kicking at Solo Nationals, I'd like to get the datalogger updated and reinstalled in the racecar. The only PC I have available is my ubuntu 18.04 laptop, and I'm not really much of a pro at it. I managed to get the source to execute, though I had to use a...

I've got it to work without the Lua script, but the steering and throttle position data(which I get via CAN) is 70% of what I'm interested in.

I've been meaning to try another SD card, but haven't yet. I'd love to see another configuration, especially if it works with a script.

Assuming haltech complies with the CAN standards and gives you a definition of how they send the data, it should be quite straightforward. If they don't give you a definition of their data stream, you'll be in the same boat trying to decode it like those of us reading an oem canbus.

Read through this thread, the AEM/GEMS software is pretty good, even if it's kind of a pain to get the data into it.

http://www.autosportlabs.org/viewtopic.php?t=3731

Hey Brent, any updates on this? It's been a few weeks now and several races where I'd really like to have run data have passed. As it sits the RCP is pretty much useless to me.

Any advice on how to get it to work somewhat reliably? Revert firmware back a ways? Different SD card?

I wrote a relatively simple script to display CAN data in realtime from the serial port of the RCP, thought it might be useful here. The lua script the RCP has loaded is just printing CAN data like : "ID, byte, byte, byte, ...". I believe there's an example script that does this in the wik...

Got a chance to play with this some. Updated to 2.8.2 and 1.3.4 app. Starting logging with the button, at first I could not get any data out of it. Terminal output: Logging started Open: rc_14.log file: close *Wait several seconds and hit button again* Logging stopped Logging: wrote 0 *W...

In my case, I was powered on the entire time the logs were collected (RCP powered through the OBD connection). It stays powered on whenever connected to the OBD port, even if the car is off. I've been using the same micro SD card from the beginning. 32gb class 10 SanDisk ultra card. I didn't see th...

I don't have detailed info on when the log was started or stopped, but I'm pretty confident that it's not resetting due to voltage sag on start. In one case I have a log that ends several turns into a run. I will be sure to start the log only after the engine is running at the next event. I do know ...

Right now I'm triggering the logging with the button, nothing in the script should be triggering it. Here is the script: --500K baud. set your baud rate here. initCAN(0, 500000) setTickRate(30) --onTick() will be called at 30Hz. steering = ...

Used the RCP at the NJ Prosolo, data looked a lot like what I pictured above, most of it missing.

I've had 2 autocrosses so far this year. So far I've only gotten data for about half of the runs I've taken. Most times a file is created, but it has no data, or it's cut off after some period of time. I'm not seeing the error light on after a run at all. I'm using a lua script to read the canbus, b...

I'm mounting the RCP vertically, so that the label faces drivers left, green connector rear. Trying to calibrate the accelerometer for this I have switched the X and Z axes. If I click the Calibrate button, it sets AccelX to have a resting value of 1.0G, Z to have a resting value of 0G. If I tilt th...