niScope Configure Trigger Edge sending error to niScope Initiate Acquisition

[Wolley]

I'm getting an error from my Trigger off of my scope that keeps failing the program. The error code is -1074135022,

it says

niScope Initiate Acquisition.vi:1<ERR>Attribute or property not supported.

Device: NI_Scope
Property: Trigger Holdoff

Status Code: -200197

I'm using an NI-5133, running Labview 2011 and scope 3.9.4

Thank you for you help!

Wolley

[James-K]

Wolley,

Try eliminating the 5E-7 from the trigger holdoff input on the Configure Trigger Edge VI.

[Wolley]

Upon doing so, I now have an error that I think is due to it trying to trigger while collection is still taking place. I may very well be wrong in this, though. It comes out of the niScope MultiRead block, and says

niScope Multi Read WDT.vi:1<ERR>A previous acquisition is still in progress. If you are attempting to change an attribute, note you can only change fetch attributes while an acquisition is still in progress.

Status Code: -1074118647

Attached is the current state of the VI. I don't think the minor changes I've added in should be causing the error.

Thanks,

Wolley

[James-K]

Wholley,

I would recommend taking a look at the example niScope EX Configured Acquisition.vi (Example Finder->Hardware Input and Output->Modular Instruments->NI-SCOPE->Demos) to have a starting point for something that works with a trigger.  Also, I would recommend modifiying your code such that you are not creating/closing the hardware reference with each iteration of the loop.

[Wolley]

I've made some moderately substantial revision, and have attached my current VI. Triggering seems fine now, but I now can't get any measurements because of an error code -1074126847.

It says

niScope Fetch Array Measurement.vi:1<ERR>Specified channel is not enabled.

Cannot fetch waveform from disabled channel.

I've verified that my scope is working fine through the soft front panel, and is able to measure off of channel 0 as I'm trying to do. I don't know why it would refer to that channel as being disabled. Any thoughts?

Thanks,

Wolley

[James-K]

Wolley,

Try adding a niScope Configure Chan Characteristics VI after the initialize VI.