I set the ELM327 type to Request/Reply
Connection type BTLE (obviously)
BTLE Peripheral Name to IOS-Vlink (that's how it connects with another program)
BTLE Service UUID: e7810a71-73ae-499d-8c15faa9aef0c3f2
BTLE Characteristic UUID: BEF8D6C9-9c21-4c9e-b632-bd58c1009f9f (both the only ones that made sense in LightBlue and suggested and indicated in https://stackoverflow.com/questions/425 ... peripheral
In the connection process the dongle lights green (BT connection attempted), but never blue (OBD data).
I did get the log from OBD/GPS buddy, but don't really know what to look for. Also, I couldn't manually initialize the dongle sending ATZ command using LightBlue.
The log says:
Code: Select all
[size=85]SENSORCONNECT 0003678393@main D 02 --> call to BTLESensor::connect ()
SENSORCONNECT 0003678393@main D 03 --> call to BTLESensor::connectAndRetryIfNotSuccessful (reconnect: true)
SENSORCONNECT 0003678393@main D 04 --> call to Sensor::connectAndRetryIfNotSuccessful (reconnect: true)
SENSORCONNECT 0003678393@main D 05 --> sensor class: BTLEOBDSensor
SENSORCONNECT 0003678393@main D 05 --> call to Sensor::setReconnect (reconnect: true)
SENSORCONNECT 0003678393@main D 05 --> Sensor::setReconnect () returns
SENSORCONNECT 0003678393@main D 04 --> Sensor::connectAndRetryIfNotSuccessful () returns
BLUETOOTHLE 0003678393@main D 04 --> call to BTLESensor::startConnecting ()
BLUETOOTHLE 0003678393@main D 05 --> triggering discovery of characteristics for peripheral 8A0F8251-562B-4188-9289-F16A703688B6 in state BTLEPeripheralStateAvailable...
BLUETOOTHLE 0003678393@main D 05 --> ... for service 180A and characteristics (2A26,2A19)
BLUETOOTHLE 0003678393@main D 05 --> ... for service <CBService: 0x17407ff80, isPrimary = YES, UUID = E7810A71-73AE-499D-8C15-FAA9AEF0C3F2> skipped
BLUETOOTHLE 0003678393@main D 04 --> BTLESensor::startConnecting () returns[/size]
Code: Select all
[size=85]OBDSENSORS 0003676469@main D 00 --> call to StreamSensor::stream:handleEvent: (stream: inputstream, eventcode: NSStreamEventErrorOccurred)
OBDSENSORS 0003676469@main E 01 --> error #64: "The operation couldn’t be completed. Host is down" detected...
OBDSENSORS 0003676469@main E 01 --> error reported twice ignored...
OBDSENSORS 0003676469@main D 00 --> StreamSensor::stream:handleEvent: () returns
OBDSENSORS 0003676469@main D 00 --> call to StreamSensor::stream:handleEvent: (stream: outputstream, eventcode: NSStreamEventErrorOccurred)
OBDSENSORS 0003676469@main E 01 --> error #64: "The operation couldn’t be completed. Host is down" detected...
SENSORCONNECT 0003676469@main E 01 --> disconnecting due to stream error: The operation couldn’t be completed. Host is down
SENSORCONNECT 0003676469@main D 01 --> call to WifiOBDSensor::closeAndReconnect (reconnect: true)
OBDSENSORS 0003676469@main D 02 --> setting initializing = true
OBDSENSORS 0003676469@main D 02 --> call to OBDStimulator::updateOBDRequests (resetNumReplies: true)
OBDSENSORS 0003676469@main D 03 --> reset 0 numReplies
OBDSENSORS 0003676469@main D 03 --> OBD protocol initialization selected: ATSPA0
OBDSENSORS 0003676469@main D 03 --> adaptive timing selected: ATAT0
OBDSENSORS 0003676469@main D 03 --> request timeout set to: ATSTFF (from 1.02)
OBDSENSORS 0003676469@main D 03 --> throttle PID selected: TPS
OBDSENSORS 0003676469@main D 03 --> baud rate AT command selected: NULL
OBDSENSORS 0003676469@main D 02 --> OBDStimulator::updateOBDRequests () returns
OBDSENSORS 0003676469@main D 02 --> call to OBDParser::expectNextMessageWithStatus (startState: OBDStatusPIDExpected, mode: 0, pid: 0)
OBDSENSORS 0003676469@main D 03 --> changeOBDStatus (newOBDStatus: OBDStatusPIDExpected) changes lastSequenceHadErrors to false
OBDSENSORS 0003676469@main D 02 --> OBDParser::expectNextMessageWithStatus () returns[/size]
Are the UUIDs wrong? Should I enter some funny ASCII initialisation string?