NI-8452 SPI communication with texas instruments ADS1278

I'm looking for some help with setting up a Labview VI to use SPI communication between an NI-8452 and a texas instruments ADS1278 A/D converter evaluation board. From all of the sample VI's I have seen the LabVIEW routines vary widely for different models of Texas Instruments ADC's. My issue is how to deal with the DRDY pin on the ADC; it is an active low output from the ADC and signals when valid data is ready for retreival.
There is a DRDY pin listed under the SPI stream configuration property node, but I am not sure how to set this up as it is a seperate pin from the standard SPI 4-wire communication (SCLK, MOSI, MISO, and CS). Also, this ADC does not use the chip select (CS) line. I would like to set the program up so that an interrupt is triggered when the DRDY pin pullls low and enters a standard SPI stream routine.
Any information on how to deal with this DRDY signal would be greatly appreciated.
http://www.ti.com/lit/ug/sbau197/sbau197.pdf
http://www.ti.com/lit/ds/sbas367f/sbas367f.pdf
Thanks,
Grant
Attachments:
ADS1278 SPI timing.jpg ‏86 KB

I highly recommend saving the NI-845x Hardware and Software Manual if you are looking in using SPI communication with the 8452, as it is extremely helpful. We can see on page 387 (Chapter 14, section 4), there are descriptions for the extra SPI pins. The DRDY pin is configured as an input using GPIO1, so P0.1 for the 8451 and DIO1 for the 8452.
Also, I would recommend posting any future SPI communication or NI-845x questions to the Automotive and Embedded Networks forum. This way you'll get exposure to other users that are more familar with what your looking into.
Hope this helps!
Daniel K | NI Applications Engineer | Certified LabVIEW Developer

Similar Messages

Teststand best practices architecture for communicating with TCP instruments

Hi,
I am using Teststand 2014 and LabVIEW 2013 SP1 as the module adapter.
My Teststand sequence file includes communication with 3-5 different instruments via TCP/IP.
Such as Spectrum analyzer, generator and other RF measurement devices.
There are many steps located in subsequences that implement code to communicated with these devices whether to fetch , query or write.
What is the best architecture to implement this program ?
As I can see it there are many possibilities, such as :
1. Launching a subsequence as a new thread in the Sequence Setup. This subsequence calls a VI that dynamically register for events/queue that can be launched from any step. (in this case there is a VI running in the background that can perform Write/Read/Qurey to the instrument and he is triggered from any step using an event or dequeue element)
This option can be duplicated for any instrument or only once for all of the instrument with prioritizing the event queue.
2. Creating a communication reference in the Setup of the Main Sequence. And passing it to any step that need it. (there is also the question how to pass this reference… in Teststand globals or in LabVIEW queue).
another 2 small questions that I encountered -
Is using LabVIEW queues and notifiers in TS steps and obtaining their reference (in the LabVIEW code) by name is considered best practices ?
If I would like to run only one VI in a new thread, should I use a new subsequnce and set it as a new thread or use the Run VI Asynchronously ? what are the differences ?

I use Action Engines to hold my VISA Sessions and just write my LabVIEW VIs to use those to send commands and read data. Any returned data can be analyzed in the VI or passed on to TestStand as a step result. You just need a sequence to run at start up to initialize your Action Engines and another one to close them.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Kinect for windows v2 with Texas Instruments chipsets

are the issues with other than Intel or Reneas chipsets going to ever been resolved...? Unfortunately those SO specific requirements are only becoming known after buying the sensor and troubleshooting why is not working, since it is only then when you
realise all these 'hidden' sites where those specificities are mentioned. The official site states very general requirements so people are found buying the sensors expecting to work, as i did. The weird thing is that with the Texas Instrument USB3 chipset
on my laptop the sensor seems to work perfect the first time connected and only causes the port to stop working after the sensor is shut off and then restarted. So there seems not to be an issue of bandwidth or power, after a reboot of the laptop the sensor
is again found to be working well. If somehow the sensor is kept on, then all the samples and kinect apps work perfectly...the problems with the TI chipsets comes only when the sensor is off and then on again without a pc reboot. Are there any suggestions,
workarounds solutions for this. Is MS planning to ever attend these issues or is this a sensor that will work only on these specific configurations...?

Intel and Renesas chipsets are the only chipset that are known to support the full USB3 specification that Kinect requires. The specification can be found here: http://www.usb.org/developers/docs/
As for what can be done, you will have to use a different machine or if you have a desktop you can purchase an PCI Express expansion card that has this chipset, as long as it is PCI Express 2.0 compliant and the motherboard is Gen 2.0+ enabled for the
PCIx slot.
Carmine Sirignano - MSFT

