OpenXC CrossChasm 5 Cellular VI

[Aditya Sabadra]

Hi,

I have recently bought OpenXC ChrossChasam 5 Cellular VI device and I am trying to perform smoke tests on it connecting through laptop.

I wanted to know does the micro USB port serve as power source port + data transfer port ?, or the other port similar to USBA/B in orange and micro USB both need to be connected.

Thanks and Regards,

Aditya Sabadra

[Eric Marsman]

Hi Aditya,

The C5 Cellular does not use the large USB (orange) port. In uses the micro-USB like the other OpenXC VIs. 

The one thing to note about the C5 Cell is that the 3G radio is powered from 12V from OBD-II, not the USB like the rest of the VIs. You will NOT be able to transmit data over cellular without a 12V source. Emulated data over USB should work as on other VIs. 

http://vi-firmware.openxcplatform.com/en/master/platforms/crosschasm-c5-cellular.html#telit-power-source

Regards,

Eric

[Aditya Sabadra]

Hi Eric,

Thank you for your prompt response, it's very helpful. I appreciate it.

I would also like to know does the OpenXC Vehicle Interface Driver : https://github.com/openxc/vi-windows-driver are supported for windows 10 machine ? as I see on GitHub steps for only windows 8 and earlier versions has been given.

 I am trying to install those drivers through on windows 10 machine, and get connected to the device but I am facing issues.

[Eric Marsman]

Hi Aditya,

Yes, it should work on Windows 10. I have tested it, but haven't yet updated the documentation. What issues are you facing? 

Regards,

Eric

[Aditya Sabadra]

Hi Eric,

First of all I was not able to see the device plugged in, still the same problem. But recognizing through COM port number I was able to run the "avrdude Bootloader command" and Chipkit command saw the blue light on device which means its recognizing device and can send commands. After that the device name changed from just com port to "Chipkit STK005".

And when I am trying to install the Windows VI driver and picking up the Open_XC.inf file and install it from the windows VI driver folder, it throws an error and closes out stating doesn't contain signature. 

If you can sent me links to follow particular steps on windows 10 that will be helpful.

Thanks and Regards,

Aditya Sabadra

[Eric Marsman]

Just like Windows 8, you have to allow unsigned drivers. It is a little more complex than on Win 8 though. Try one of these and let us know:

http://www.top-password.com/blog/how-to-disable-driver-signature-enforcement-in-windows-10-8-7/

There are other ways to do it as well if you search for Windows 10 signed drivers.

Regards,

Eric

[Aditya Sabadra]

Hi Eric,

Thank you for your responses.

I am working on Windows 10 and whenever I am trying to install Windows VI drivers and follow the given steps it throws an error that digital signature is not valid, and process ends their and drivers are not able to install. 

Then I started from beginning uninstalled whatever I had for this setup, and started back from scratch then I got the error when I am trying to pick the OpenXC_Vehicle_Interface.inf file the error popped was of you have 64 bit operating system please make sure a 64bit windows driver is specified. 

So after working on Windows 10 and doing all the loop around and following multiple steps to get it running I switched to Linux Mint machine, for linux the steps are very straight forward for Python Smoke Test, but I also faced the challenge here all setup went successfully, but I am always getting an error of Device is not connected please plug in a valid OBD device. So issue remains on Linux as well as device not detected. 

I have tried "avrdude" bootloader flashing command and that time light turns blue and pink but it stays in timeout session state. So no further process or steps can be followed to make it working through Python Smoke Test. 

Please let me know the resolution how we can achieve this device getting connected to my Laptop and make it working and start emulating the data. 

Thank you for your valuable time and consideration.

Thanks and Regards,

Aditya Sabadra

[Eric Marsman]

Did you try and re-flash the bootloader on the C5? Your comment ""avrdude" bootloader flashing " is what I noticed. What command did you run? The bootloader should already be flashed and you shouldn't have to change it. If you did change the bootloader, that could be a problem.

You need to flash the device firmware within the first 5 seconds. The timeout error is concerning.

I'm having trouble keeping track of exactly what is going on between the different platforms and versions. Please post exact commands and outputs that you are trying and we'll go from there. I would stick with the windows platform as that is our common use case. 

Regards,

Eric

[Aditya Sabadra]

Hi Eric,

