Trigger Error/Hp 4284A

[David W Green]

We have just set up an HP 4284 LCR Bridge and are running LabVIEW V5. just to get going and give an idea of how the 4284 works with labView we ran the 'Getting Started vi' that is packaged with LabVIEW for use with the 4284. the 4284 is generating a 'Trigger Ignored' (Error G(/H)PIB 211). the solution given is to widen the time between triggers. Using the 'Highlight Execution' function, the error occurs around the TRGSet / TrigSend blocks of the vi. there is a delay value set on the TRGset block, this being 0.1, we have tried increasing this delay (maximum allowable 6(sec)) but this has no effect.

HAs anyone experianced this problem or does anyone have any suggestions to overcome the problem. as no measurements can be taken with out overcomming
this problem.

Thank you very much for your help

David Green

[Mike_S.]

I ran that example on V6i and had no errors. I then connected the LCR bridge to a system still using V5.0.1f1 and installed the older driver version for this instrument. I received an error in the Initialize.vi - this was due to an incorrect string connected to the Regular Expression of the Match Pattern function in the true case of the ID Query. When I changed the string from HP428 to 428 the error was resolved and the top level VI then ran OK.

The reason I mention this, is that there were differences between the two driver versions - I don't know which version you are using, but it's possible there is a syntax error causing your problem - I have seen this before with other instrument drivers - although the error that you've noted is not listed among the HPI
B errors in the manual, it is listed under the Device-Specific operation errors. I assume that the instrument operates OK in manual mode?

I've attached a .gif file showing the trigger VI's from the drivers that I have - maybe you can verify
that this is equivalent to the driver VIs that you are using. Hope this helps some - good luck.

[David W Green]

Thanks for your comments Mike,

I am gonna go and take a look and see if there are any differences. The situation was a bit desperate so I ventured to phone Tech Sup! (make what you will of the exclamation mark!). I think it was something to do with the age of the drivers. I got emailed the application examples from V6, downwardly converted to V5. Ran those and the trigger problem disappeared!?

Problem solved. But it does annoy me that I don’t truly know what the real problem was.

Tech. Support can be helpful!

Thanks for your time. I let you know for interests sake if there are any differences as soon as.

Thanks again

David W. Green