Can I use Linx arduino to do analog read and SPI write at the same time?

[andywong1026]

Simultaneously, for example to control a  SPI DAC chip output and read back the  output by the analog input of an Arduino.

[jorgemondadori]

Sure can do, but not simultaneously, but sequentially at very close data rate. That for Arduino can be called simultaneously

[andywong1026]

But, I am getting error with this vi. Couldn't figure out. I am new to Labview.

[jorgemondadori]

What errors are you getting? can you use only SPI? can you use only analog read?
how is your circuit wired?

try to avoid those red coercion dots on analog read, by using expected data type.

[andywong1026]

Apparently, I got rid of the error. By try and error.. I don't know if this is the correct way of doing. Please advise.

[GovBob]

Note that I don't have LINX or a newer version of LabVIEW.

But let me quote a LINX Makerhub FAQ 

"When you call the LINX Initialize VI it establishes a connection to the LINX device and the Init VI passes out the LINX Ref wire. You can think of this wire as the connection to the device and it contains all of the info needed to 'talk to' the device. You really shouldn't branch / split this wire because you only have one connection to the device. If you split the wire you don't get a new connection, you juts get the same connection. If you split the LINX Ref wire, the VIs downstream might both try to talk to the device at the same time. In this case a command might be sent to the LINX device before the previous one is complete, and the responses to the commands might get swapped resulting in incorrect data being returned. Since only one command can be sent at a time splitting the LINX Ref wire doesn't result in any performance increase and adds risk for incorrect data. When you call the close VI the connection is closed. This includes any copies of the connection in branched / split wires. Once the connection is closed you can no longer talk to the device unless you establish a new connection with the LINX Init vi."

So just keep those vi's inline.