RaceCapture support

Discussion related to external and internal GPS sensors
silacim3
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 1
Joined: Tue Jul 31, 2018 11:33 pm

RaceCapture support

Postby silacim3 » Tue Jul 31, 2018 11:48 pm

Hi, new member here.

I'm looking at using RaceCapture with HLT mainly because RaceCapture can provide much faster data over CAN than standard OBD, but I couldn't find any info on the latest releases of RaceCapture and whether they are supported by HLT or not.

1- Harry had a detailed post about RaceCapture which referred to RaceCapture Track and RaceCapture Pro Mk2. However, RaceCaputer's current products are RCT Mk2, and RCP Mk3. Are those supported by HLT as well and is one preferred over the other?

2- Between BT and Wifi, is there any preference as to which one to use assuming I have both iPhone and Android phones? Is one faster than the other?

3- RaceCapture can drive the GoPro with their Wifi module. How one would go about setting this up with HLT? Can the Wifi module be used to both drive the GoPro and connect to HLT or should BT module be used in that case and connect the GoPro directly to HLT instead of RaceCapture.

4- Is HLT able to export all channels from RCP to vbo format for data analysis on Circuit Tools.

Thanks in advance.


User avatar
Harry
Site Admin
Site Admin
Posts: 8890
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Has thanked: 98 times
Been thanked: 365 times
Contact:

Re: RaceCapture support

Postby Harry » Fri Aug 10, 2018 6:50 pm

They are all supported, but you need to configure it in a way LapTimer understands (see the post mentioned). The MK2 is the only device I have available and use for testing. As RCP devices are heavily customizable, please never expect anything to work "out of the box". You really need to understand channel configuration et al to get things running.

BT is preferable for sensor communication. It is a bit slower than WiFi, but a lot more reliable. WiFi is actually a workaround RCP devices provide: ASL doesn't certify its devices by Apple, so WiFi is needed to connect at all.

If you want to operate the cam using the RCP, I'd suggest to drop the use of LapTimer and go with ASL's tools. They are limited compared to LapTimer, but this is simply getting to complicated and there is too much overlap between the systems.

VBO's set of standard channels is limited to GPS. Everything else differs by devices and and is not standardized. LapTimer adds a number of engine channels we have seen frequently in VBO exports (like RPM), but as I said - this is not standardized stuff.

- Harry


Image Image Image Image
schluerfi1978
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 49
Joined: Mon Oct 03, 2011 8:04 pm
Has thanked: 3 times
Been thanked: 2 times

Re: RaceCapture support

Postby schluerfi1978 » Sun Sep 09, 2018 2:02 pm

Hello Harry,
can HLT Version 22 now make use of the gyro and accelerometer data that is supplied by the RaceCapture device? In this older topic from 2017, you mentioned that support for this might be added later: viewtopic.php?f=39&t=4244&p=21686&hilit=racecapture#p21686 .

With best regards,
Michael


User avatar
Harry
Site Admin
Site Admin
Posts: 8890
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Has thanked: 98 times
Been thanked: 365 times
Contact:

Re: RaceCapture support

Postby Harry » Sun Sep 09, 2018 2:06 pm

Hi,

That's a low priority in general (i.e. all external sensors). I think for 99% of all LapTimer users, the accelerometer built into the smartphone is fully sufficient. All accessory manufacturers built these IMU sensors into their GPS and OBD devices now. Not sure this makes too much sense except for devices usable standalone (like RCPs).

- Harry


Image Image Image Image

Return to “GPS”

Who is online

Users browsing this forum: No registered users and 1 guest