06-02-2014 06:39 AM - edited 06-02-2014 07:00 AM
I work with myRIO for implelementing of SMBust protocol. After few trials I decide to convert existing I2C master solution for myRIO - look good, separated code consumes 65% total slices in compilation.
(bat the way: why so much?)
Did any of you made implementation of SMBus at myRIO ? any tips? How can I reduce amount of consumed slices ?
06-05-2014 03:54 AM - last edited on 01-25-2024 05:45 PM by migration-bot
Good Morning MikrobiUK,
Officially, we can only communicate with myRIO by two ways: I2C and SPI and there is an API developed for you to use both protocol as shown below:
“SPI and I2C Driver API - National Instruments”
Hence we don’t recommend you to use the SMBus protocol.
Please let me know if you have any other thought.
Thank you.
Lanxi
06-09-2014 02:59 AM
Well that is my starting point, I need to spent more time with that. Also I2C implementation dedicated to myRIO looks fine.
And yes, I would like to use proper I2C protocol, but I have hardware that operate with SMBus protocol and I need to communicate with that.
I will continue my work with that..