Search the Community
Showing results for tags 'i2c'.
-
View File MCP2221A library There it is. The complete library for the MCP2221A. I2c adapter, I/O in a single IC. I love that one. Let me know if any bug is found. I try to make that library as much convenient as possible to use. Two version available 32 bit and 64 bit. little note: to open by serial number, the enumeration need to be activated on the device first. (open by index, enable the enumeration) It needs to be done only once in the life time of the device. PLEASE do not take ownership of this work since it is not yours. You have it for free, but the credit is still mine... I spent many hours of my life to make it works. Submitter Benoit Submitted 05/29/2018 Category *Uncertified* LabVIEW Version 2017 License Type BSD (Most common)
-
Hi I am using the MPSSE I2C drivers over a USB FT232H device, communicating with BMP280. When I read the BMP280 device ID, it is supposed to return 0x58 but the DeviceRead vi returns 0xFF. I have used a logic analyser and can confirm that the device is actually sending 0x58, but the output from the read vi is 0xFF. Has anyone had this same problem, or can anyone suggest what might be the issue? Thanks Arj
-
Version 1.0.0
442 downloads
There it is. The complete library for the MCP2221A. I2c adapter, I/O in a single IC. I love that one. Let me know if any bug is found. I try to make that library as much convenient as possible to use. Two version available 32 bit and 64 bit. little note: to open by serial number, the enumeration need to be activated on the device first. (open by index, enable the enumeration) It needs to be done only once in the life time of the device. PLEASE do not take ownership of this work since it is not yours. You have it for free, but the credit is still mine... I spent many hours of my life to make it works. -
I have a question.... The MPSSE I2C driver works great. But it does not have a Write-Read dll in it. Calling the WriteDevice and Read Device separately in LabVIEW is generating considerable delay ( ~1ms windows scheduler + labview ). is there a combined DLL for Write-Read. currently I am able to reach only about 400 samples per second with my ADC. I want to be able to use upto 10ksps. Is there any other way to reduce this delay ? Thanks for the help.
-
Hi Folks, The scenario is, I have a sbRIO 9651 and a MPU 6050 (A IMU sensor). I would like to acquire sensor data in FPGA VI, stream it to RT VI for processing and analysis and view it from windows based VI. I came across certain problems which I wasn't able to figure out. I dont have the appropriate cable to interface the sensor yet, which I have ordered, to test the VI. 1. FPGA VI: The I2C Master VI outputs a array of 14 bytes raw data (6 bytes for Accelerometer, 6 bytes for gyroscope and 2 bytes for temperature). since the data can only be written element by element in a DMA FIFO, how can I stream an array to RT VI. I did an auto-indexed for loop to write data but I dont know if this will work. 2. RT VI: Initialization of MPU6050 is done here. It involves writing a byte array sequence to I2C Master VI to configure it and then a write-read(writing a register to read data from) process to acquire data. I am not sure how to do the write- read part. I was able to do it in myRIO RT Vi as it had clear APIs 3. The single process shared variable 'RT Stop' used for communication between loops in RT VI is written a value after the loop ends which I dont know as to why. The architecture is based on the Turbine example from cRIO developers guide. I am attaching the VIs for your reference. Please have a look into the code and let me know if you find anything that needs correction. I am totally new to Real time and FPGA programming. Thanks a ton Gokul first1.lvproj RT VI.vi FPGA acq.vi first1.lvproj
-
Version 1.0.0.0
1,395 downloads
There it is... finaly... Because the code given in the FTDI web page is not convenient, not working and haven't been developed by real LABview programmer, I decided to create a library for the I2C. a version for SPI will come soon. This library is free to use. If FTDI want's it in ther site, I do not allow you to publish it since you didn't help any of your customer with LABview. but of course feel free to publish this link.