Autosport Labs

The documentation here: https://wiki.autosportlabs.com/AnalogX says Analog input 1 is on the Blue wire, and channel 1 is at the base address + 20. If I configure a channel in RaceCapture using Base+20 and map it to a Dashboard display it will display the data on the Brown wire, which is channel 4, a...

Brent,

I thought I tried that, but I just tried again and that does seem to work. Sorry for the extraneous error log!

Doug

Brent, I think this issue is related to the other one I posted about the input order being reversed. When I changed the input offset (or when I changed which analog wire I connected my input to) the data displayed in RaceCapture tracked that on my voltmeter much more closely. That said, there is ano...

Some CAN bus values cannot be configured from the RaceCapture App on Windows (I'm using Windows 10, I don't know about other versions). In particular, CAN bus data offsets higher than 5 cannot be programmed because the select boxes drop below the dialog and do not show and the Units Conversion canno...

The documentation for the AnalogX shows the analog input offsets as 0, 2, 4, and 6 for analog inputs 1, 2, 3, and 4. This is reversed. It took me 2 days to figure this out, but I'm positive this is the case. You can see this by watching the serial data with HyperTerminal and un-grounding a single an...

I decided I was making this too complicated to start out, so I removed the load cell and load cell amp and replaced them with a potentiometer connected between the 5V and ground on the analog input side of the AnalogX, with the wiper going to the channel 1 input. I put a voltmeter on the pot and was...

I'm trying to connect an AnalogX to measure the load on each corner using shock load donuts. On the workbench I connected the AnalogX to a RaceCapture Pro2 and connected a load cell amp to the AnalogX analog input 1 (blue wire). I have a voltmeter on the load cell amp output and it reads a steady 0....

I just emailed 3 logfiles and the datastore. Please let me know if you need anything else!

Doug

We're also seeing this issue. We' running a RaceCapture Pro MK3 and the RaceCapture App 1.11.0 on Windows 10. I am able to view data by editing the .log file, and if I look at the file (by changing the suffix to .csv and reading it into Excel) there are no duplicate column names. One thing that migh...

I was able to borrow a Galaxy Tab E. It works, and more than just one time! Both the Tab E and my phone (Galaxy S5) have Android 6.0.1, but the phone has an older kernel (3.4.0 versus 3.10.49-8498553). Most of the rest of the stuff appears the same between the two. The Tab E does seem to make itself...

It appears this was a one-time deal. Now that I've connected sensors I can no longer connect to the MK1 via Bluetooth. I have Version 1.10.2 of the App on my Samsung S5 and on my Windows10 PC and Firmware version 2.8.7 in the MK1. The PC can connect over USB but the phone cannot connect via Bluetoot...

Brent,

Thanks for the help. I did get it to connect to my phone. I thought I tried exactly what you suggested a couple times with no luck. However, it worked this time! I think I rebooted my phone in between - perhaps that helped.

Now I'm on to setup and configuration!

Doug

Brent, I was able to update the firmware using the instructions provided by mwehnes, and following that I was able to communicate with the app on my PC. You mention the MK1 can connect with the App on my phone/tablet via Bluetooth. How do I go about doing that? I have a small black box that connects...

@mwehnes - Thanks so much for the FW update instructions - I seriously doubt I would have figured this out on my own! I finally had a chance to try it and it worked exactly as you described. It is a lot of extra work just because the drivers are unsigned!

I'm working with a race team that is setting up 2 cars for a comparison test day. We have a Pro3 and a MK1. The Pro3 connects to Windows 10 just fine over USB but I cannot get the MK1 to connect. I tried both Windows 10 and Windows Vista (I don't have Windows 7). Thinking the firmware might be out o...