ReDrive sensor does not work

Help on issues you run into with LapTimer; in case you have a question on how to use LapTimer, use the forum "Using LapTimer" instead
Gridzilla
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 2
Joined: Fri Sep 28, 2018 10:07 am

ReDrive sensor does not work

Post by Gridzilla » Fri Sep 28, 2018 12:39 pm

Hello,

I have Harry's Laptimer Petrolhead v22.1 with ReDrive running on firmware 1.5.181. Adding the RDG_... device as a GPS sensor just shows it as "Searching" then "Not available". This happens regardless whether the ReDrive app is running in background or not. When I run the ReDrive application instead of Laptimer then the device is seen just fine, gets a fix, 20HZ etc.

Any help appreciated,
Thanks
User avatar
Harry
Site Admin
Site Admin
Posts: 9579
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: ReDrive sensor does not work

Post by Harry » Tue Oct 02, 2018 6:54 pm

When on Android, make sure you have Bluetooth Low Energy enabled in LapTimer's Expert Settings. Please do not pair the reDrive device in Sensor List (for Android) - it is not a Bluetooth SPP device which requires pairing. Finally, make sure you kill any other app connecting to ReDrive. Concurrent connects will never work for accessories.

- Harry
Image Image Image Image
Gridzilla
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 2
Joined: Fri Sep 28, 2018 10:07 am

Re: ReDrive sensor does not work

Post by Gridzilla » Tue Oct 02, 2018 7:01 pm

The above worked for me, in addition to a re-pairing with the device. Great work!
User avatar
Mateusz
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 86
Joined: Mon Jul 03, 2017 8:32 pm

Re: ReDrive sensor does not work

Post by Mateusz » Mon Oct 08, 2018 10:27 am

I've got a problem with ReDrive on 22.1 as well - this time on IOS. Still working perfect on v22 pre-release beta and release v22.0xx, but stopped connecting after upgrading to 22.1. Has anything changed in the latest version?
User avatar
Harry
Site Admin
Site Admin
Posts: 9579
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: ReDrive sensor does not work

Post by Harry » Mon Oct 08, 2018 12:42 pm

Nothing I’m aware of. What exactly happens when connecting a ReDrive? No connect or wrong data? Please make sure all other apps accessing it are killed. For Android, make sure you have enabled BT LOw Energy accessories in Expert Settings.

Harry
Image Image Image Image
User avatar
Mateusz
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 86
Joined: Mon Jul 03, 2017 8:32 pm

Re: ReDrive sensor does not work

Post by Mateusz » Mon Oct 08, 2018 2:43 pm

No connection, no detection. BTLE is enabled (OBD works, and it is iOS anyway). I think I did kill all instances of everything.
On another phone with an older version of v22 the dongle connects instantly (just like on the phone in question, before the upgrade to v22.1)

If wrong data was displayed after connection, I would have been responsible! :)
User avatar
Harry
Site Admin
Site Admin
Posts: 9579
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: ReDrive sensor does not work

Post by Harry » Mon Oct 08, 2018 3:00 pm

So please select "All" in the top of Sensor List and check if you see the ReDrive entry. Which status does it show?

- Harry
Image Image Image Image
User avatar
Mateusz
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 86
Joined: Mon Jul 03, 2017 8:32 pm

Re: ReDrive sensor does not work

Post by Mateusz » Thu Oct 11, 2018 7:28 pm

It shows <searching>. In further troubleshooting:

- upgraded the previously working phone to iOS12 (Aug v22 still works)
- installed the current v22.1.1 alongside pre-release testflight v22, with fresh settings (v22.1.1 does not work on the previously working phone, pre-release v22 continues to work well). I double-checked BTLE settings, OBD still works.
- Checked GPS Buddy v22.1, same effect. Log entries I found semi-relevant are pasted below. The problem seems to be BT connection, not data transfer.

Code: Select all

SENSORCONNECT  0013902067@main  D 01   --> call to ScriptedBTLESensor::closeAndReconnect (reconnect: false)
SENSORCONNECT  0013902067@main  D 02     --> call to BTLESensor::closeAndReconnect (reconnect: false)
SENSORCONNECT  0013902067@main  D 03       --> call to Sensor::closeAndReconnect (reconnect: false)
SENSORCONNECT  0013902067@main  D 04         --> call to ScriptedBTLESensor::didDisconnect ()
SENSORCONNECT  0013902067@main  D 05           --> call to Sensor::didDisconnect ()
SENSORCONNECT  0013902067@main  D 05           --> Sensor::didDisconnect () returns
SCRIPT         0013902067@main  D 05           --> call to Script::hasScriptFunction (fctnName: sensor.ondisconnect)
SCRIPT         0013902067@main  D 06             --> call to Script::getFunction (fctnName: sensor.ondisconnect, fcnt: .)
SCRIPT         0013902067@main  D 07               --> call to Script::getFunctionModule (., fctnName: sensor.ondisconnect)
SCRIPT         0013902067@main  D 08                 --> found module sensor
SCRIPT         0013902067@main  D 08                 --> found function name ondisconnect
SCRIPT         0013902067@main  D 07               --> Script::getFunctionModule () returns ondisconnect
SCRIPT         0013902067@main  D 06             --> Script::getFunction () returns
SCRIPT         0013902067@main  D 05           --> Script::hasScriptFunction () returns true
SCRIPT         0013902067@main  D 05           --> call to Script::callScriptFunction (fctnName: sensor.ondisconnect, signature: >, ...)
SCRIPT         0013902067@main  D 06             --> call to Script::getFunction (fctnName: sensor.ondisconnect, fcnt: .)
SCRIPT         0013902067@main  D 07               --> call to Script::getFunctionModule (., fctnName: sensor.ondisconnect)
SCRIPT         0013902067@main  D 08                 --> found module sensor
SCRIPT         0013902067@main  D 08                 --> found function name ondisconnect
SCRIPT         0013902067@main  D 07               --> Script::getFunctionModule () returns ondisconnect
SCRIPT         0013902067@main  D 06             --> Script::getFunction () returns
SCRIPT         0013902067@main  D 06             --> calling script function...
SENSORCONNECT  0013902067@main  D 06             --> ReDrive BLE sensor disconnected...
SCRIPT         0013902067@main  D 05           --> Script::callScriptFunction () returns
...
SENSORCONNECT  0013904215@main  D 01   --> checking sensor ReDrive BLE GNSS (not connected, not available) with highPrioConnectionFound: false
SCRIPT         0013904215@main  D 01   --> call to Script::getFunction (fctnName: sensor.onnameprefix, fcnt: .)
SCRIPT         0013904215@main  D 02     --> call to Script::getFunctionModule (., fctnName: sensor.onnameprefix)

User avatar
Mateusz
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 86
Joined: Mon Jul 03, 2017 8:32 pm

Re: ReDrive sensor does not work

Post by Mateusz » Fri Oct 19, 2018 10:29 am

Is there any way to roll back the install to 22.0?
I don't imagine a script sidestepping the built-in version would be helpful here, as the built-in version works the same way...
User avatar
Harry
Site Admin
Site Admin
Posts: 9579
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: ReDrive sensor does not work

Post by Harry » Sun Oct 21, 2018 11:08 am

I assume it is some difference between script versions used for the beta and the production version.
You can override the script installed by the production version by adding your own custom version.
As this is developer stuff, any further questions in this need to be discussed in the developer area.

- Harry
Image Image Image Image
Post Reply