Agilent N330X Error -1074000000

[Max_PLCTech]

Hi,

we have an Eload Agilent N3300A connected to Labview 2011 trough GPIB.

this is a new setup, however we get the attached error when the system run Eload Sweep Test vi. this error occur when the mentioned vi try to execute the "N330X configure trigger" sub vi. 

When I run the "N330X configure trigger" individually, it doesn't return any error, but when it is called it does return the mentioned error. this two vi was originally downloaded from NI database.

[ben64]

---

@Max_PLCTech wrote:

Hi,

we have an Eload Agilent N3300A connected to Labview 2011 trough GPIB.

this is a new setup, however we get the attached error when the system run Eload Sweep Test vi. this error occur when the mentioned vi try to execute the "N330X configure trigger" sub vi. 

When I run the "N330X configure trigger" individually, it doesn't return any error, but when it is called it does return the mentioned error. this two vi was originally downloaded from NI database.

---

The error message specify query interrupted. Since there is no query in the configure trigger vi I would say that the error is either related to what's going on in your Verify Input Low vi (not attached) or because a new command is sent (config trigger) before the previous query was answered (wich also point to the code in the Verify Input Low vi)

edit: the error probably pops up in the config trigger vi because there is no error handling in the verify input low vi.

Ben64

[Max_PLCTech]

Thanks Ben, Yes In fact, when I deleted the  "Verify Input Low" temporary, the "configure trigger" doesn't return that error. It seems something is wrong inside the attached vi.

[ben64 · Accepted solution]

There is nothing obvious in your vi but I would put a wait time of 100 ms in your while loop, there is no reason to query the value as fast as possible. The byte count set to 11 bytes seems to be a bit low. Since there is probably a termination character you can set it to a much higher value (like 128). It is possible that the query returns more than 11 bytes, this would trig an error. I also question the use of the Abort.vi, I don't really see why it is used and I would remove it.

Ben64

[Max_PLCTech]

Ben, I think the problem is solved !( at least for this part of the program). 

I raised the bye count to 64 and the error is gone. I will add the wait time and may be error query too, but I have to investigate the purpose of this vi first because honestly I dont know why the guy before me had used it. I mean if this was just for temporary test? I'l get rid of it.

[andmboa7]

Hey Max_PLCTech!

You can mark this forum as resolved and give kudos to Ben 🙂