Bluetooth Messages slowly received by OpenXC enabler

[Jacob Albert]

I am receiving messages in the enabler App from my custom firmware, but when I swipe right there are no CAN messages. It's like 2 messages every 30 seconds.

 Enabler is version 6.1.6.

I set the baud rate using blueterm and the commands $$$ SU,46. I think my hardware is working. If that was wrong would I even see any messages?

If my firmware spec is incorrect would that cause this?

What else could be the issue?

Thanks 

[Jacob Albert]

All I get in the logs is {"command_response":"version","message":"7.1.1 (default)","status":true,"a":{"a":{"command":"version"},"b":124090386},"timestamp":1471219205.109}

{"command_response":"device_id","message":"00066679E38D","status":true,"a":{"a":{"command":"device_id"},"b":-1623397107},"timestamp":1471219205.16}

{"command_response":"version","message":"7.1.1 (default)","status":true,"a":{"a":{"command":"version"},"b":124090386},"timestamp":1471219210.368}

{"command_response":"device_id","message":"00066679E38D","status":true,"a":{"a":{"command":"device_id"},"b":-1623397107},"timestamp":1471219210.413}

{"command_response":"version","message":"7.1.1 (default)","status":true,"a":{"a":{"command":"version"},"b":124090386},"timestamp":1471219221.007}

{"command_response":"device_id","message":"00066679E38D","status":true,"a":{"a":{"command":"device_id"},"b":-1623397107},"timestamp":1471219221.052}

{"command_response":"version","message":"7.1.1 (default)","status":true,"a":{"a":{"command":"version"},"b":124090386},"timestamp":1471219244.613}

{"command_response":"device_id","message":"00066679E38D","status":true,"a":{"a":{"command":"device_id"},"b":-1623397107},"timestamp":1471219244.657}

{"command_response":"version","message":"7.1.1 (default)","status":true,"a":{"a":{"command":"version"},"b":124090386},"timestamp":1471219247.566}

{"command_response":"device_id","message":"00066679E38D","status":true,"a":{"a":{"command":"device_id"},"b":-1623397107},"timestamp":1471219247.611}

{"command_response":"version","message":"7.1.1 (default)","status":true,"a":{"a":{"command":"version"},"b":124090386},"timestamp":1471219257.066}

{"command_response":"device_id","message":"00066679E38D","status":true,"a":{"a":{"command":"device_id"},"b":-1623397107},"timestamp":1471219257.109}

{"command_response":"version","message":"7.1.1 (default)","status":true,"a":{"a":{"command":"version"},"b":124090386},"timestamp":1471219291.347}

{"command_response":"device_id","message":"00066679E38D","status":true,"a":{"a":{"command":"device_id"},"b":-1623397107},"timestamp":1471219291.389}

{"command_response":"version","message":"7.1.1 (default)","status":true,"a":{"a":{"command":"version"},"b":124090386},"timestamp":1471219299.42}

{"command_response":"device_id","message":"00066679E38D","status":true,"a":{"a":{"command":"device_id"},"b":-1623397107},"timestamp":1471219299.463}

{"command_response":"version","message":"7.1.1 (default)","status":true,"a":{"a":{"command":"version"},"b":124090386},"timestamp":1471219303.001}

{"command_response":"device_id","message":"00066679E38D","status":true,"a":{"a":{"command":"device_id"},"b":-1623397107},"timestamp":1471219303.046}

Doesn't look like any CAN data is coming through right? The chipkit light stays green constantly. Any ideas?

[Eric Marsman]

Hi Jacob,

Correct, you're not getting any CAN data. You'll have to provide more info on your custom firmware and how it is configured for us to be able to assist. 

I assume you used a standard build first and everything is working there? That will confirm your bluetooth settings and Android device are all working properly. 

Regards,

Eric

[Jacob Albert]

Thanks for getting back to me - My current issue is that I cannot get the bluesmirf into command mode by typing $$$. It connects with a solid green light to the openx-enabler app / blueterm. Might be a baud rate issue. My older bluesmirf would go into command mode though.

 
This has a pass through firmware on it in hopes to just catch any CAN data coming through on a particular message bus to make testing simpler. I can read the emulated data over USB consistently when I flash that build. I have a  custom CAN Spec for the particular device I am connecting to, but I get no data out of it besides the version.

Here's my pass through for one particular message set on my bus - I should see some data correct when connected by USB? I am not getting anything.
{   "buses": {
        "hs": {
            "controller": 1,
            "speed": 500000,
            "raw_can_mode": "filtered"
        }
    },
    "messages": {
      "0x01F0A003": {
        "bus": "hs"

[Zac]

Hi Jacob,

First thing I notice is that your CAN message id has a very large value: 0x01F0A003. OpenXC only supports 11bit or 19 bit CAN IDs so that's most likely why you can't get any data over USB. Might that be a typo?

The only think I can think to do for the Bluesmirf would be to ensure that you disconnect the UART pins from the Chipkit before going into command mode. Have you tried that?

- Zac

[Jacob Albert]

Good info - That's interesting and I'm not super knowledgeable, but doesn't CAN2.0A support 11 bit and the latest version CAN2.0B  support 29 bit IDs? What is 19 bit? Openxc does not support 29 bit IDs then? My spec uses them :(

 I will retry command mode with the UART pins disconnected.

[Zac]

Ah, my apologies, correct it's 29 bit not 19-bit. 

So OpenXC should support your 29-bit message IDs - I was wrong earlier. See here: https://github.com/openxc/vi-firmware/blob/0ee0b5ab03174a8729ca417d101848584b26b993/src/can/canutil.h#L59

That being said, I haven't tested this myself (don't have any modules that send extended CAN IDs...) but we do test for it in the functional tests here: https://github.com/openxc/vi-firmware/blob/0ee0b5ab03174a8729ca417d101848584b26b993/script/functional_test.py