New ONavi Sensor Drivers for Windows (32 & 64-bit)

New ONavi Sensor Drivers for Windows (32 & 64-bit)

log in

Advanced search

Questions and Answers : Windows : New ONavi Sensor Drivers for Windows (32 & 64-bit)

1 · 2 · 3 · 4 . . . 6 · Next
Author Message
Carl Christensen
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 9 Jan 08
Posts: 1039
Credit: 11,336
RAC: 26
Message 3081 - Posted: 12 Aug 2011, 22:24:19 UTC
Last modified: 12 Aug 2011, 22:25:11 UTC

If you are having trouble with your ONavi sensor - please try out these new drivers and report back in this thread as to your success (or lack thereof)

32-bit Windows ONavi Sensor Driver

64-bit Windows ONavi Sensor Driver

Profile Robert Pick
Send message
Joined: 6 Nov 08
Posts: 6
Credit: 30,313
RAC: 512
Message 3084 - Posted: 12 Aug 2011, 23:27:56 UTC

Workes like a charm!!!!!! Took 5 min. to install on my Eee Pc. I shall let the task I'm running on my watt hog finish and start up a new one on the ASUS. Then it's 24/7 till something else busts. Thanks Again Carl, Pick

Timothy Kirkpatrick
Send message
Joined: 9 Jul 11
Posts: 24
Credit: 22,885
RAC: 525
Message 3087 - Posted: 16 Aug 2011, 17:24:24 UTC

I've been trying to get this O-navi 16bit sensor to work under XP pro 32bit and win7 ultimate 32bit. Tried the new driver on both OS's and it works for anywhere from 30mins to hours, then something tanks. Now I can't get it to see the sensor on win7 no matter what I do. The appl is still running, but not incrementing progress and pulling up the graphics shows 'no sensor found, demo mode'. Computer triggers show trigger sent, but sensor not found. I've been messing with this since I got the sensor about 3 weeks ago. I've been running BOINC on linux and windoze since 2000 and never had this much of a hassle with an appl. I've been involved with computer hardware/software since 1975 (Unix). Platform is a Dell GX620 SFF with max ram @ 4GB and CPU=Intel pentium D @ 3.4GHz. Everything else has no issues. I'm ready to pitch this whole QCN deal and forget about it. Any advice/info from anybody would be appreciated.
Thanks for the updated driver, but no-go so far.

-tim k6tpk
tpk@sonic.net

Timothy Kirkpatrick
Send message
Joined: 9 Jul 11
Posts: 24
Credit: 22,885
RAC: 525
Message 3088 - Posted: 16 Aug 2011, 17:43:17 UTC

I forgot to add that the O-navi sensor works as advertised under OSX86 10.6.7 on my Dell 9150 hackintosh using almost the same hardware as the GX620. It also seems to keep running on win 7 on my HPC workstation which has a Gigabyte mobo, AMD Phenom 1090T, 16GB Corsair mem, XFX Radeon HD5970 and a Corsair 850W PS. I run Linux, openBSD and Open Solaris 99% of the time and win 7 when I need to do something with odd-ball multi-media not supported under linux/Solaris. I only run the workstation from 0800-2300 7 days due to the cost of power. That's why I want QCN to run on the Dell since it runs 24/7 for my VWS weather station and BOINC.

Thanks
-tim k6tpk
tpk@sonic.net

Carl Christensen
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 9 Jan 08
Posts: 1039
Credit: 11,336
RAC: 26
Message 3090 - Posted: 16 Aug 2011, 20:57:02 UTC - in response to Message 3088.

hmm that's odd, I think the ONavi, since it uses a "middleware" driver to turn the USB into a 'virtual modem/serial port" is a little more sensitive to USB hardware than our other sensors. For example, it doesn't seem to work on really new Apple iMacs (2011 vintage). I still haven't figured that out.

DeborahLynn
Send message
Joined: 2 Aug 11
Posts: 3
Credit: 10,699
RAC: 1
Message 3115 - Posted: 30 Aug 2011, 6:03:43 UTC - in response to Message 3087.

Tim - I agree. It's a little frustrating to get up and running on this project. I'm somewhat technical and as far as I can tell, I've done the right things but can't get this project to work. QCNLive says I'm in Demo Mode, but it does not seem to be updated with the current gen of sensors (none of the settings for detecting the sensor worked), ditto regarding the triggers web page- it indicates the sensor is not detected (I think I installed the correct device driver), and so on.

I'm mailing the project staff again to see if someone can get me up and running.

K5QP
Send message
Joined: 10 Aug 11
Posts: 4
Credit: 24,201
RAC: 570
Message 3120 - Posted: 2 Sep 2011, 0:40:54 UTC

