01-21-2008 02:38 PM
Possible reason(s):
This attribute or function is not supported in this session.
Ensure that you are not using an acquisition-only attribute or function in a generation session or a generation-only attribute or function in an acquisition session."
FYI, I used PFI2 and PFI3 for generation and acquisition and wired the two pins together following the instruction in the code. I also wired "DDC CLK OUT" and "STROBE" together in the connector.
Can anybody help me on this issue?
Thanks a lot!
Jing
01-21-2008 11:25 PM
Hi Jing,
You’ll notice in the Example Finder that in the Requirements field for this example that the 6541 is not supported. This error is occurring at the property node that enables hardware comparison. Please note that in the NI Digital Waveform Generator/Analyzer Help that the 6541 doesn’t support hardware comparison.
Please post back if you have any questions. Have a great day!01-22-2008 01:19 PM
Hi Ryan,
Thanks for the link of the thread.
Since I have a PXI-6541, is there anyway that I can compare input signal to the card with the signal in the existing HWS file?
Thanks a lot!
Jing
01-22-2008 01:49 PM - edited 01-22-2008 01:50 PM
Jing,
Yes, you can still compare your acquisition data to the data in your HWS file. The comparison will need to happen in software rather than on the hardware device (like the 655x products). There is a VI in the digital palette called "Digital Comparison.vi". It takes two digital waveforms, compares them, and returns any error information. I've included an example that uses this software compare VI.
You will need to write a VI that does a simple Data Acquistion using your NI-6541 device. There are plenty of examples in the example finder on how to do this. In addition to that, you will need to use NI-HWS file api to read the data from your HWS file. The file api VIs can be found in the HSDIO Palette in LabVIEW. Now that you have your acquisition data, and you have read the data from your HWS file, just pass those two waveforms into the digital compare VI.
-Jared
01-22-2008 03:32 PM
Hi Jared,
Thank you so much for the example code and the suggestions! I will start working on it now and let you know how it goes. ^_^
Thanks!
Jing
01-24-2008 05:22 PM
Hi Jared,
I am trying to do Internal Scan test. Attached please find a simplified VCD-file-converted HWS file. I should send SPI_CLKH into the ASIC. After a certain time, signal IRQ_real is supposed to come out from the ASIC.
I should acquire IRQ_real and compare it with IRQ in the attached HWS file. They should match each other.
Here are my questions:
1. How to set the acquisition trigger so that I can catch the starting point of IRQ_real as soon as they start coming out the ASIC? Which acquisition trigger should I use, considering there are many trigger types in the "HSDIO Configure Trigger" function.
2. I checked the "Acquisition and Generation" examples, both acquisition and generation process used the function "NIConfigure Sample Clock". Shall I use the same "On Board Clock" for both acquisition and generation process? How do I determine the "On Board Clock" frequency?
Thank you so much!
Jing
01-25-2008 01:02 PM
Hello,
Please view the Help document titled Trigger Summary in the NI Digital Waveform Generator/Analyzer. This document will help you select the proper trigger. I would recommend looking at the Start – Digital Edge Trigger. Please read about both start and reference triggers to determine which might better suit your application.
I am assuming that you need to generate and acquire, since you are first sending out the SPI_CLKH and then later acquire the IRQ_Real. The sample clock functions can be set to the same sample clock resource. However, if the signal you are generating and the signal you are acquiring are at the same time base, I would not suggest using the same sample clock. This is because you want to follow Nyquist Theorem. This states that the acquisition rate should at least be two times the incoming signal’s frequency. Most people actually do five or ten times to get a cleaner signal. Thus, you would want to set the sample clock for the generation to the rate at which you want to generate and then set another sample clock to five times the IRQ_Real frequency for the acquisition task.
01-25-2008 03:55 PM - edited 01-25-2008 03:57 PM
03-14-2008 07:58 PM
Hi Jared and Samantha,
Thanks a lot for your help. Sorry for replying so late. Was pulled to some other projects recently.
I tried the "pattern match" Jared suggested on the simplified version of vectors. The acquisition works pretty well. Thank you so much!
After I tried the real version of vectors, I encountered another problem. In the vectors of driving signals, there are some period of "Z" instead of "0" or "1". As a result, it may cause a short period of "X" in the output signal. As I am storing the acquired signal into a file and comparing it with the existing data, the following error message pops up:
+++++++++++
Error -1074118585 occurred at niHSDIO Write Named Waveform From File (HWS).vi:
Possible reason(s):
Driver Status: (Hex 0xBFFA4047) A digital state value in the waveform you attempted to write is invalid for this device or for this configuration.
Supported Values: 0, 1
Status Code: -219406
+++++++++++
Could you give me any suggestions?
Thank you so much!
Jing
03-18-2008 03:03 PM
Hello,
The error you are receiving is related to the HWS file you are attempting to generate having Z states. The 6541 cannot generate this state. To avoid this error please change any Z states in the drive data to a 0 or a 1. Do you have the NI Digital Waveform Editor? You can change the Z states by using the Digital Waveform Editor. In addition, I noticed that you started with a VCD file. The Digital Waveform Editor has an VCD Import Wizard, which allows to you configure and change the Z state upon import. The topic titled VCD Import Wizard within the NI Digital Waveform Editor Help outlines this in further detail.
In summary, the error is occurring at the niHSDIO Write Named Waveform.vi due to the Z states in the HWS file. There are not any X states acquired since it seems the error occurs prior to acquisition.