Thank you for response.

Yes I tried to re-flash the bootloader on the C5, I used this command "avrdude.exe -U flash:w:libusb0.dll -c stk500 -p 32MX795F512L -C avrdude.conf -P COM3",  do you think this would be the issue ?

I was following this on Windows 10, but as I see their is no good material for Windows 10 and we are in time sensitive state, to get the first phase of project I have moved to Windows 7.

1. On Windows 7 I was able to install the drivers for the devices please find the attached screenshots, this show that device drivers are installed successfully, but when we run the Openxc-control version command and try to run other commands it throws an error "No Usb vehicle interface detected-is one plugged in ?"  inspite of the device plugged in it throws an error, please find the second screenshot of command prompt reflecting error.

After all this I have tried testing it through Android Application as well but no luck their as well it can't recognize the device at all.

What you think what can be the issue ? As after following all the steps as provided on OpenXC on various different platform but no luck.

Thanks and Regards,

Aditya Sabadra

[Aditya Sabadra]

Hi Eric,

Can we please get the update on the issue. We are in time critical state and want to get this resolved as early as possible so that we can start streaming live data from device. 
So it would be helpful if you can get back to us with resolution.

Thank you for your valuable time and consideration.

Regards,

Aditya Sabadra

[Kanishka Vedi]

Hi Aditya,

I think you are trying to run the command too soon. If you try it after 5seconds of connecting the VI to laptop, you should be able to get the version like below:

C:\Users\vkanishk>openxc-control version

Can't read logs from data source -- stopping: ("USB device couldn't be read", US

BError(None, 'libusb0-dll:err [_usb_reap_async] timeout error\n'))

Device is running version 7.2.1-dev (emulator)

Regards

Kanishka

[Aditya Sabadra]

Hi Kanishka,

Thank you for response. But I don't think so its causing an issue as we are giving time to get device get connected and then hitting the command. 

Hope @Eric can put some insights on this issue.

Awaiting for his response

Thanks and Regards,

Aditya Sabadra 

[Aditya Sabadra]

Hi Kanishka,

Looking at your response to my post it seems you would have also faced the same issue, If you don’t mind can you share which device you are having currently and faced the issue on? We are having “OpenXC CrossChasam C5 Cellular VI”.

I just want to confirm that it’s not the device which is faulty as we have tried all the possible ways and on all different machines(windows 10, windows 7, linux mint ). We have even tried connecting through OpenXC Enabler Android Application but no luck their as well.

We are thinking to return back this device and get it replaced. 

Thanks and Regards,

Aditya Sabadra 

[Aditya Sabadra]

Does anybody have any comments to resolve this issue ? 

I have spent two weeks trying to configure the device on different machines (Windows 10, Windows 7, Linux Mint) as well I have even tried on "Android OpenXC Enabler Application"  without any success. At this point I am thinking either the device is defective or the drivers are not working. I will return the device and look for some other device or solution.

Have anybody had any faulty device issue in past ? 

@Kanishka :What device were you using ? I am using OpenXC CrossChasam Cellular C5 VI device. 

Thanks and Regards,

Aditya Sabadra

[Eric Marsman]

Ok, several comments.

> Yes I tried to re-flash the bootloader on the C5, I used this command "avrdude.exe -U flash:w:libusb0.dll -c stk500 -p 32MX795F512L -C avrdude.conf -P COM3",

You should NOT be flashing the bootloader. You only need to flash the firmware. This is not the correct command to flash anything. From http://vi-firmware.openxcplatform.com/en/master/_static/QuickStart%20guide%20to%20using%20C5%20Hardware%20and%20OpenXC.pdf. See step 10 for windows. The -U argument should be the .hex file that is the firmware:

avrdude.exe -U flash:w:<HEX> -c stk500 -p 32MX795F512L -C avrdude.conf -P COM<N>

For you, the hex file should be vi-emulator-firmware-CROSSCHASM_C5_CELLULAR-ctv7.2.0.hex from the github vi-firmware releases download.