To those having problems with the ONavi sensor, I have found a few solutions that may help. First assign the lowest possible available com port to the device. High number com ports seem to take a lower precedence. Next determine if other applications that have USB access are absolutely necessary. Some devices can interrupt the com port process and that will cause the sensor to crash. And lastly under the windows performance be sure to allow background applications to have equal or prioity processor use. Since I have used all these on my installation it has not crashed or lost the sensor. In fact if there is any interruption then the sensor resets itself. I hope this helps. I have had mine up and running for a couple of weeks now and it seems to be very stable.

Profile wd9dui
Send message
Joined: 25 Mar 10
Posts: 51
Credit: 30,147
RAC: 278
Message 3121 - Posted: 2 Sep 2011, 2:36:25 UTC - in response to Message 3120.

K5QP/Mike K6TPK /Tim
I think that we have something here, I had an old JoyWarrior 24F8 USB, it would spend ½ it’s life resetting, I could not figure what was going on with it, (RF?) I had put chokes in line and caps to see it that would fix it. NOT! I gave up and got a new ONavi A 16-bit USB today and seems to play a lot better. It is kind of funny that you started talking about Com ports as when I went in to put in my HF connections for JT65 I could not believe the number of com ports being used. I have over 30 in use! I was not aware that USB consumed com ports. How do you go into windows and tell which has what port? Do you pull out USB connections and put them in by priory? The other thing that I notice that my MagicJack seems to act funny even though I have a cable connection. I could see how if all of these comm. ports are in line things will not work the way it should….



____________

K5QP
Send message
Joined: 10 Aug 11
Posts: 4
Credit: 24,201
RAC: 570
Message 3123 - Posted: 3 Sep 2011, 1:06:48 UTC - in response to Message 3121.

To get to your com ports go to control panel, then System, then Hardware, then Device Manager, then scroll down to Ports. Find the XR21V1410 USB UART and it will have a com port number at the end....Right mouse click on it and go to properties...Then go to Port Settings and click on the Advanced button. At the bottom of the Advanced Settings you will see the com port in a window. Click on the button on the right side of that window and you will see all the available com ports as well as the ports that are occuppied. If you do not have a low number (less than 5) then unplug all your usb devices and plug in your ONAVI device first or as providing you do not have a mouse or keyboard that has to be in first...anyway once the computer finds your ONAVI device then you can load/plug in the remainder of the usb devices. As for your magicjack device. That will likely be an interruption in the com port activity since the magicjack device continually checks into the internet via its usb connection and that will interrupt the continuity that the ONAVI device needs to keep the data stream consistent. I use my magicjack device on a acer stand alone pc that is not on the machine that is doing the QCN activity. I hope that this helps....Later

Profile wd9dui
Send message
Joined: 25 Mar 10
Posts: 51
Credit: 30,147
RAC: 278
Message 3125 - Posted: 3 Sep 2011, 1:57:22 UTC - in response to Message 3123.

Yes, thanks for the response. I got in there this AM and bumped it up, I also have pulled out the other hubs and just have the keyboard and mouse plugged in. I see that it still likes to spend a lot of time calibrating….. Over all the new 16bit ONavi is working a lot better than the old one, the x-y-z lines don‘t go flat, it also a lot more sensitive.
Gary

____________

Profile wd9dui
Send message
Joined: 25 Mar 10
Posts: 51
Credit: 30,147
RAC: 278
Message 3126 - Posted: 4 Sep 2011, 18:44:35 UTC

Good news! After playing with this for the past few days, it appears that the resets have settle down. I found that when changing ports it can cause problems, -no sensor detected- . It took me a while but after putting the sensor on the next available open com port things started to work again. I also have the hubs back in line and MagicJack. It would be nice if there was a 3rd party software that would allow you to go in and look and see what is going on with the USB/com ports and assign priority’s etc. I guess you could spend days on this one! It is a science in it self…

have good holiday.
Gary

____________

Jim1348
Send message
Joined: 6 Sep 11
Posts: 28
Credit: 8,606
RAC: 0
Message 3132 - Posted: 6 Sep 2011, 13:09:25 UTC - in response to Message 3081.

If you are having trouble with your ONavi sensor - please try out these new drivers and report back in this thread as to your success (or lack thereof)

I just installed the ONavi 16-bit with the new drivers along with QCN Live and BOINC, and everything installed fine (ONavi on Comm Port 3). And when I open QCN Live, I can see the 2D/3D data OK after calibration. The problem is that it only works once, or maybe twice. If I open QCN Live thereafter, I get "Demo mode: no sensor found" message until I reboot, and then it works fine again.

