From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
08-26-2009 08:44 PM
Invalid separator - The parser was expecting a separator and encountered an
illegal character. For example, the semicolon was omitted after a program
message unit.
followed by an error saying that the quest was unterminated. (Which i assume is caused by the first error)
It's highly confusing because all three commands were taken directly from the programming manual. Any suggestions on why all of my commands (and I do mean all) with colons in them are giving me these two errors?
08-26-2009 10:05 PM
08-26-2009 11:41 PM
08-27-2009 10:30 AM
What is wrong with the link I gave you. A link is meant to be clicked on so that is all that you have to do.
Your statement that you cannot use the GPIB functions because you have a USB-GPIB is just plain silly. Of course you can use them but it's even sillier to be using the low level GPIB functions anyway. You should be using VISA functions for everything and of course that is what the driver uses.
If any of your past projects involved instrument communication and you did not even try to find an existing driver, you spend a considerable amount of time recreating the wheel.
08-27-2009 11:05 AM - edited 08-27-2009 11:09 AM
Sorry, it was very late when I made that reply. I followed that link this morning and all of the drivers there crash on launch when they try to initialize visa. I get an error that says: AGPNA Initialize - Serial Port Not Supported. Which is bizarre because I'm using USB to GPIB. So I'm really not sure what I'm doing wrong. It seems like most drivers I've tried to use have had similar problems and looking at the block diagram didn't help much either 😕 for some reason the commands it was sending to the PNA have all these %.; things in it which I'm not sure what do. I've never had to add a bunch of %.; strings to my code in the past.
Also, I've found a Prologix GPIB Sample vi that lets me send strings over VISA to my device. Once again things like *IDN? and *STB? are working but things like CALC:MARK ON are not working and I'm getting that error again from the first post.
08-27-2009 11:15 AM
I suspect that by 'crash' you are simply getting an error. What do you have the VISA Resource Name control set to? Did you click on the arrow and select your instrument from the list.
The % is not being sent. I think you are looking at the string format commands. These are basic LabVIEW functions on the string palette (i.e. Format Into String) and if you've never used these either, you might want to look at the LabVIEW tutorials and look at the LabVIEW help.
What does Prologix have to do with this? Is that what you are calling the USB-GPIB converter?
08-27-2009 11:19 AM
Yeah, I'm getting that serial error. I've used the string formatting stuff before. I've just never seen a %.; command before. I believe prologix is the manufacturer of the converter. And yeah I've been setting it to the proper com channel (Com 3 in this case) I just still don't understand why it'll respond properly to *IDN? and *STB? but not CALC:MARK:STAT? all three of which are from the programming manual. Are these different types of commands or something? 😕
08-27-2009 11:34 AM
08-27-2009 11:41 AM
08-27-2009 02:03 PM
This USB-GPIB device appears as a COM port? Does the Prologix USB-GPIB show up in Measurement and Automation Explorer? If so, does it show as a GPIB card or a COM port?