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-13-2005 06:24 AM
08-15-2005 05:04 PM
tbihn,
Wow, that's a lot of questions!
Send EOI at End of Write in MAX should accomplish the same thing as Assert EOI on Write in CW. EOI is indeed a control line on the GPIB bus, it is asserted when a write is completed to signal the end of the command.
Terminate Read on EOS in MAX should be the same as EOS Ends Read on CW. This is generally not used since EOI is the most common form of termination, but EOS enables you to end a read when a certain character is read, such as a carriage return or line feed. This is usually not necessary though.
Set EOI with EOS on Write gives you the benefit of sending two different methods of termination. You could think of this as "covering all bases". It is disabled by default because EOI is the default termination method, so if you are not paying attention to your EOS setting, you could be sending out accidental EOI signals if one of your transmitted characters mistakenly matches the EOS character that you aren't using.
I am not 100% on what the EOS byte "0" setting does, but I if you actually wanted to set your EOS character to line feed or carriage return, you would need to change it to the appropriate number. If you click in the EOS byte field, then click on the ? button in the top right corner of the Properties window, you can get more details about this setting.
REN is the Remote Enable line, which tells the instrument that GPIB is going to send commands to it. It should be enabled before you begin your GPIB communication to the instrument to let it know it will be controlled remotely (by the PCI-GPIB card).
Setting the timeout to a lower number will let your commands time out faster, which reduces the time that a bad command takes before it errors out. However, this could also be a bad thing if you have commands that take longer than the timeout to execute, such as large data transfers. If this is the case, a short timeout will cut the command off before it finishes, resulting in lost data and an unnecessary error.
The settings you set in CWGPIB should override the default ones from MAX in your program.
Hope this helps, have a good day!