HSDIO-6541 Hardware Compare Error-1074118626

[jcao]

Hi,
 
I ran example file "Hardware Compare - Error Locations. vi"  and got the following error message:
 
"Error -1074118626 occurred at Property Node (arg 1) in Hardware Compare - Error Locations.vi

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  

[ryan_d]

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 <a href="http://digital.ni.com/manuals.nsf/websearch/28328731D00E483786257361005589B4" target="_blank">NI
Digital Waveform Generator/Analyzer Help</a> that the 6541 doesn?t support
hardware comparison.

Please post back if you have any questions. Have a great day!

[JaredW]

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&nbsp;digital compare VI.
-JaredMessage Edited by JaredW on 01-22-2008 01:50 PM


DigitalSoftwareCompare.vi:
http://forums.ni.com/attachments/ni/70/8084/1/DigitalSoftwareCompare.vi

[jcao]

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

[jcao]

Hi Jared,
I am trying to do Internal Scan test. Attached please find a simplified VCD-file-converted HWS file. I&nbsp;should send SPI_CLKH into the ASIC. After a certain time,&nbsp;signal IRQ_real&nbsp;is supposed to come out from the ASIC.
I should acquire&nbsp;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&nbsp;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
&nbsp;
&nbsp;


Que.zip:
http://forums.ni.com/attachments/ni/70/8099/1/Que.zip

[samantham]

Hello,

Please view the Help document titled Trigger Summary in the NI Digital Waveform Generator/Analyzer.&nbsp; This document will help you select the proper trigger.&nbsp; I would recommend looking at the Start ? Digital Edge Trigger.&nbsp; 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.&nbsp; The sample clock functions can be set to the same sample clock resource.&nbsp; 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.&nbsp; This is because you want to follow Nyquist Theorem.&nbsp; This states that the acquisition rate should at least be two times the incoming signal?s frequency.&nbsp; Most people actually do five or ten times to get a cleaner signal.&nbsp; 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.
&nbsp;

[JaredW]

For your application, the Nyquist theorem doesn't apply.&nbsp; In most cases where you are generating and acquiring response digital data, you will almost always want to use the same clock for both generation and acquisition.
&nbsp;
I would recommend reading up on Round Trip Delay elimination in the HSDIO help to get a good understanding of the system you are trying to build. This doc can be found in the NI Digital Waveform Generator/Analyzer help under Programming-&gt;Features-&gt;Eliminating&nbsp;Round Trip Delay. This will&nbsp;talk about a source synchronous method of&nbsp;generating and acquiring data.&nbsp;This would requir you&nbsp;routing the clock through the ASCI and back into the NI-6541, as well as a synchronous trigger.
&nbsp;
If you cannot change up your&nbsp;ASIC to&nbsp;do the above, I would then recommend&nbsp;using&nbsp;a pattern match start trigger for acquiring your response data.&nbsp;Here is the programming flow: 1) Configure the generation session using an onboard clock&nbsp;&nbsp; 2) Configure the acquisitin session using an onboard clock and a pattern match trigger that matches when IRQ_Real is&nbsp;HIGH&nbsp; 3) Start&nbsp;the Acquisition session&nbsp; 4) Start the Generation session&nbsp; 5) Wait until Done&nbsp; 6) Read&nbsp;acquistion data from device&nbsp; 7) close both sessions.
&nbsp;
&nbsp;Looking at your HWS waveform, I know that the IRQ_Real signal will be low until the ASIC starts generating data to it, which is why I chose to use the pattern match on that signal when it is HIGH. Now to do the software compare, you will need to get the IRQ_Real data out of your HWS file, and remove all of the leading zeros such that the first value is a HIGH. Now your expected response data will be aligned to the pattern matched data. Lastly send both the acquired IRQ_Real data and the modified HWS IRQ_Real data to the software compare VI discussed in the previous post.
&nbsp;
One last thing that may or may not be an issue (depending on how fast your clock is) is data delay.&nbsp;If the acquired data is totally incorrect, there is a chance it is because the IRQ_real data coming from the ASIC is transitioning at the same time as the onboard clock, thus the 6541 is sampling when the IRQ data is in an invalid state. To get around this, you can use the Data Delay feature to delay when the acquired data is sampled within a clock period.&nbsp;You will have to just coerce this value manually until the data starts looking correct. I would start with 50% delay, then 25% and 75%, etc, until the data looks good. There is an example for using data delay, In the examle finder, go to Modular Instruments-&gt;NI-HSDIO-&gt;Dynamic Acquisition-&gt;Dynamic Acquisition With Data Delay.vi
&nbsp;
good luck,
Jared
&nbsp;Message Edited by JaredW on 01-25-2008 03:57 PM

[jcao]

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&nbsp;encountered another problem.&nbsp;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:&nbsp; (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

[ryanm]

Hi Jcao,
&nbsp;
Samantha is correct that the 6541 does not support tristate on the fly.&nbsp; Do you need&nbsp;this ability (i.e. are your data lines bidirectional)?
&nbsp;
Thanks,
Ryan

[jcao]

Hi Samantha and Ryan,
Thanks a lot for your reply. Yes, both of you are right. The error comes from the generation section because there are Z's in the HWS file. I modified the HWS file so the error disappeared. Now I am investigating whether the Z's come from the VCD file which the HWS file was generated from, or come from the WGL.pat file which the VCD was generated from.
Thanks again!
Jing

[jcao]

Hi Jason,
We used ModelSIM.
Thanks,
Jing