12-01-2015 03:12 AM
I get this message ni compactrio driver support for labview 2015 is missing. Is very fustrating. I installed all the cd that came along my rio, i also have something called toolkit installed allready. Its when i start a program downloaded from net mybot ( segway program) i get this message. Has anyone the same problem? solution
12-01-2015 05:23 AM
Did you install the drivers also?
You need to have the NI-RIO driver installed. You should find it on the DVD's or you can download the driver on the NI site.
12-01-2015 06:01 AM
12-01-2015 06:29 AM
Please go into NI-MAX and verify that you have installed all the drivers, and what version you have installed.
12-01-2015 06:31 AM
Hi student,
what did you install?
"something called toolkit" and "some driver dvd" isn't enough information fur us to tell you what's wrong! Please check, what software you did install (MAX -> Software section).
You need to install drivers after you did install a new LabVIEW version. And you need to install drivers for each LabVIEW version you want to use…
12-01-2015 06:33 AM
If you installed LabVIEW 2015, you need the latest cRIO and DAQmx drivers. Any driver set from 2013 will not be compatible with LabVIEW 2015.
12-01-2015 07:01 AM
Hi!
Thanks, I opend max now and took a picture of what drivers that is installed. see attatchment / also a picture of the DVD i installed.
The program i try to open is a segway program from this forum page https://decibel.ni.com/content/docs/DOC-34547 also this https://decibel.ni.com/content/docs/DOC-30571
12-01-2015 07:06 AM
Did you install the cRIO drivers AFTER installing LabVIEW? I would try reinstalling the drivers.
12-01-2015 07:14 AM
yes, I installed the drivers last.
Thanks! I will try that reinstall
12-01-2015 08:15 AM
Thanks! looks like it helped for the error I had didn show up 🙂
No I got a new one 363013 message attatchment.
I looked it up on NI now and it says
http://zone.ni.com/reference/en-XX/help/373925B-01/myrioreference/myrio_error_codes/
−363013 | A timeout occurred during the last I2C read/write operation. |
Any suggestion about this?
From the message attatched there where a lot more information than when I looked it up.