I am running Win7 64-bit, and have a USB WiFi adapter. Otherwise, I have only the keyboard and mouse connected to the USB ports. This is a dedicated BOINC and Folding@home machine, so I don't use it for other purposes.

Q: If I get the "no sensor found" message, does that mean that BOINC is also not sending data? If that is the case, I can live with it for the moment, since I have no pressing need to see the data, but I am wondering what it means.

Jim1348
Send message
Joined: 6 Sep 11
Posts: 28
Credit: 8,606
RAC: 0
Message 3133 - Posted: 6 Sep 2011, 18:04:09 UTC - in response to Message 3132.

Guess what? It is BOINC/QCN Sensor that is causing the problem with QCN Live. If I suspend the BOINC/QCN Sensor application, the problem does not reoccur after a reboot. Note that I can run other BOINC applications (e.g., World Community Grid) without a problem on BOINC 6.12.33 64-bit. Apparently the time window when I could access QCN Live corresponded to the time before BOINC launched QCN Sensor after a reboot (about two minutes as I recall).

I guess it means that BOINC grabs the com port or whatever, and does not let go. Is this known behavior? I have not seen it mentioned before.

Carl Christensen
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 9 Jan 08
Posts: 1039
Credit: 11,336
RAC: 26
Message 3136 - Posted: 6 Sep 2011, 19:37:15 UTC - in response to Message 3135.

the ONavi doesn't "like" to be used both by the BOINC/QCN and the QCNLive -- so it could be that it is working on BOINC, but when you run QCNLive the BOINC/QCN has full control of the sensor, so you don't see it in QCNLive.

The drivers are a little flaky though unfortunately - but first make sure you are not trying to run both programs at once (the JoyWarrior was "friendlier" for running both BOINC/QCN and QCNLive at the same time).

Profile wd9dui
Send message
Joined: 25 Mar 10
Posts: 51
Credit: 30,147
RAC: 278
Message 3137 - Posted: 6 Sep 2011, 20:03:52 UTC

Jim, try to stay away from com3, I thing something else is using it. I ran into same problem, move away to the next open port and restart. See if it starts to work.
Gary

____________

Jim1348
Send message
Joined: 6 Sep 11
Posts: 28
Credit: 8,606
RAC: 0
Message 3138 - Posted: 6 Sep 2011, 20:44:55 UTC - in response to Message 3137.

Jim, try to stay away from com3, I thing something else is using it. I ran into same problem, move away to the next open port and restart. See if it starts to work.
Gary

Gary,
Thanks, but no go. I tried both ports 4 and 30. (Windows complained that these ports were in use, but apparently it complains about all the ports.) At any rate, it was the same as for port 3: I could get either QCN Live to work, or BOINC/QCN Sensor, but not both at the same time. It is no big deal; I wasn't planning to look at the graph anyway except to see if the ONavi sensor was working. It looks like 20 meters sounds on a bad day.
73,
WF3X

Profile Betsy C.
Avatar
Send message
Joined: 6 Sep 11
Posts: 15
Credit: 28,547
RAC: 272
Message 3140 - Posted: 7 Sep 2011, 3:39:57 UTC

This is my first post here. I was so excited about receiving my sensor today, and I can't wait to really start to familiarize myself with all of this. I am also receiving the message "demo mode- sensor not found". The only other thing attached to my laptop is a fan that sits underneath it. Could it be causing problems? Also, I was halfway through the install and having problems, then I saw this thread. I should have looked here first! Should I perhaps uninstall/reinstall the programs? Thank you.

Jim1348
Send message
Joined: 6 Sep 11
Posts: 28
Credit: 8,606
RAC: 0
Message 3143 - Posted: 7 Sep 2011, 11:49:41 UTC - in response to Message 3140.

I am also receiving the message "demo mode- sensor not found". The only other thing attached to my laptop is a fan that sits underneath it. Could it be causing problems? Also, I was halfway through the install and having problems, then I saw this thread. I should have looked here first! Should I perhaps uninstall/reinstall the programs? Thank you.

Do you have BOINC installed? I would just reboot and then open QCN Live immediately, before BOINC/QCN Sensor has a chance to grab it.

However, after you are finished viewing, you will need to reboot again (without opening QCN Live this time) so that BOINC can send data from the sensor to QCN. You can check to see if BOINC is sending data by looking at the BOINC manager under the "Tasks" tab to see if the "Progress" percentage is increasing for the QCN Sensor application. At least that is how it works for me under Win7 64-bit, though it might be different for WinXP or other operating systems.

1 · 2 · 3 · 4 . . . 6 · Next
Post to thread

Questions and Answers : Windows : New ONavi Sensor Drivers for Windows (32 & 64-bit)


Return to Quake-Catcher Network Sensor Monitoring main page


Copyright © 2013 Stanford University