This will emulate data on the USB port and keep the device on. Note that the Cellular connection will not be active (http://vi-firmware.openxcplatform.com/en/master/platforms/crosschasm-c5-cellular.html#telit-power-source).

What did your avrdude command output? If you passed a .dll as the .hex input, I'm assuming it would throw several errors.

FYI, if you want to know about flashing the bootloader see this: https://github.com/openxc/PIC32-avrdude-bootloader. It does require a PICKIt3 to program though. 

> After all this I have tried testing it through Android Application as well but no luck their as well it can't recognize the device at all.

This is expected. The Android application uses a Bluetooth connection to an OpenXC VI. The device you have is a C5 Cellular device that connects directly to the cloud. If you want to use Android, you need to get the Ford Reference VI or the C5 BT. We recommend the Reference VI (http://openxcplatform.com/vehicle-interface/hardware.html#ford-reference-design).

Based on all of the above, I'm assuming you have a good device, you just have yet to program the firmware correctly on the device. This makes sense that the driver is installed correctly, but the device is not operating. 

[Eric Marsman]

Hi Aditya,

Any update on this? I assume all is working since I haven't heard anything else? 

Regards,

Eric

[Aditya Sabadra]

Hi Eric,

We are still working on it, we have moved to Windows 7 and all the setup went fine on this. Thank you for your prompt responses and updates. 

We have tested with Android application connecting through car and now the application is able to recognize the device as well. 

We are now following links to setup the development environment : 

http://vi-firmware.openxcplatform.com/en/master/getting-started/development-environment.html

But in Vagrant setup we are facing issues, and I am getting following attach error.

I am not able to ssh into the environment, its not able to pick up the identity file and not able to verify it and when password prompt appears I am not getting whats the vagrant password. I have seen many blogs where password is "vagrant" but not working.

And After Vagrant ssh It ask to hit vagrant --provision command but after that it throws an bootstrap error, I have seen in this forum that you also faced kind of such issue.

Can you put some insights on this ?

Thanks and Regards,

Aditya Sabadra 

[Eric Marsman]

How are you testing with Android and a C5 Cellular device? This has me confused.

Please post the output of the "vagrant up" command. Since you already have tried and had errors, do a "vagrant destory" first to restart the process. 

For any issues, I need the command you run and the output. Saying you had a vagrant bootstrap error without telling me what it is doesn't help. 

Regards,

Eric

[Aditya Sabadra]

Hi Eric,

I am connecting OBD device and Android phone through USB. So I am able to connect and test through an Android application. It can be tested and connected through an Micro USB cord on both end, Android Application is not only specific to Bluetooth Devices. 

I am following step by step instructions from the following link http://vi-firmware.openxcplatform.com/en/master/getting-started/development-environment.html 

1. Install VirtualBox.
2. If using Windows 7 (not required in Windows 8), add the VirtualBox tools to your PATH: PATH=%PATH%;c:\Program Files\Oracle\VirtualBox. If you aren’t sure how to edit your PATH, see this guide for all versions of Windows. Log out and back in for the change to take effect.
3. Install Vagrant.
4. Navigate to the vi-firmware repository in the GitHub app, click the gear icon in the top right corner and select “Open in Git Shell”.
5. In the shell, run vagrant up to initialize the Vagrant VM - this may take up to 10 minutes as it downloads and installs a number of dependencies in the VM. ---- I have attached screenshots of logs once I hit the Vagrant Up Command. Please see the attached screenshots. 
6. If the initialization completes with no errors, run vagrant ssh to open a shell in the VM. -- I have attached Screenshot of log once I hit the Vagrant Ssh command it asks for password, you can see the error.
7. The vi-firmware directly is shared with the VM in the default home directory. Move into that directory and compile away

And after multiple attempts of "Vagrant Up" I saw at the log end which mentioned hit the "Vagrant --provision", so once I hit the Vagrant --Provision it throws the following error--

Cannot find the bootstrap.sh file. I am not worried about this issue right now as it the vagrant up works and vagrant ssh works I am good.

Please find the attached screenshots and let me know what's going wrong and how we can resolve it.

Thanks and Regards,

Aditya Sabadra

[Eric Marsman]

Hi Aditya,

Good point on Android and USB. Not a common use case, but I understand. 

I don't see any errors in your vagrant up images. Are you still getting an error? You said you are now able to vagrant ssh so I'm assuming the vagrant destroy and re-initialize fixed the issue. 

FYI, you can just redirect the vagrant output with "% vagrant up > vagrant.log" instead of taking screenshots of the long shell scroll. A little easier to process. 

If you have any further issues, please post.

Regards,

Eric

[Aditya Sabadra]

Hi Eric,

Thank you for your responses.

I am still facing issues and Vagrant Destroy has not fixed it. 

I am not able to ssh into the Vagrant Box. 

Its prompting for Password and I am not sure whats the password is, I have seen many blogs which says password is vagrant but it's not picking up you can see the Vagrant ssh Error in the image. and before the Vagrant SSH error you can see the Identity file error technically it should recognize the Private key that is identity file and proceed but its failing. 
I see in Vagrant Up logs that it can recognize the Identity file. 

Please find the output for Vagrant SSH here : 

Thanks and Regards,

Aditya Sabadra

[Eric Marsman]

It can't find the Identity file. Vagrant just uses whatever windows ssh client you have. 

What ssh client are you using? 

Do you have any configs or identity setup up in ~/.ssh/? 

Does $HOME match ~? 

This is kind of out of the scope of OpenXC setup. I think something is messed up on your windows ssh side.

Regards,

Eric

[Aditya Sabadra]

Hi Eric,

I am using Git Shell as mentioned in the Open XC content. 

And I have not pre-configured any ssh keys. 

Currently its not able to recognize the identity file but still prompt for to enter the vagrant password. Do you know what's the password ? 

Is their a way to ssh through the password instead of going though identity file validation ?

Thanks and Regards,

Aditya Sabadra

[Eric Marsman]

I have never tried or had to login with user/password on vagrant. Something is different with your setup than the standard. The user and password should both be "vagrant". We use the ubuntu/precise64 box.

https://www.vagrantup.com/docs/boxes/base.html#quot-vagrant-quot-user

You can try to login with that, but I think it's better to try and fix your setup. Do you have GitHub Desktop installed? 

Please check your output of these commands with mine. Note that I was thinking it was having something to do with being on D: drive, but that works fine for me as well. I also use GitBash instead of PowerShell (much preferred). This is available in the github desktop settings.

Regards,

Eric

[Aditya Sabadra]

Hi Eric,

We have passed the vagrant issue and logged into the (Development Environment) Vagrant Box. We tweaked the VagrantFile and it worked for us. 

Now we are following Customizing VI Configuration steps : http://vi-firmware.openxcplatform.com/en/master/getting-started/config.html

Their are few questions I have : First of all does the firmware which is currently on OBD2 support all the Vehicles Manufactured in US i.e FORD, MERCEDES, HYUNDAI, Volkswagon, BMW ?

Does it also support India make cars and if we need to use the device on Indian make cars what we need to do to generate the firmware ?

And I see on the docs if we run the $fab reference build 

It complies fordboard and generate an hex file 

Is this firmware file which we configured to get specific datasets only support particular makes and models to read data ? 

Also I had an question which more towards data coming out from OBD device : I see that whenever I run the Openxc-dump command their is bunch of data which is spit out on the console when the device is only connected to the Laptop.

But when we connect the device to Laptop / Android Application and to the OBD port on the car and execute the openxc-dump is this still the emulated data ? or its a real data coming out from the car ? 

My take what I see is the data looks like is emulated data on both the ends. 

 

So please let me know your take. 

[Eric Marsman]

Hi Aditya,

Great. Please share your VagrantFile tweak so others will have the answer if they run into the same problem.

Yes, diagnostics should be standard across those vehicles and most in India. 

For your builds, a couple things

1) "% fab reference build" generates a .bin file, not a .hex. .hex is for c5 platforms. For that, you'll need "%fab c5cell build" since that is the device you are using. 

2) What they firmware does depends totally on how you configure it in your build. The webpage you link to tells you how to configure the json & signals.cpp. If you wan't diagnostic data, you can add "translated_obd2" to your fab command (http://vi-firmware.openxcplatform.com/en/master/compile/example-builds.html?highlight=translated_obd2).

3) Since you say you are using the device connected to laptop only (not car) and you are getting data, I'm assuming you have the "emulator" firmware programmed in the device. As long as the "emulator" firmware is there, you will always get emulated data. If you want to get vehicle data, you have to program it with the correct type for that vehicle (or the translated_obd2). Then it will attempt to read data off from your vehicle. Emulator is vehicle independent. 

Regards,

Eric