Adafruit implementation

[bsculley]

Hi Collin,

I am trying to implement the Adafruit module on GEVCU 6.2. I have the module connected and configured in GEVCU, but I'm not able to see a Bluetooth device.

5147 - INFO: - add device: AdaFruit BLE (id: 0x1041, 0x20074EE0)

Do I need to do anything besides connecting it and enabling the device?

Thanks,
Bob

[collin80]

Umm... Sadly, I don't remember. It's probably been 3 years since I tried to use an Adafruit BLE module with a GEVCU6.2. Hmm. What does it say when you enable debugging output? (LOGLEVEL=0 on the console). That might help to narrow it down.

…

On Sat, Sep 22, 2018 at 12:55 PM bsculley ***@***.***> wrote: Hi Collin, I am trying to implement the Adafruit module on GEVCU 6.2. I have the module connected and configured in GEVCU, but I'm not able to see a Bluetooth device. 5147 - INFO: - add device: AdaFruit BLE (id: 0x1041, 0x20074EE0) Do I need to do anything besides connecting it and enabling the device? Thanks, Bob — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACC7ZepT6rbdhi-sgfaPZSXDH9HcDfeuks5udmtjgaJpZM4W1WU3> .

[bsculley]

Here's the GEVCU log starting from an 'a' reset. At the end, the DATATYPE=2 error repeats forever.
I tried to run some of the samples included with the library, but got no response at all. Not even the "Adafruit Bluefruit AT Command Example" serial output.

I also tried starting the Bluetooth in verbose mode, but it crashes with a serial port error.

ADABLUE reset
209847 - DEBUG: New checksum: BF
210723 - DEBUG: Set new BLE state: 1
210725 - DEBUG: Factory Resetting BLE
211124 - DEBUG: New checksum: BF
211843 - DEBUG: Set new BLE state: 2
211845 - DEBUG: Sending power level cmd
211854 - DEBUG: Cmd completed as true in state 2
211856 - DEBUG: Set new BLE state: 3
211883 - DEBUG: Sending device name cmd
211957 - DEBUG: Cmd completed as true in state 3
211958 - DEBUG: Set new BLE state: 4
211963 - DEBUG: Sending add service cmd
211972 - DEBUG: Got a new line: 1
211973 - DEBUG: Cmd completed as true in state 4
211975 - DEBUG: Set new BLE state: 5
212003 - DEBUG: Sending characteristic definition
212404 - DEBUG: New checksum: BF
213203 - DEBUG: Sending characteristic definition
213224 - DEBUG: Got a new line: Option Error: UON=TimeRunning
213225 - DEBUG: Cmd completed as false in state 5
213227 - DEBUG: Error setting characteristics!
213243 - DEBUG: Sending characteristic definition
213264 - DEBUG: Got a new line: Option Error: DATATYPE=2
213265 - DEBUG: Cmd completed as false in state 5
213267 - DEBUG: Error setting characteristics!
213283 - DEBUG: Sending characteristic definition
213304 - DEBUG: Got a new line: Option Error: DATATYPE=2
213305 - DEBUG: Cmd completed as false in state 5
213307 - DEBUG: Error setting characteristics!
213323 - DEBUG: Sending characteristic definition
213345 - DEBUG: Got a new line: Option Error: DATATYPE=2

I added a display of the characteristic being sent:

8832 - DEBUG: Sending characteristic definition: TimeRunning
8853 - DEBUG: Got a new line: Option Error: DATATYPE=2
8855 - DEBUG: Cmd completed as false in state 5
8858 - DEBUG: Error setting characteristics!

I also got this sequence, but not consistently:

7531 - DEBUG: Set new BLE state: 5
7559 - DEBUG: Sending characteristic definition: TimeRunning
7761 - DEBUG: New checksum: BF
8759 - DEBUG: Sending characteristic definition: TimeRunning
8783 - DEBUG: Got a new line: Option Error: URESENTATION=08-0AT+GATTADDCHAR=UUID=12545
8784 - DEBUG: Cmd completed as false in state 5
8786 - DEBUG: Error setting characteristics!

[collin80]

Hmmm.. It seems to work for a little bit then fail and get stuck. And, it seems to be corrupting the lines a little bit. For instance, it should be PRESENTATION= not URESTENTATION=, things like that. It seems like U's are getting inserted in there randomly. Maybe the SPI link is going too quickly? It's also possible that they updated the API in the meantime. The code in GEVCU was written in 2016 apparently and recently Adafruit has been updating the firmware again. Have you updated the firmware on your BLE module recently? I'll try to dig up an Adafruit BLE module on my end and see if I can get it to work.

