I have Max6675 thermocouple amplifier with K-type thermocouple connected via Arduino Uno board.
I want to acquire the temperature signals using LabView 2016 .
I build the Cod using Maker Hub / LINX / LIFA ( labview for arduino Interface kit)
But I have Problem with the code the , what is the values for the "i2c" and "SPI channel " and the " SPI configuration" , if there is any conditions for these parameters
Hello Nather!
The following links may help you to resolve your problem
1. http://www.microchip.com/forums/m260193.aspx
2. www.ritsumei.ac.jp/~piumarta/topics4/doc/spi_i2c.pdf
3. https://electronics.stackexchange.com/questions/29037/tradeoffs-when-considering-spi-or-i2c
Hi, if you have a generic arduino compatible board using the ch340g FTDI interface, try flashing the firmware on your board first (use this link )
https://www.labviewmakerhub.com/doku.php?id=learn:tutorials:libraries:linx:sparkfun_inventors_kit:setup
then run your code, if you're sure that your script isn't the problem, if you're not sure if about your programming skills here is IC2 in a nutshell and for SPI, i recommend to make sure you have a pull down resistor on your CS pin if you have multiple SPI devices
http://www.robot-electronics.co.uk/i2c-tutorial
thank you Bhagwan Das
but for the first link I have a problem to get access
Hello Natheer!
The first link has following information:
Well, let's start with hardware:
- let's first state that they both are "Master/Slave" protocols, i.e. communication is always initiated by one Master.
- I2C only uses 2 wires, Clock & Data; Clock is unidirectional (mostly, though there is an exception) and Data is bidirectional. More than 2 devices can exist on the same bus, and they will still use 2 wires altogether (addressing is software-based).
- SPI uses at minimum 4 wires, one Clock, one Data Out, one Data In, and one CS (chip select). So, Clock is always an output going from Master to slave(s), Data In is a input, and Data Out is a output. CS is a chip select signal, which allows one (among possibly several) slave devices. So, as we can see, addressing is done in hardware.
SPI is inherently faster (up to some 25MHz, maybe more), while I2C is slower (100-400KHz). This is inherently due to the use of more signals to perform communication (in fact, beyond else, I2C uses special sequences to show Start and Stop of communication, while SPI uses CS wire).
As for software, the actual communication is similar among the two, i.e. Clock is generated by Master, and Data is written or read on edges of clock. What changes is that SPI can read & write at the same time, while I2C not. And also the Beginning and End of communication, as we saw above.
well, I suggest you using VI Package Manager + Arduino software so you can communicate easily with Labview using the Arduino module in Labview
check this out :
https://www.youtube.com/watch?v=RGRhIQneO6w
in your case see this tutorial :
https://www.youtube.com/watch?v=JT-IZKkRCzs
https://www.youtube.com/watch?v=JT-IZKkRCzs
Hello Natheer, I have the same problem as you. Did you interface the Max6675 SPI with arduino to Labview, using Linx?
If you did it, can you share your vi?
I found another solution, using the Serial Interface of Labview, but it does not look very performing and reliable. You can check the following link:
https://www.youtube.com/watch?v=HkZylQ9GGYM
- Badges
- Science topic
- Similar topics
- Chemistry