Reading data from mlx90129 rfid tag chip by using spi communication with labview?

Hi,
i have evb90129 evalution board in that mlx90129 chip and external memory (cat25128) and three external sensors are there, i am logging data from chip by using rfid reader it ok i am reading. at the same time i configured spi communication and i am trying to read data i am reading data from internal memory not from external memory i tried but i didnt suceed , now can i use labview to read data from mlx chip and external memory. for spi communication i am using sparkfunction atmega168 microcontroller and also i have spi to usb cable? now can i communicate or i required any devies? is it possible?
thanks in advance,
biji.

I suspect the culprit to be the first parameter to your function actually. Calling another function requires the caller to allocate any buffer with a big enough size for the function to write something into. Allocate that array by using Initialize Array with U8 as type and the correct number as size. Pass this size also as read_length. While your code doesn't make use of this I think the third parameter to your function is either wrong or unnecessary.
As you use it now it is really nothing more than a local stack variable which you could declare inside the fucntion just as well. On the other hand what you probably want to do is have a function prototype like:
extern "C" _declspec(dllexport) unsigned char read_Sensor(unsigned *char read_data, unsigned long read_length, unsigned long *byte_transfered);
But you will have to do some modifications in your C code to support that parameter correctly.
That all said, doing the same in LabVIEW using VISA functions would have been done with about two VISA nodes, no DLL headaches and probably already long ago working.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Macbook pro models with "Texas Instruments" firewire chipset

Hi
Please, anyone knows wich macbook pro models(MA896LL/A, etc..) in 2007 and 2008 have "Texas instruments" or "Agere" firewire chipset?
Overall between MA896LL and MA896LL/A (mid 2007 and late 2007)
Thanks

Well, I've run a few tests, and learned something new.
CS6 on my MacBook Pro has three acceleration modes now: Software, Hardware (OpenCL) and Hardware (CUDA).
I've run software only... not so great. Then I ran Hardware Open CL, and it "acts" like CUDA did on my Mac Pro with GTX 285... bars that were red turned yellow, and some things ran without rendering! I was pretty surprised by this, as I have only 512MB VRAM, not 1GB VRAM on the 650M.
This is only my not-very-serious edit-on-the-road system, so I didn't spec it out to be a monster editing laptop, but I'm extremely pleased by how well it runs with CS6. I have two very nice, new SSDs inside; one for OS X/apps, and the other for media, as well as 16GB RAM. Each SSD runs at 500MB/sec +/- whether read or write, despite the second SSD being in the space where the optical drive was.
It's too bad there's not just a *wee bit* more space where the optical drive was... or I'd try to stuff THREE SSDs inside, and RAID two of them for media.
So far, I'm really pleased with how well it works with only 512MB VRAM, which was the question I had wanted answered.

NI USB 845x SPI communication with Max1108

Hi,
I'm trying to communicate with the Max1108 (datasheet attached)
when using 8451 Test Panel I get random results,only once i got expected results and i captured this moment(i cant reproduce it somehow)
I followed this code,
http://forums.ni.com/ni/attachments/ni/170/283809/1/MLX90316%20Read.c
which was published by NI in forums..and got same results when I use script functions(code1), and empty read buffer when using regular spi API's (code2)
Please ignore the c# adjustments ..
what am i doing wrong ?
Thanks,
Ori
Attachments:
MAX11008 DS.pdf ‏646 KB
code2.txt ‏9 KB
code1.txt ‏3 KB

Solved, thanks for your "help"

SPI communication with 93LC46 EEPROM

Hello awesome NI readers,
I've been trying to communicate with my 93LC46 EEPROM device via SPI but haven't had much success. I am using the NI USB-8451 to interface with it.
The 93LC46 device is active high for chip select so I used the "General SPI Write Script" example and modified it a bit.
I've connected 4 wires between my device and the USB-8451 device. SDI, SDO, SCLK and CS. pin 16 on 8451 to my SCKL, pin 15 on 8451 to my SDO, pin 14 on 8451 to my SDI and pin 13 on 8451 to my CS.
The ORG pin on the 93LC46 is pulled down to ground (see wiring diagram) so it's a 128-8bit organization. The read instruction I am trying to send is 10bits long so I am sending 2 bytes, one byte at a time.
When i try to run my program and look at the SPI signal on my oscilloscope, all i see is my 4 lines toggle their signal once and then nothing. Obviously, I'm doing something wrong since I can't even see my clock signal running! I have attached the datasheet of my EEPROM device the wiring diagram for it. I also attached the code I am using.
Any help or advice is greatly appreciated! Hope this makes sense.
Thank you.
Serge