[bsculley]

I have not updated the firmware on the BLE module. It appears to be an OTA update, but the device is not providing any Bluetooth connection. I'm getting groups of three flashes on the red LED. Should it be instantiating a Bluetooth connection?

Also, I got the examples to run. The ble.info() call hangs. Here is the output from the atcommand example:

Adafruit Bluefruit AT Command Example
-------------------------------------
Initialising the Bluefruit LE module: OK!
Performing a factory reset: 
Requesting Bluefruit info:

Also, got a new message from GEVCU:

7785 - DEBUG: New checksum: BF
8784 - DEBUG: Sending characteristic definition: TimeRunning
8806 - DEBUG: Got a new line: Option Error: UON=TimeRunning
8807 - DEBUG: Cmd completed as false in state 5
8809 - DEBUG: Error setting characteristics!

This only happens on the first attempt to send the characteristic.

[bsculley]

Further to this issue, I have managed to connect to the BLE device using the Adafruit android app. I see the device being advertised as GEVCU 6.2 ECU, but the firmware update failed with error DFU DEVICE DISCONNECTED. Is there something I need to do on GEVCU for this to work?

[collin80]

When I asked about the firmware version I was referring to the Adafruit module itself, just to be clear. It sounds like you tried to do that with their Adafruit app which is the proper way to do it. It ought to work. I've updated BLE firmware through their app before. If it won't do it then perhaps you've got a questionable module that just doesn't quite work properly.

…

On Thu, Sep 27, 2018 at 11:11 AM bsculley ***@***.***> wrote: Further to this issue, I have managed to connect to the BLE device using the Adafruit android app. I see the device being advertised as GEVCU 6.2 ECU, but the firmware update failed with error DFU DEVICE DISCONNECTED. Is there something I need to do on GEVCU for this to work? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACC7ZT81OQJqFhCGYY_nz9FCK5J_cuwqks5ufOqqgaJpZM4W1WU3> .

[bsculley]

I have asked about it on the Adafruit forum. Maybe I'll get an answer.
Can you confirm a version of the firmware that works with GEVCU? The module I have is 0.6.5.

[bsculley]

I bought a new Bluetooth module and am getting the same results as before. Device software is revision 0.6.5. Should I upgrade it? I really need to get this working.

36879 - DEBUG: Cmd completed as true in state 4
36880 - DEBUG: Set new BLE state: 5
36884 - DEBUG: Sending characteristic definition: TimeRunning
36906 - DEBUG: Got a new line: Option Error: DATATYPE=2
36907 - DEBUG: Cmd completed as false in state 5
36909 - DEBUG: Error setting characteristics!
36924 - DEBUG: Sending characteristic definition: TimeRunning
37045 - DEBUG: New checksum: BF
38084 - DEBUG: Sending characteristic definition: TimeRunning
38106 - DEBUG: Got a new line: Option Error: UON=TimeRunning
38107 - DEBUG: Cmd completed as false in state 5
38109 - DEBUG: Error setting characteristics!
38124 - DEBUG: Sending characteristic definition: TimeRunning
38145 - DEBUG: Got a new line: Option Error: DATATYPE=2
38147 - DEBUG: Cmd completed as false in state 5
38149 - DEBUG: Error setting characteristics!

[collin80]

I finally got around to looking into this more thoroughly. I first tried with a unit of unknown firmware version (forgot to check) it did work. Then I tried the Adafruit app and it asked if I wanted to update to 0.8.0. I said yes. It worked afterward too. Here's a snippet of it starting up:

