Help with GPIB-RS232

[mudson]

Have you attempted to query the device through the test panels available in Measurement & Automation Explorer?  This is the best place to start the trouble shooting process.  

If you are interested, drivers are available for your device:

http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:id/q/F4/

Once we eliminate hardware communication issues, we can start looking at your code.

Best regards.

[kzaneh]

Mathew,

Thanks for the reply, Yes I started with MAX and had a problem reading the query if the GPIB converter is in 'Normal' operation mode...in 'Config' mode MAX talks to it with no problems. I tried to use the F4 drivers but I need them for LabVIEW and the link you post has them in LabWindows/CVI. I tried to use the Instrument driver import wizard to change the LabWindows F4 drivers to LabVIEW but I got an error because the import wizard apparrently needs .fp files.....

I tried to use the F4D and F4S drivers but receive errors that other people are also receiving and posting herein...

However, I did manage to make enough changes to the F4S drivers and GPIB-RS232 Converter, I'm in D Mode now, to at least communicate with the Watlow F4 controller, however I still get read warnings, see attachment, and I always timeout on any read after a write. Should I be adding cr lf after eache write?

Thank again for any and all help.

Kert

[mudson]

Kert,

I'm sorry we're still working on this!  Hopefully we'll reach a solution soon.
I don't mean to be pedantic, but just to be absolutely clear:
You receive a time-out when the device is queried with

*IDN?\n 

I'm looking at some of the literature published by Watcom.  I see two devices listed as F4: a Ramping Temperature Controller, and a Temperature Process Controller.  Which one are you using?

Also, I noticed that MODBUS is referenced in the error message, are you using MODBUS?

[kzaneh]

Mathew,

I get an error when the device is queried with anything including *IDN?, *IDN?\n, ...etc IF the GPIB-RS232 Converter is in 'NORMAL' configuration and it is queried from NI's MAX utility. See attachments for responses from MAX while attempting communication.

If I query the device with any request from the F4S Watlow NI LabVIEW drivers downloaded from the website with 1 modification to remove ARG[2] errors, I get a warning...see the attachment from the previous post.

Just to be absolutely clear...'pedantic' to borrow your term, I am NOT using anything from Watcom. My lab setup pursuant to this test and hardware is as follows.

My PC is running Windows 7 64bit Ultimate with LabVIEW 2010 SP1 32bit. I am connected to the NI GPIB-RS232 using an NI GPIB-USB-HS cable. The DB9 output from the GPIB-RS232 is connected to a Test Equity 105A (Half-Cube) Temperature Chamber with a Watlow F4 Controller via a 9pin 'crossover' cable...pins 2 and 3 are crossed and pin 5 is connected straight thru.

I ohmed out the cable with a voltmeter and it checks out fine. I ran the Test Chamber with no problems by replacing the NI GPIB-RS232 with an ICS 4899A-GPIB-MODBUS Interface box and Cable and using different LabVIEW VI's. My point here is that problem is not in the test chamber, controller, pc or GPIB cable...

In all of the literature and manuals that I have for the Watlow F4 controller I do NOT see a differentiation from Ramp or Process type, however since I can set profiles for this controller I can only assume it is of the ramp type.

The protocol I am attempting to use is GPIB to MODBUS RTU.

Now having said all of that I believe the warning/error is related to the way VISA ends the line (EOS, EOI etc) and have not had the time to try all of the variations. The original error I get while trying to use the NI LabVIEW F4S drivers that I download from the NI website are related to an attempt in the software to set the ASRL thru a property node.

I am trying to minimize unknowns...and share that effort in the best possible way so please DO be PEDANTIC and thanks for your time!

Kert

[mudson]

Kert,

I apologize that it has been a while since my least response.
After some digging, it turns out that the warning you received is not something about which to be concerned.  It is a status message.  Error messages that are causes for concern have negative values.

http://digital.ni.com/public.nsf/allkb/C96C84C922DC3F978625632500482F78

It still concerns me that you are not able to query the device without a time-out, so I will keep researching on this end.