I wanted to follow-up to stuff the archive for anyone searching in the future,
including myself when I forget how to do this again in 2 weeks. We
successfully have a trial Cutler Hammer drive communicating well with an FBM
232. So far we are able to control anything that can be done with hard I/O and
get any information available from the keypad.
Here's the set-up that worked:
Drive: Cutler Hammer SVX 9000 series
Drive option card: Modbus / TCP IP OPTCI-V, installs in expander slot D
Alternative: Eaton DG-1 series is supposed work exactly the same way but has
the Modbus comms card integrated as standard
Configuration: In the keypad change remote control option to "fieldbus" and
remote reference to "fieldbus".
FBM 232 connected to the comms card through a generic unmanaged Ethernet swtich
(was a Netgear JGS524, will be a phoenix contact)
Also connected with a crossover cable while troubleshooting and that worked as
well, the manual says explicitly it wouldn't work, not sure why.
ECB 200:
DEV_ID: GNBA08
HWTYPE: 232
SWTYPE: 232
PORTEX: 1
FILEID: GNAA08.XML
FSENAB: 0 (default)
FSDLAY: 1000 (default)
WDTMR: 10 (default)
SFILEID: MODBUS.ZIPH
SYSCFG: 1000 (default)
SYSOPT: 0 (default)
ECB 201:
NAME: VFD100
HWTYPE: 232
SWTYPE: 232
PARENT: GNBA08
DVNAME: 192.168.100.100
DVOPTS: MODBUS
PORTNO: 1
ERROPT : 0xFFFE (default)
All other options blank (default)
GNAA08.XML:
IP address: 192.168.100.99
Subnet mask: 255.255.255.0
Default Gateway: 192.168.100.99 (I have no idea what to put here or if it even
matters but it's working)
DCI block for controlling drive:
This is where I had the most troubles, I'm just barely understanding Modbus
life after all of this but it seems to be working well, so take all this with a
grain of salt. I ran into a lot of "duplicate address" errors when I put in
multiple DCI blocks. I learned that I need to add the :C16, :C8, etc in the
PKCOGP (where 16 represents the length of bits? in the address space).
According to the drive comms manual at address 00001 there are 16 consecutive
bits. When I left it without the :C16 it defaults to 32 bits and it didn't
communicate.
Name: CONTROL
Type: PAKOUT
IOM_ID: VFD100
PKCOGP: 00001:C16
PKCOPT: 1
All other values default
Now toggling the following bits does the following (full memory map in the
cutler hamer manual)
IN_1 starts/stops
IN_2 fwd/rev
IN_3 fault reset
IN_4-IN_16 FBDIN1-10, I don't' use these or know what they do yet
Name: FEEDBACK
Type: PAKIN
IOM_ID: VFD100
PKINGP: 10001:C8
PKIOPT: 1
PAKCIN: 0
UPDPER: 10000
SIMOPT: 0
1 is ready confirm
2 is run confirm, 3-8 are other nice things to see
Then I added IIN blocks for any other value we want to see. One example is
torque feedback:
TYPE: IIN
IOM_ID: VFD100
PNT_NO: 410301
All other parameters default
All the other nice to know things are in addresses 410301 - 410325, so I'm
thinking I have to set up an IIN block for each one I care to watch.
Hopefully someday this helps someone else out there!
Chad Ziesemer
Control Systems Engineer
Cell: 920.427.9147
Desk: 920.886.2376
Galloway Company
601 South Commercial Street
PO Box 609, Neenah, WI 54957-0609
From: Chad Ziesemer
Sent: Thursday, November 05, 2015 5:20 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Anyone using Cutler Hammer SVX drives with Foxboro?
Is anyone else out there using Cutler Hammer (Eaton) SVX series drives at their
facility with Foxboro? I'm setting up a trial to communicate all of the drive
info into and out of Foxboro via an FBM 232. I'd love to hear in general what
your control set-up looks like and what your experience was: smooth sailing or
rough sledding.
Also I'll take this opportunity to see, is there anyone else on this list using
Foxboro reasonably close to Neenah, Wisconsin? We've got a small group of
engineers here that would love to network with someone local and see what we
can learn from each other.
Chad Ziesemer
Control Systems Engineer
Cell: 920.427.9147
Desk: 920.886.2376
Galloway Company
601 South Commercial Street
PO Box 609, Neenah, WI 54957-0609
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