Hi j_bou,
Thanks for taking the time to reply. I did try the basic API but I realized some assumptions the code was making did not work for my device. The pulse that I was seeing on the SPI lines was a mix of low->high->low or high->low->high.
Since I couldn't see any clock running, I was thinking that my EEPROM must be a slave to something else and running off their clock. This EEPROM is part of a board assembly so I was looking at what other IC's were on the board and there's a PIC18F252, so i'm thinking I have to write code to talk to the PIC to be able to talk to the EEPROM and that I cannot talk to the EEPROM directly. Hopefully, it works out!
Don't know if I should keep this thread open until my problem is resolved because this issue might be related to something different that what I am asking here.
- Serge

SPI communication with PCMCIA 6062E Card. Is it possible?

Good night, budies. I need your help, cause I want to communicate via SPI with the 6062E Card. Is it possible?
Thank youU!

You already asked this question.

Difficulty about communication with an instrument

hi,
I have a instrument which can measure voltage .According to the Getting Started with Labview,I could not communicate with it yet?
what should I do?
what the reference to look?

Sorry again............your info is not really helpful.........
with Google I only found a "Door closer" Type UA304.
Find attached a vi - made for HP34401-DMM connected via GPIB;
maybe this gives an impression, how to handle such kind of
instrument.
Hope this helps.
Regards and best wishes for 2005.
Werner
Attachments:
HP 34401_DMM_test.zip ‏161 KB

Need urgent help with communicating with the HP 4155B analyser with Labview

i folks,
I'm currently trying to communicate with our HP 4155B semiconductor pamaremter analyser. I do not have experience with GPIB yet. I have installed the NI VISA.
I was wondering if anyone could help with getting me started on how to start communicating with the device using Labview.
I'm not certain where to start.
Kind regards
Rob

Hi,
Thanks for the help. I now have communication with the instrument.
I was wondering if it's possible to to setup a data measurement (I-V Sweep) and be able to read the measurement data in realtime as it is being measured. So I basically see the graph updating itself on the PC during the measurement.
Is this possible? Could anyone give advice on how I can go about this or are there any examples that can help me understand how to do this?
I'm not completely sure how to initialise the instruemnt for communication and handle VISA WRITEs and READs. within LabView
Best regards
Rob

Any LabWindows/CVI examples for SPI communication using DAQmx?

I have a PXIe-6363 module in a PXI running as a real time target, and I'm trying to talk to an accelerometer that communicates with SPI. I know the 6363 isn't one of the special modules built for SPI, but my understanding is it should be capable; the issue is just the programming. I've seen examples of this for LabVIEW using DAQmx. Are there any examples out there for doing it in LabWindows/CVI?
I'm looking to save time and avoid reinventing the wheel here. SPI is easy on an Arduino, so it should be doable in LabWindows/CVI, right?
Thanks,
Matt

Hey Matt,
I was unable to find any full examples of SPI communication with DAQmx in C. My best suggestion would be to use the LabVIEW examples and implement the same series of function calls to implement the LabVIEW code in C. The DAQmx C API is good about keeping a standard with naming conventions to map with the function names in LabVIEW.

Commands to FTDI virtual COM port via NI VISA interfere with communication with FTDI chip using D2XX drivers

Hello!
I am trying to communicate with a DLP Design module DLP-USB1232H which uses an FTDI chip. My program uses the D2XX drivers. It works, but...
In another program that runs at the same time, I'm communicating with another instrument via a virtual COM port (VCP) that uses an FTDI UART. In this program, I use the VISA Serial Port functions. It works, too, but...
The first program has the capability of listing all the FTDI devices in the system prior to choosing the right one to communicate with. When the VCP is plugged in, it lists it (FT232R USB UART) along with the DLP-USB1232H and communication with the latter device works. But as soon as the second program sends a command through the VCP, the first program no longer "sees" any FTDI device. It stops working.
I have tried 2 different FTDI VCPs; one a standalone cable and the other built in to the instrument.
I’m using Windows 7 32-bit. My programs are both LabVIEW 8.5 executables.
Is VISA "taking over" the channel to the DLP-USB1232H? Does someone who understands NI's implementation of VISA have any ideas on why VISA is doing this? Or if something else is going on?
I'm also interested in workaround ideas. I've tried a "Prolific" VCP, but most drivers don't work and the one that doesn't give an error in Device Manager doesn't communicate with the instrument.
Cheers
Halden
Solved!
Go to Solution.

