ADI 16448 Registry Set Error

traverda · January 10, 2018, 6:06pm

Last year our team used the ADI 16448 IMU in LabVIEW, and this year the associated IMU vi’s have changed so that they no longer properly “play” together. It appears that the “IMU 16448 Open” vi has been very recently modified (github.com/juchong/ADIS16448-RoboRIO-Driver), but not the “IMU 16448 Set/Get Registry” vi’s. The Open exposes an “ADI IMU DevRef Out” data type, and the associated “ADI IMU Registry Set” currently expects an “ADI Interrupt DevRef In” type as input. The corresponding “ADI IMU Registry Get” likewise outputs an “ADI IMU Interrupt DevRef” type, not an “ADI IMU DevRef” output the “ADI IMU Reset” is expecting. Is there a conversion between the two data types that I am missing?

juchong · January 14, 2018, 11:49pm

traverda:

Last year our team used the ADI 16448 IMU in LabVIEW, and this year the associated IMU vi’s have changed so that they no longer properly “play” together. It appears that the “IMU 16448 Open” vi has been very recently modified (GitHub - juchong/ADIS16448-RoboRIO-Driver: ADIS16448 IMU Library for FIRST Robotics and the RoboRIO designed for use with WPILib), but not the “IMU 16448 Set/Get Registry” vi’s. The Open exposes an “ADI IMU DevRef Out” data type, and the associated “ADI IMU Registry Set” currently expects an “ADI Interrupt DevRef In” type as input. The corresponding “ADI IMU Registry Get” likewise outputs an “ADI IMU Interrupt DevRef” type, not an “ADI IMU DevRef” output the “ADI IMU Reset” is expecting. Is there a conversion between the two data types that I am missing?

Hi! It looks like in my haste to finish updating the driver I failed to clean up. dkt01 on GitHub went ahead and cleaned up the DevRef issues. If you pull and use the new code, you should be good to go! I’m also working on building an updated installer that should be online later tonight.