3645 - DEBUG: Set new BLE state: 1
3645 - DEBUG: Factory Resetting BLE
.4755 - DEBUG: Set new BLE state: 2
4755 - DEBUG: Sending power level cmd
4759 - DEBUG: Cmd completed as true in state 2
4760 - DEBUG: Set new BLE state: 3
4765 - DEBUG: Sending device name cmd
4770 - DEBUG: Cmd completed as true in state 3
4770 - DEBUG: Set new BLE state: 4
4775 - DEBUG: Sending add service cmd
4780 - DEBUG: Got a new line: 1
4780 - DEBUG: Cmd completed as true in state 4
4780 - DEBUG: Set new BLE state: 5
4785 - DEBUG: Sending characteristic definition
4799 - DEBUG: Got a new line: 1
4799 - DEBUG: Cmd completed as true in state 5
4805 - DEBUG: Sending characteristic definition
4820 - DEBUG: Got a new line: 2
4820 - DEBUG: Cmd completed as true in state 5
4825 - DEBUG: Sending characteristic definition
4845 - DEBUG: Got a new line: 3
4845 - DEBUG: Cmd completed as true in state 5
4845 - DEBUG: Sending characteristic definition
4882 - DEBUG: Got a new line: 4
4882 - DEBUG: Cmd completed as true in state 5
4885 - DEBUG: Sending characteristic definition
4899 - DEBUG: Got a new line: 5
4900 - DEBUG: Cmd completed as true in state 5
4905 - DEBUG: Sending characteristic definition
4921 - DEBUG: Got a new line: 6
4921 - DEBUG: Cmd completed as true in state 5
4925 - DEBUG: Sending characteristic definition
4974 - DEBUG: Got a new line: 7
4974 - DEBUG: Cmd completed as true in state 5
4975 - DEBUG: Sending characteristic definition
5000 - DEBUG: Got a new line: 8
5000 - DEBUG: Cmd completed as true in state 5
5005 - DEBUG: Sending characteristic definition
5019 - DEBUG: Got a new line: 9
5019 - DEBUG: Cmd completed as true in state 5
5025 - DEBUG: Sending characteristic definition
5045 - DEBUG: Got a new line: 10
5045 - DEBUG: Cmd completed as true in state 5
5045 - DEBUG: Sending characteristic definition
5061 - DEBUG: Got a new line: 11
5061 - DEBUG: Cmd completed as true in state 5
5065 - DEBUG: Sending characteristic definition
5080 - DEBUG: Got a new line: 12
5080 - DEBUG: Cmd completed as true in state 5
5085 - DEBUG: Sending characteristic definition
5100 - DEBUG: Got a new line: 13
5101 - DEBUG: Cmd completed as true in state 5
5105 - DEBUG: Sending characteristic definition
5985 - DEBUG: Sending characteristic definition
6003 - DEBUG: Got a new line: Option Error: UAT+GATTADDCHAR=UUID=12558
6004 - DEBUG: Cmd completed as false in state 5
6004 - DEBUG: Error setting characteristics!
6005 - DEBUG: Sending characteristic definition
6021 - DEBUG: Got a new line: 14
6021 - DEBUG: Cmd completed as true in state 5
6025 - DEBUG: Set new BLE state: 6
6035 - DEBUG: Sending gap advert data cmd
6042 - DEBUG: Cmd completed as true in state 6
6042 - DEBUG: Set new BLE state: 7
6045 - DEBUG: Resetting BLE to enable new settings.
6045 - DEBUG: Set new BLE state: 8
6046 - DEBUG: Cmd completed as true in state 8
7155 - DEBUG: Set new BLE state: 10
7159 - DEBUG: Cmd completed as true in state 10
7169 - DEBUG: Cmd completed as true in state 10
7179 - DEBUG: Cmd completed as true in state 10
7189 - DEBUG: Cmd completed as true in state 10
7199 - DEBUG: Cmd completed as true in state 10
7209 - DEBUG: Cmd completed as true in state 10
7219 - DEBUG: Cmd completed as true in state 10
7225 - DEBUG: Set new BLE state: 11
7235 - DEBUG: Set new BLE state: 13
7239 - DEBUG: Got a new line: 0x0,0x0
7239 - DEBUG: Cmd completed as true in state 13
7240 - DEBUG: Set new BLE state: 11
7246 - DEBUG:  - Updated timeRunning
7249 - DEBUG: Cmd completed as true in state 11
7256 - DEBUG:  - Updated bleThrBrkLevels 2
7261 - DEBUG: Cmd completed as true in state 11
7266 - DEBUG:  - Updated bleTrqReqAct 1
7269 - DEBUG: Cmd completed as true in state 11
7286 - DEBUG:  - Updated bleThrBrkLevels 2
7292 - DEBUG: Cmd completed as true in state 11
7298 - DEBUG:  - Updated bleThrottleIO 9
8006 - DEBUG:  - Updated timeRunning
8009 - DEBUG: Cmd completed as false in state 11
8016 - DEBUG:  - Updated bleThrBrkLevels 2
8021 - DEBUG: Cmd completed as true in state 11
8026 - DEBUG:  - Updated bleThrottleMap 10
8031 - DEBUG: Cmd completed as true in state 11
8036 - DEBUG:  - Updated bleThrBrkLevels 2
8041 - DEBUG: Cmd completed as true in state 11
8046 - DEBUG:  - Updated bleDeviceEnable 13
8051 - DEBUG: Cmd completed as true in state 11
8056 - DEBUG:  - Updated bleThrBrkLevels 2
8061 - DEBUG: Cmd completed as true in state 11
8245 - DEBUG: Set new BLE state: 13
8248 - DEBUG: Got a new line: 0x0,0x0

