Re: [foxboro] Connecting Limitorque & Integrator 30
- From: Roger Smith <RSmith@xxxxxxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 29 Nov 2001 11:10:57 -0500
I'm resending this because my first one came back to me garbled. I hope
this is better.
Douglas,
I'm trying to understand if there is a bit mapping here. For the values you
listed for turning on the various relays, if you forget the last two zero's
in the values, 09 is 00001001 in binary. Likewise, 0A is 00001010. Now you
might conclude, that the rightmost bit controls relay 1 and the second
rightmost bit controls relay 2. However, when you look at relay 3, you said
you need to send 0B, which is 00001011. So bit mapping doesn't seem to make
any sense.
Another possibility is that the Limitorque looks at this register as a
command, with the forth rightmost bit being the desired relay state (on=1,
off=0) and the other three rightmost bits representing the relay number
(relay 1=001, relay 2=010, relay 3=011, etc.). This seems to agree with the
information you gave below. While a much more difficult situation, this can
be dealt with. Some how you have to queue up the requests to set or reset
the various relays. Here is some possible CALC block code to do it by
continuously cycling through the relays and outputting the command. I think
it will work but have not tested it. BI01-BI06 are the desired states for
relays 1-6, i.e. BI01 might be GDEV.COUT_1 and BI02 GDEV.COUT_2 or
~GDEV.COUT_1. M01-M06 are set to the command value for turning off relays
1-6 (i.e. M01=0001, M02=0010, M03=0011, etc). M07-M12 are set to the
command value for turning on the relays (i.e. M07=1001, M08=1010, etc).
(M01 might actually need to be 000100000000, 0100 hex, and M07 100100000000,
0900 hex) RO02 will be tied to an AOUT going to the Limitorque. Set the
block period long enough so that the command for each relay will be sent to
the Limitorque long enough or add some timing logic to the CALC block.
1 INC RO01 stores the value of the relay we are dealing with
2 IN RO01
3 IN 6
4 SUB
5 BIP 8 if greater than 6, set to 1
6 IN 1
7 OUT RO01
8 IN RO01 get the current relay
9 STM M24 holds the value of the relay we are dealing with now
10 INB M24 gets the Boolean input pointed to by M24, i.e. for the
appropriate relay
11 IN 6
12 MUL either 6 or zero depending on Boolean value
13 ADD relay number plus either 6 or zero
14 STM M23
15 LACI M23 gets the memory register pointed to by M23
16 OUT RO02
Roger B. Smith
Process Control Engineering
Waste Water Services
City of Atlanta
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On
Behalf Of DOUGLAS NAVARRO
Sent: Wednesday, November 28, 2001 2:33 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Connecting Limitorque & Integrator 30
Roger,
You are are right, DATYPE=3 should allow for the 06 command to be sent. The
problem is that I need to write a number into the modbus register to engage
the relays in the field unit and not a single bit. For example, I need to
write a hex 0900 for relay 1, 0A00 for relay 2, 0B00 for realy 3, and so
on. The output from the GDEV block is a boolean ( COUT_1 or COUT_2).
Each Six Realy Board unit has 6 relays and we have three pumps configured
per SRB unit. Relay 1 starts pump 1, relay 2 stops pump 1, relay 3 starts
pump 2, relay 4 stops relay 2, and so on.
Therefore, when I start pump 1 (COUT_1 in the GDEV block is set to true) I
need to write a 0900 into an ouput register and sent it with the 06
command. If I stop the pump (COUT_2 set to true) a 0A00 has to be written.
The question is how I write these values into the output register whenever
the parameters COUT_1 and COUT_2 of the 3 pumps are set.
Regards,
Douglas
Roger Smith <RSmith@xxxxxxxxxxxxxxxx>@freelists.org con fecha 28/11/2001
12:25:09 PM
Por favor, responda a foxboro@xxxxxxxxxxxxx
Enviado por: foxboro-bounce@xxxxxxxxxxxxx
Destinatarios: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
CC:
Asunto: Re: [foxboro] Connecting Limitorque & Integrator 30
If your MDSCAN block is configured with DATYPE=3, function code 06 should
be
used for the writes. While this data type is for registers ("analog" type
data or Modicon 16 bit data type 4xxxx), you can still access individual
bits with CIN, COUT, MCIN, MCOUT, etc. For example, if the MDSCAN has
DATYPE=3, and RDADDR=1, a COUT can be configured for PNT_NO=1.2 to set the
second bit in that register. I believe the same should be true with the
MOVLV but I have always used COUT's. You can actually read several
contiguous registers, treating some as analog (using AIN, AOUT etc) and
others as Boolean.
I can't remember if the bit mapping between Foxboro and Modicon is reversed
(i.e. low order versus high order) but once you figure that out it should
be
simple.
Roger B. Smith
Process Control Engineering
Waste Water Services
City of Atlanta
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of DOUGLAS NAVARRO
Sent: Wednesday, November 28, 2001 10:33 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Connecting Limitorque & Integrator 30
Does anybody have any experience connecting Limitorque's two wire valve
system (with UEC
and Six Relay Board units) via an I/A Series Integrator 30 for modbus ?
We are trying to configure an Integrator 30 to be connected to the DCS port
of a DC100 master
station for Limitorque's two wire system. We are using the MOVLV and the
GDEV blocks to configure
valves and pumps respectively, but we have encountered a problem with
sending commands
to the SRB units whose 6 relays(K1 throuhg K6) are commanded by the modbus
06 command
(Preset single register) instead of the 05 command (Force single coil)
which is used for UEC units.
As far as I can see the output of the MOVLV and GDEV blocks are boolen
values suited for the
05 command and not an integer value which would be required for the 06
command.
I would appreciate hearing from anyone who has tackled this situation
before.
Regards,
Douglas
*************** PDVSA4S INTERNET E-MAIL USE ***************
This message may contain information solely of the interest of PDVSA or
its businesses. Copying, distribution, disclosure or any use of the
information contained in this transmission is permitted only to
authorized parties. If you have received this e-mail by error, please
destroy it and notify webmaster@xxxxxxxxx or the sender by reply email.
****** USO DEL CORREO ELECTRONICO DE PDVSA HACIA INTERNET ******
Esta nota puede contener informacion de interes solo para PDVSA o sus
negocios. Solo esta permitida su copia, distribucion o uso a personas
autorizadas. Si recibio esta nota por error, por favor destruyala y
notifique al remitente o a webmaster@xxxxxxxxxx
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist
list info: //www.freelists.org/list/foxboro
subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist
list info: //www.freelists.org/list/foxboro
subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
*************** PDVSA4S INTERNET E-MAIL USE ***************
This message may contain information solely of the interest of PDVSA or
its businesses. Copying, distribution, disclosure or any use of the
information contained in this transmission is permitted only to
authorized parties. If you have received this e-mail by error, please
destroy it and notify webmaster@xxxxxxxxx or the sender by reply email.
****** USO DEL CORREO ELECTRONICO DE PDVSA HACIA INTERNET ******
Esta nota puede contener informacion de interes solo para PDVSA o sus
negocios. Solo esta permitida su copia, distribucion o uso a personas
autorizadas. Si recibio esta nota por error, por favor destruyala y
notifique al remitente o a webmaster@xxxxxxxxxx
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist
list info: //www.freelists.org/list/foxboro
subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist
list info: //www.freelists.org/list/foxboro
subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
