If it works in the DM ,it will work in FV. I didn't realize that the toggle command had been changed to support bit twiddling. Good to know. Regards, =20 Alex Johnson Invensys Systems, Inc. 10900 Equity Drive Houston, TX 77041 713.329.8472 (voice) 713.329.1700 (fax) 713.329.1600 (switchboard) alex.johnson@xxxxxxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] Sent: Friday, August 04, 2006 3:25 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Trying to set CINMSK in a MCIN block through a display Alex and Tim, It can be done in the Display Configurator using SELECT FUNCTION execute program and then typing in the following command: dmcmd toggle CMPD:BLK.CINMSK.B1=3D20 where .B1 is equal to CINMSK for CIN_1 and .B32 is equal to CINMSK for .CIN_32 Not sure how you do it in FoxView but I don't think that is an issue with Tim. Tim I will forward a DM compatible graphic as an attachment that you can FTP to your UNIX system if you want one. Let me know. Tom VandeWater Control Systems Developer/Analyst Dow Corning Corporation Carrollton, KY USA -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Johnson, Alex P (IPS) Sent: Friday, August 04, 2006 3:08 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Trying to set CINMSK in a MCIN block through a display Sadly, FV/DM do not allow you to toggle a single bit in a packed Boolean. =3D20 So, try this: =3D20 1) Create two MCOUT blocks and an MCIN block 2) Put all three in simulation mode (IOMOPT=3D3D0) 3) Put all three in automatic mode a. MA=3D3D1 and b. INITMA=3D3D1 and/or=3D20 4) Connect the MCOUT PAKCRB output of the first MCOUT block to the II01 parameter of the new MCIN block. 5) Connect the MCOUT PAKCRB output of the second MCOUT block to the II02 parameter of the new MCIN block. 6) Connect the PAKCIN parameter of the new MCIN block to the CINMSK parameter of the MCIN block with the "problem". 7) Build your graphic to allow you to toggle any of the 16 MCOUT input parameters (IN_1 to IN_16) in each of the two blocks. =3D20 In this configuration, the display will change a bit in the input of one of the MCOUTs. The MCOUTs will update their PAKCRB output. The PAKCRB output will drive the new MCIN which will consolidate its inputs into a single 32 bit packed long - PAKCIN. The PAKCIN parameter will mask the inputs to the original/old MCIN. =3D20 Make sense? =3D20 Regards, =3D20 Alex Johnson Invensys Systems, Inc. 10900 Equity Drive Houston, TX 77041 713.329.8472 (voice) 713.329.1700 (fax) 713.329.1600 (switchboard) alex.johnson@xxxxxxxxxxxxxxxx =3D20 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] Sent: Friday, August 04, 2006 12:15 PM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] Trying to set CINMSK in a MCIN block through a display =3D20 I currently have a MCIN block that occasionally will read faulty data at point 31. I know that I can set the CINMSK to "2" instead of "0" to disable the point. Looking in a reference book I see that CINMSK is settable and connectable but it is a "pack_l" input as opposed to real, boolean, integer or string. Currently to change this point I need to go into the configuration, make the change and it CHECKPOINTS as part of exiting. I would like to make a simple button on a screen (or a text input) that I can change the CINMSK between 0 and 2 without causing the whole CP to checkpoint. ideally the one action would also set CIN_31 to true. I am not familiar enough with the system to create a button that will do this. I have copied buttons before that toggle a point and changed it to the point I need to toggle but that is as far as it goes. The system was initially installed around 1990 and uses the same program to make displays as it did back then. It is a UNIX system. =3D20 Any help would be appreciated. =3D20 Sincerely, Timothy Healey Facility Engineer Wyeth =3D20 =3D20 =3D20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =3D20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: =3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin to unsubscribe: =3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave =3D20 =3D20 =3D20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =3D20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: =3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin to unsubscribe: =3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave =3D20 =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://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