[collin80]

So, where does that leave you? Well, actually the first unit I tried did nothing because it was a UART version of the board. You see, there were many versions of the GEVCU6 design before we settled upon the latest one. First we used very cheap BLE modules that were not configurable - they just were BLE to UART chips. Then we switched to Adafruit but the UART version. Then we switched to the SPI version to try to get more speed. I believe you must have the newest, SPI version or you wouldn't get anything at all. With the UART version youd be stuck at state 2 forever trying to set the power level. Anyway, so you probably have the newest board version but something is still not working. First of all, use the DEV branch of GEVCU6 because it is newer and has updates compared to the master branch. That's the version I'm testing with. Then, just to be sure, use the Adafruit library I've put here: www.savvycan.com/Adafruit_BLE_SPI.zip

Between those two things it ought to work because I did just test and was able to get to a stable state and see it with the Adafruit android app.

[collin80]

Lastly, if you've already modified things elsewhere in the code and don't want to overwrite all your changes, then try grabbing just adafruitBLE.cpp and adafruitBLE.h from the DEV branch. Those two files should be the only ones you really need to fix BLE but there were a LOT of BLE related commits between MASTER and DEV so I can't say for 100% sure nothing changed outside those files but it shouldn't have. It is intentionally object oriented and segmented.

[bsculley]

I downloaded and installed the Adafruit library. Nothing much changed, just a new error. I'll try the DEV version of GEVCU tomorrow. Are most of the changes to the AdafruitBLE files, or are they more widespread?

41361 - DEBUG: Set new BLE state: 5
41388 - DEBUG: Sending characteristic definition: TimeRunning
41412 - DEBUG: Got a new line: Option Error: DATATYPE=2
41414 - DEBUG: Cmd completed as false in state 5
41416 - DEBUG: Error setting characteristics!
41428 - DEBUG: Sending characteristic definition: TimeRunning
42269 - DEBUG: New checksum: BF
42588 - DEBUG: Sending characteristic definition: TimeRunning
42611 - DEBUG: Got a new line: Option Error: UAT+GATTADDCHAR=UUID=12545
42612 - DEBUG: Cmd completed as false in state 5
42614 - DEBUG: Error setting characteristics!
42628 - DEBUG: Sending characteristic definition: TimeRunning
42649 - DEBUG: Got a new line: Option Error: DATATYPE=2
42651 - DEBUG: Cmd completed as false in state 5
42653 - DEBUG: Error setting characteristics!

[bsculley]

I got the DEV code and copied AdafruitBLE into my project. It didn't help. It doesn't look like there are any changes to other modules that would affect Bluetooth functionality. Can you zip up all the code and libraries you are testing with so I can verify that it works with the hardware I have? If it does, I can back apply my changes.

[collin80]

Here's my copy of the GEVCU6 code though it ought to be the same as the GITHub version: www.savvycan.com/GEVCU6.zip

And, you already have the AdafruitBLE library I'm using. Between those two things those are the only two pieces of code I could possibly have that would be different.

So, if it still doesn't work then you have the same code and you tried two different BLE modules so that pretty much leads to suspecting the GEVCU board itself. That's not an ideal situation but maybe there could be something else you could try.

In the Adafruit_BLE_SPI library I sent before there is a line that sets up the SPI speed. It is set to 3Mhz which is under the 4MHz upper limit for the BLE module but since it looks like you're getting comm errors you might try lowing the speed to 1Mhz to see if things improve. BluefruitLE_SPI.cpp on line 45 you'll find the SPI set up. Change the 3 to a 1 and try reloading the IDE and recompiling everything. This will vastly slow down the SPI comm and might help if you aren't getting as stable of a connection as you should.

[bsculley]

Thanks. I reset the SPI speed to 1000000 and recompiled my code, but that didn't make any difference. Then I tried your sketch. At first it wouldn't run properly, but I discovered that the verbose setting was causing the serial port to disconnect. I set verbose off and tried your sketch again (still with the SPI speed set to 1000000). Now it runs ok, but with the same errors regarding sending the characteristic definition. It looks like the GEVCU itself might be the problem. How do you suggest proceeding from this point?

Is the behavior of the verbose setting indicative of anything? I assume it works for you?