Got Gyro drift? Try Sensor Fusion !

[jhersh]

Originally Posted by tetris

Hello
yes exactly I need the WPI library functions (in the Rock Robotics directory)
Can you send it to me ? Where can I find it? I need to understand the blockdiagramms in order to
adapt the programm with my USB 8451 device.

regards

If you actually installed the FRC update then you would have these VIs. You could then use those VIs to understand the API that FRC uses so that you can port to the other USB I2C API.

I would recommend installing the "FRC Update".

[tetris]

Thanks a lot yes I did it and it works.
Nice that you help people and thanks a lot jhersh..... because other user on this forum was very unhelpful and not friendly with me!

Happy new year Jhersh and all the best in the new year 2016!!!!
Denis from GENEVA

[juchong]

Hi everyone! I hate to bring up an old post, but I want to post a shout-out to the RoboBees for providing the FIRST community with an elegant AHRS implementation!

As some of you may know, I've been working to improve the software libraries available for the ADIS16448 IMU. I ran across the RoboBees implementation and managed to integrate it into the main IMU code.

Once again, thank you very much for all of your hard work! If you would like to take a look at the code, you can find it on GitHub here.

[Bpk9p4]

Has anyone tried to use this code this year. I used it last year with great success. However i started to add this into my 2016 code and it keeps asking for a FPGA_TypedefDigitalModule.ctl does anyone know where to find this

[PhilBot]

Originally Posted by Bpk9p4

Has anyone tried to use this code this year. I used it last year with great success. However i started to add this into my 2016 code and it keeps asking for a FPGA_TypedefDigitalModule.ctl does anyone know where to find this

NI changed the VI's for several I/O devices this year. In most cases they removed the need to enter a module number, but your old code is still trying to provide one from an enumerated list. But that typedef does not exist any more.

There's probably a faster way, but if you just drill down through the VIs and locate all the ones with errors, you can just delete the "module number" constant that is giving the problem. It's not needed any more.

Phil.

[Richard100]

Bpk - If I remember correctly, you can just delete the reference to the .control in the code and the rest should work ok.

See this for a much more advanced IMU with LabVIEW code The RoboBees are using this one for StrongHold - you might like it.