08-22-2019 12:00 AM
Dear Experts,
I wanted to test the available hardware to its limits. I have a PXIe 1065 chassis with Industrial Desktop computer with LV RT connected over MXI. The PXIe chassis has 5 pxi 6259 cards.
I wanted to test the system and made a small program which digitizes 32X5 channels at 31KSPS which is near the maximum acquisition rate supported by 6259 card.
When I am executing the program the cores in Controller are jumping to 99-100% load which I believe is not a good sign. Is there is any solution to achieve this by making some optimizations in the code.
I am attaching my snippet for your reference and comments. I have tried with all the data types. U16, double , waveform and even raw type.
later I aim to add consumer loop for data logging.
Pls give your suggestions.
08-22-2019 12:23 AM
mcduff
08-22-2019 03:47 AM
Thanks for your reply.
When I am trying to combine them to a single tasks , I am getting error stating that one or more device do not support multidevice tasks.
I will remove the graphs and include DAQmx logging and update here.
08-22-2019 06:59 AM
Hi,
While using the DAQmx based logging , I am getting strange results. The data is getting plotted properly but in while the data is not logged correctly.
There is loss in the signal shape. Pls see the attached image.. I have executed the inbuilt example for DAQmx based logging.
08-22-2019 08:05 AM
You need to post some code, otherwise hard to help.
mcduff
08-22-2019 10:21 AM
@falcon98 wrote:
Thanks for your reply.
When I am trying to combine them to a single tasks , I am getting error stating that one or more device do not support multidevice tasks.
I will remove the graphs and include DAQmx logging and update here.
If the devices are identical, in a PXI chassis, typically they can be combined into a single task. However, if you are using DAQmx with RealTime LabVIEW, that option my not exist as DAQmx is new for LabVIEW RT. I never used it with RT LabVIEW, but with Windows I know it works.
mcduff
08-23-2019 04:22 PM
U
@mcduff wrote:
if you are using DAQmx with RealTime LabVIEW, that option my not exist as DAQmx is new for LabVIEW RT. I never used it with RT LabVIEW, but with Windows I know it works.
Um, I forget when DAQmx was released. In LabVIEW 7.0, we used "Traditional DAQ" on LabVIEW RT running on a PXI (not PXI-e, yet) system. When I started updating it (LabVIEW 8-something), I used DAQmx (thank goodness I could dump Legacy DAQ!) on my PXI-based LabVIEW RT system -- I think the final update of this particular Project was in LabVIEW 2014. Not only does DAQmx work well in Windows, it works even better in LabVIEW RT (well, at least as well ...).
Bob Schor
08-23-2019 04:25 PM
@Bob_Schor wrote:
U
@mcduff wrote:
if you are using DAQmx with RealTime LabVIEW, that option my not exist as DAQmx is new for LabVIEW RT. I never used it with RT LabVIEW, but with Windows I know it works.Um, I forget when DAQmx was released. In LabVIEW 7.0, we used "Traditional DAQ" on LabVIEW RT running on a PXI (not PXI-e, yet) system. When I started updating it (LabVIEW 8-something), I used DAQmx (thank goodness I could dump Legacy DAQ!) on my PXI-based LabVIEW RT system -- I think the final update of this particular Project was in LabVIEW 2014. Not only does DAQmx work well in Windows, it works even better in LabVIEW RT (well, at least as well ...).
Bob Schor
I guess I was thinking of DAQmx on cRIO, which is new.
Sorry.
mcduff
08-26-2019 01:20 AM
Is there any efficient way to achieve the maximum acquisition and logging with the PXIe. I am trying but each time the processor cores jump to 100% load.
08-26-2019 09:37 AM
@falcon98 wrote:
Is there any efficient way to achieve the maximum acquisition and logging with the PXIe. I am trying but each time the processor cores jump to 100% load.
Post some code otherwise hard to help.
mcduff