Watlow F4 and Modbus

[thehobbs]

I just want to make sure you guys are aware of the certified LabVIEW instrument driver on IDNet (ni.com/idnet) for the Watlow F4 Series:

https://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9722659CE034080020E74...

[Joe_Gerhardstein]

Thanks Jason.  I hadn't come across that driver yet.

I downloaded it, but am getting the same errors I do with the LV7 Modbus libraries (timeouts when trying to read registers).  There must be something wrong with this controller, as I have tried talking with several example programs now and none seem able to read from it.  Must be time to call Watlow/Russells.


Joe

Message Edited by Joe Gerhardstein on 08-18-2006 10:44 AM

[Brian_Beal]

Joe-

Sorry that I just thought of this now.  You could download Watlow's configuration software.  I think it is called Watview.  It is a free download, and this will certainly work if there are no hardware problems.

[sigaman]

Joe,

Did you get anywhere with your timeout issues communicating with the F4?  I am having the same problems and was wondering if you had any ideas.

Thanks,

-Steve

[Peter256]

Joe,

If you are still having problems with Watlow F4 communications, contact me at the phone number on my website.

Peter Kesselman
VP Product Marketing
TestEquity LLC
http://www.testequity.com

Message Edited by Peter256 on 12-01-2006 05:54 PM

[MGould]

You may want to check how long your timeout is set for when you are opening your comm port.  I know I've had issues becuase the F4 can take up to a second or two to respond.  I think I have mine set to a 5 second time out to be safe.  Yes this does make your app slow if you F4 isn't on but it is possible to play with the timeout until you hit a "sweet" spot.   Are you using 485 or 232?

[Joe_Gerhardstein]

Steve:

No, I'm still running open-loop (e.g., cannot read from the F4).  This has been working okay for us for the last few months.  The only problem is when the serial cable falls out of the F4's interface port.

[Joe_Gerhardstein]

RS232.  I've tried longer timeouts, but have not gotten it to work.

[sigaman]

I just wanted to let you guys know, I was having problems communicating with the F4, then I did a firmware update and all works well now.  The firmware update is on Watlow's website so you might want to try that if you are not on the current firmware.

Good Luck,

-Steve

[dandnguy]

Hi Joe,

I have just bought a Watlow F4 controller and it is not responding to the query as well.

I just want to read the current temperature (Register 100 - Input 1 Value).

I have also tried to read other simple register like current date, month, etc... but it is not returning anything.

Did you find out what is wrong? If so, can you tell me what was wrong?

Thanks

Dan