Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test with Windows 8 #1

Open
DaveMelcher opened this issue Jan 27, 2014 · 9 comments
Open

Test with Windows 8 #1

DaveMelcher opened this issue Jan 27, 2014 · 9 comments
Assignees

Comments

@DaveMelcher
Copy link
Member

No description provided.

@ghost ghost assigned DaveMelcher Jan 27, 2014
@DaveMelcher
Copy link
Member Author

With Windows 8, I never see anything happen in the Device Manager. No yellow punctuation of any kind.

@kewashi
Copy link
Contributor

kewashi commented Nov 22, 2014

I solved this problem today. You have to first enable unsigned drivers. This website shows you how:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
Following these instructions will require you to reboot a few times. Note that you cannot use the CMD command prompt version of these instructions, or at least I couldn't get that to work.

Then you have to download the original libusb-win2 zip file and run the inf-wizard.exe to create a new OpenXC_Vehicle_Interface.inf file.

Then you follow the main instructions again. Also, I think the .iinf file is corrupt on the main page.

I will try to upload the one that I made in case that helps anyone.

@peplin
Copy link
Member

peplin commented Nov 22, 2014

That's great, Ken, thank you! I haven't upgraded to Win8 so it would be awesome if you can upload the driver that works for you.

@kewashi
Copy link
Contributor

kewashi commented Nov 22, 2014

Yea, I just got the usb backend driver installed and working fine, but I still get an error when I run openxc-control version even though it still returns the version number. It returns:

Can't read logs from data source -- stopping: ("USB device couldn't be read", USBError(None, 'libusb0-dll:err [_usb_reap_async] time
out error\n'))
Device is running version 7.0.0 (default)

openxc-dump seems to work fine, returning the expected stream of json lines

I will continue tweaking it until I figure it out. I may need to tweak the source and recompile the driver, but I hope not. It has been years since I have done any low level C coding...

My goal is to work mainly with Python since that will be faster and easier than me messing with Android development, although I will probably end up playing with both. My goal is to motivate others to join in - after all, if an old guy in upper management like me can do it, anyone probably can... :)

Also, I'm not in the OpenXC group so I couldn't upload any files. How do I get added?

Ken

PS - the guys told me good things about you when I visited the lab last week... cool.

@sudo-a13
Copy link

@kewashi best way to push your driver is to work off your branch and generate a pull-request https://help.github.com/articles/using-pull-requests/#initiating-the-pull-request.

We will merge it with the master once you generate one

@kewashi
Copy link
Contributor

kewashi commented Nov 22, 2014

Got it... thanks. Sounds simple enough.

@peplin
Copy link
Member

peplin commented Nov 23, 2014

Can't read logs from data source -- stopping: ("USB device couldn't be read", USBError(None, 'libusb0-dll:err [_usb_reap_async] time
out error\n'))
Device is running version 7.0.0 (default)

The fact that it does get the version OK, and you said openxc-dump works, make me think the is working fine. I think the time out error is a result of some less-than-graceful shutdown code in the Python library. I've created an issue in the python library so we remember to look into that.

@kewashi
Copy link
Contributor

kewashi commented Nov 26, 2014

One other issue I found and resolved for Windows and Python - not sure if this is specific to 8 or not - is that after installing Python 2.7 the _curses library is not present, which causes the openxc-dashboard script to not work. It returns an error stating that _curses module could not be found. This is remedied by simply installing a port of _curses from here:

http://www.lfd.uci.edu/~gohlke/pythonlibs/#curses

Note that this is different from the curses library. The curses library expects to find this module in the Python install but since the default Python 2.7 build for Windows was not built with this module included it has to be added manually. After adding this module, openxc-dashboard works beautifully.

This was important for me to figure out because I wanted to confirm that the USB backend interface was indeed working. With the dashboard running, I can clearly see that it is working and returning the expected random data provided by the emulator that I flashed into the VI.

Now, on to writing some Python scripts that do something interesting...

@kyusuk
Copy link

kyusuk commented Sep 23, 2015

We found another simple method for Windows.

  • First, copy 'vi-emulator-firmware-FORDBOARD-xxx.bin' in programming mode
  • Then, reconnect VI in non-programming mode (just connect it)
  • Device manager will show unassigned device but show 'OpenXC vehicle interface'
  • Download Zadig (http://zadig.akeo.ie/)
  • Run Zadig, and open menu Options > List all devices
  • You will see 'OpenXC vehicle interface' from the list
  • Select and Install libusb-win32

Tested on Windows 8.1 and Windows 10. No reboot required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants