03-03-2016 10:20 AM
Hi Austin,
From this sentence that we read from the datasheet of NI PCIe 6353 "X Series DAQ hardware provides analog inputs, analog outputs, hardware-timed digital I/O, and four counter/timers on a single device, making it a cost-effective option for basic device under test characterization and test automation"
We understand we need to use "Using an Internal Sample Clock" example from "Serial Protocol Communication Reference Design for Digital Waveform Devices" article.
Because we are newbie to Labview we may be asking very obviously known things.
But still we can not decide which one to use "Init IntClk Device.vi" or "SDW 16-bit Register Swap.vi" or using them together.
Best regards,
Uğur ÖZENÇ
03-04-2016 03:38 AM
Hi Austin,
The missing parts of the picture is are occuring in our side. As told in the article we started from using "Init IntClk Device.vi". When we tried running, it returned an error called -200452. When we researched about the error we found this (http://digital.ni.com/public.nsf/allkb/05A563FE3AA7B3C286256FF90077C303) it says 'The different properties of DAQmx property nodes are device specific. This means that certain properties are only supported by certain DAQ devices.'
So we understand PCIe 6353 does not have DataActiveEvent.OutputTerminal property, so what can we use instead this?
Best regards,
Uğur ÖZENÇ
03-04-2016 11:52 AM
Hey abilgi,
I was looking into your issue a bit, and I at least have this to offer. It looks like you definitely don't want to use the Internal Sample Clock method. My justification comes from this line in the article: 'NI DAQ devices do not generally have an onboard oscillator used to run hardware-timed DIO tasks. However, some devices, like the M-series (62xx), are capable of correlating their DI and DO tasks to an externally generated clock signal." Your PCIe card is also capable of correlating digital input and output tasks to an external clock signal, so that methodology should hopefully work for you.
I think that also explains the property issue you were running into: "M-series devices do not generate a Data Active event. Fortunately, the DI and DO tasks will be sampling with a clock source that is not free-running -- the CO task -- so they will not start until the clock does. This fact can be used to ensure a simultaneous start without the need for a trigger signal." So, you won't need to use the Data Active property as a trigger for the channels.
I also saw you've already made a post in the specific discussion forum for this API; that's a great idea. That forum should get you more specialized assistance with your configuration. Hope this helps!
Cason
03-07-2016 08:25 AM
Dear Cason,
I may be misunderstood, I wanted to use Internal Sample Clock method but it produced me that error. I mean if I have a chance to use Internal Sample Clock I can use it, but couldn't manage it. If you can lead me I can apply it. Also If it is easier I can use externally generated clock signal but I don't want to use second hardware if it is possible do with my daq card.
I hope they may help me also.
Thanks for your helps,
Best regards,
03-08-2016 06:15 PM - edited 03-08-2016 06:18 PM
Hi Albigi,
After digging deeper into the Serial Waveform Protocol, it looks like the error you are seeing is because that Data Active Event is only available on our HSDIO targets. I'm sorry if I was unclear earlier on whether this property was usable on your 6353. You should, however be able to use an external clock to do it using Correlated DIO. I would also ask on the other board if anyone has had experience with this DAQ card and the SPI waveform library.
Hope this helps!
03-09-2016 02:57 AM
Dear Austin,
As you mentioned that I am trying to use external clock to do this using Correlated DIO. But I am unsure that If I need a second device or I can do it with just 6353. From this explanation "Using Correlated DIO
NI DAQ devices do not generally have an onboard oscillator used to run hardware-timed DIO tasks. However, some devices, like the M-series (62xx), are capable of correlating their DI and DO tasks to an externally generated clock signal. A counter/timer on the device can be used to generate an oversample clock, which can then be internally routed to the DI and DO tasks."(Serial Protocol Communication Reference Design for Digital Waveform Devices) I undestand that I can do it using just one M series 62xx. But this doesn't explain if I can do it with X series 6353.
If it does what should my 'Counter task', 'Digital output task', 'Digital Input task' look like in Run CorrDIO Device.vi as seen in the attachment?
Best regards,
Uğur ÖZENÇ
03-09-2016 04:59 PM - edited 03-09-2016 04:59 PM
Hi Albigi,
As far as correlated DIO, you should be able to do that with just the 6353. The 6353 is an X-series card, which is newer than the M-series card, encompasses most, if not all, of the properties and functionality of the M-series cards.
Would you mind posting your VI? The screenshot of the front panel looks like it should, but I really need to see the block diagram in order to diagnose the issues you are seeing.
Also, did posting on the other Discussion yield any insight into this?
03-10-2016 09:17 AM
Hi Austin,
I am connecting the outputs of the "Init CorrDIO Device.vi" to "Run CorrDIO Device.vi" and produce "CorrDIO Device.vi". Then I get error -201435. All of them are in the attached zip file.
I could't have any reply from other thread yet.
Thank you very much for your helps.
Best regards,
Uğur ÖZENÇ
03-11-2016 03:27 PM
Hi abilgi,
Error -201435 typically implies that no samples were provided to the DAQmx Write. Are you writing anything to the digital waveform control that is leading into the DAQmx Write (Digital Waveform 1Chan Nsamp) that came from your Run CorrDIO Device.vi?
03-21-2016 09:35 AM
Dear Yiran,
I am a newbie to labview so I may ask very easy questions. I am sorry about that. I have formed a waveform as can be seen in the Corr DIO waveform.jpg in order to send data. When I tried to form the waveforms as in Timing diagram.jpg it says
<B>Number of Lines in Channel: </B>3
<B>Number of Lines in Data: </B>4
So I formed 3 channels. And it produced no errors. But I don't know how can I form the channels as in Timing diagram.jpg?
Datasheet can be found here (https://store.invensense.com/datasheets/invensense/MPU9250REV1.0.pdf)
I appreciate your helps.
Best regards,
Uğur ÖZENÇ