Halden,
It really sounds like you have a resource conflict. That occurs when two programs or parts of programs try to use the same device or port at the same time. Your Get Device Function probably tries to open a session with each port (as you increment the index). When it hits a port which is being used by the other driver, it cannot open the session and stops working? Have you examined the errors returned by each program? The VISA drivers will return an error when the port is in use. I do not know about your program or drivers, but I would expect some kind of error. Automatic error handling in LabVIEW will not catch errors from a driver if it does not translate them to LV error clusters. So do not count on automatic error handling, if you use it, to display all possible errors.
Lynn

Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)

HI, I am having query regarding; Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)
LabVIEW: LabVIEW Instrument Control Course Day 1 coves subject like Communicating with Instruments This lesson describes how you can use LabVIEW tocommunicate with instruments. You will learn how touse NI-VISA, NI Spy, SCPI commands, and theInstrument I/O Assistant to perform instrument I/O. My question is to you,Does LabWindows/CVI: IVI Instrument Driver Development Course covers similar kind of training like Communication with Instruments? I am more interested in learning How to use SCPI commands to perform instrument I/O. Will you please guide me? So I can choose correct training course. Thanks & Regards,Jay +91 90110 62790EXFO Electro Optical Engineering India Pvt. Ltd.701, 7th floor The Ceribrum IT Park,Kalyani nagar. Wadgaown Sheri India, Maharashtra, Pune 411014

stick to the original thread.

Dual spi device with one master and one slave on the PC end

The powers that be want to emulate a hight speed RS-232 connection to an instrument we are building. We don't want to poll the instrument to see if it has data. They want the instrument to have both master and slave SPI busses so that it can push data to us.
I need to find the PC hardware to do this that is compatable with LabView so I can test it. It doesn't have to be a single device. It could be two as long as one can be master and the other slave. We have the NI USB-8452 but it can't be slave.
TIA Norm
Attachments:
Dual SPI.png ‏26 KB

Hi Viper
You are right, the 8451 can only be configured as an SPI Master. For creating a slave you would have to choose an FPGA based solution. Depending on the hardware from NI that you currently have, you can choose from different FPGA cards or devices. I found some links that might help you with your search:
Community: SPI Slave Device in FPGA
White Paper: Implementing SPI Communication Protocol in LabVIEW FPGA
Forums: Slave SPI product recomendation
Forum: SPI in FPGA Multifunctional card discussion
White Paper: SPI and LV basics (check section 7)
Hope the information provided is helpful.
WenR

Windows 8.1 and RT, XT912_Verizon Droid Razr, Texas Instruments TI_Connectivity_Module show up in my network

Checkout the thread on Microsoft Community forum.
On Windows 8.1 RT and 8.1 on a laptop, the XT912_Verizon Droid Razr keeps showing up under Phone in my network and the Texas Instruments TI_Connectivity_Module also keep showing up. Also, sometimes a Samsung Galaxy shows up, all with various,
but consistent mac addresses in the Win 8.1 (RT) File explorer. These devices are NOT showing up as available wireless networks that I can connect to. This us under Network on File Explorer. I have added mac address filtering to my router,
changed my wifi security key, which is a strong 20 random characters, and changed the user name and password for my router. These devices do not show up as being wirelessly connected to the router and do not show up as dhcp clients on my router,
from the router admin interface. This tells me that, if these devices are connecting to my network, they are not doing it wirelessly, since they are not in the mac address list and not listed as wireless connections in the router admin interface.
If I show properties of, particularly the XT912, it "disappears" from the network window on the Win 8.1 (RT) explorer. The router is a motorola sbg6580. I connected through a cable to my router, turned off all other devices, disabled
wireless on both my router and my laptop, disabled WPS, listed only allowed MAC addresses in the MAC address filtering table and changed my network password, router user name and password to random character/number strings. I haven't seen the devices
since.
So far, three other users have reported on this thread as having the same problem. The other users who have posted on the Microsoft Community forum thread continue to have the problem. The strange thing is the same device keeps showing
up, XT912_Verizon, for all users.

Hi,
For the issue, please select "Turn off network discovery" to check the result.
Meanwhile, I suggest to perform Windows Defender to run a full-system scan.
Regards,
Kelvin hsu
TechNet Community Support

NI-8452 SPI communication with texas instruments ADS1278

Similar Messages

Maybe you are looking for