12-01-2015 08:30 AM
We are going to need to have code in order to help diagnose that issue. I2C is a communication protocol between devices. Perhaps your other device was shut down or stopped sending data for some reason.
12-04-2015 07:37 AM
Hi!
I installed the dvds on my pc 2 to se if I get the same error, the driver error occours there to it super wird must be alot of people having that error.
But the other error I2C . is it possible you could study the code or just see if you are able to open it without fault message?
The program is downloadable from here https://decibel.ni.com/content/docs/DOC-34547 since its not my program I dont want to attatch the file.
the file is called myBOT-v1.zip (3.7 MB)
Can the fault be caused because I use a newer version than the program itself? 2013 is the program file while I use 2015?
Best regards
Studentent Norway
12-04-2015 07:47 AM
12-04-2015 08:14 AM
Hi!
Here is a screenshot from MAX. Its only the I2C code error code 363013 I am having problem with at pc1, at the moment as the driver fault message dissapear after installing the drivers once again.
12-05-2015 12:54 PM
Some updates:
The same fault message I2C code error code 363013 occur on 3 diffrent PC,
2 of them is mine while the last pc is a collegue of me that also get the same fault message.
We have wired up the same segway with parts from digilent.com
Nr. | Name | Link | |
---|---|---|---|
1 | Motor/Gearbox, 1:19 Ratio | https://www.digilentinc.com/Products/Detail.cfm?NavPath=2,403,625&Prod=MT-MOTOR | |
2 | Wheel Kit (pair) | https://www.digilentinc.com/Products/Detail.cfm?NavPath=2,403,621&Prod=MT-WHEELK IT | |
3 | PmodDHB1 - Dual H-Bridge | https://www.digilentinc.com/Products/Detail.cfm?NavPath=2,401,1163&Prod=PMOD-DHB 1 | |
4 | PmodGYRO 3-Axis Digital Gyroscope | https://www.digilentinc.com/Products/Detail.cfm?NavPath=2,401,937&Prod=PMOD-GYRO | |
5 | LiPo Akku, 11.1V, 1300mAh | http://www.conrad.ch/ce/de/product/239507/Hacker-LiPo-Akku-111-V-1300-mAh-25-C-S tecksystem-EC3-XH |
12-05-2015 03:12 PM
It is you who has the code, and you who has the myRIO and all the electronics.
Now you need to find your why you have a timeout.
I can't tell you that with the information that you are giving right now.
You need to do some debuging to see where and what is giving the error, and find out what to do about it.
12-05-2015 04:08 PM
Its not only me having the fault, we are actually 3 person that has the same fault. So 4 diffrent pc , 3 diffrent myrio licens .
I have googled the fault, installed all myrio dvd software serveral times, and dobble check all wires connected to myrio. Testet motorcard in a simple program from myrio essensial guide 18 H-Bridge and Geared Motor worked fine.
Do you have any tips how to locate the fault? That would be very nice. I am very new to myrio so I am willing to learn as much i can, but I need some guidelines what to search for.
12-05-2015 04:15 PM
It has nothing to do with your installation of LabVIEW or the licenses.
It is all in the code and the hardware you use.
You need to find out where the error is in the code. Look deep in the code, and try to understand it.
It is most likely the communication to the Gyro.
Make sure that is connected correctly to the myRIO.
Make a small testprogram that talks to the gyro.
12-05-2015 09:01 PM - edited 12-05-2015 09:05 PM
..
12-05-2015 09:03 PM
Nice!
After you reply, I went to ftp://ftp.ni.com/evaluation/academic/project-guide.pdf and found a lesson for my gyro board at page 95 lesson 22. I first tried with my old wiring I then got a faulty message “Error -36011. By looking at page 98 in the guide it written below.
NOTE: Double-check the “SDA” and “SCL” connections should you see the message “Error -36011 occurred at myRIO Write I2C.vi” or similar; this message indicates that NI myRIO did not receiving an expected acknowledgement from the PmodGYRO I2C-bus interface.
After reconecting switching wires the faulty message dissapear and running the mini gyro VI project i could see the gyro worked fine.
So I than started up the Mybot.vi program again hoping finally open it without any fault , but that was probably like believing on SantaC.
But it looks like I got the I2C fault away finally thanks! The next error code is the same i had at the beginning of this tread , was so sure that it was solved. I have installed the drivers so many times now.... dont know what to do next...