HMI & SCADA
Use this forum to ask about any brand HMI or SCADA software package.
1,153 topics in this forum
-
- 2 replies
- 5.6k views
-
- 0 replies
- 241 views
-
- 6 replies
- 1.2k views
-
- 0 replies
- 701 views
-
- 2 replies
- 708 views
-
- 0 replies
- 260 views
-
- 1 reply
- 295 views
-
- 10 replies
- 568 views
-
- 1 reply
- 492 views
-
- 1 reply
- 926 views
-
- 1 reply
- 1.3k views
-
- 1 reply
- 312 views
-
- 6 replies
- 605 views
-
- 4 replies
- 475 views
-
- 1 reply
- 2.1k views
-
- 3 replies
- 673 views
-
- 5 replies
- 3.9k views
-
- 3 replies
- 339 views
-
- 7 replies
- 943 views
-
- 9 replies
- 5k views
-
- 0 replies
- 840 views
-
- 0 replies
- 849 views
-
- 0 replies
- 960 views
-
- 4 replies
- 3.5k views
-
- 0 replies
- 1.3k views
-
Posts
-
Taking a quick look at the Mettler Toledo Manual it appears to use Socket Communications over Etherent. So you'll need a series of messages in sequence. A) Open Socket Connection {IP Address and Socket Number - 1026 default} B) Function Command - See Appendix C C) Message Read or Accept Logic. Definitely using in an I/O tree will be easier. -
One solution for introducing a deadband would be to use the S:14 register which holds the unrounded quotient. For Example: Case A N7:7 = 5678 DIV N7:7 100 N7:8 = 57 but S:14 = 56 Case B N7:7 = 5623 DIV N7:7 100 N7:8 = 56 and S:14 = 56 This eliminates the xx50 bounce. You could also build a memory feature. N7:7 = Initial Reading 5678 N7:8 = Low Deadband CPT N7:7 * 100 / 102 = 5566 N7:9 = High Deadband CPT N7:7 * 102 / 100 = 5791 Next Time is N7:7 is inside deadband do nothing otherwise calculate new deadband and adjust.
-
Counterpoint - I have seen the Prosoft Profibus and ProfiNet Cards work in a Control Logix chassis. Using a Field Bus common to both RA and Siemens will be critical so Ethernet/IP or ProfiNet would be my choices.
-
Just an additional update and correction. The Stratix 5400 does do NAT it's what is called Static NAT, while the 1783-NATR does dynamic NAT DYNAMIC NAT maps an Automation Device with an Inside IP {192.168.1.2 for example} to an Outside IP {123.45.67.89 for example}. Any internet connected device wishing to communicate with the Automation Device does so via the Outside IP. STATIC NAT maps an Automation Device with an Inside IP {192.168.1.2 for example} to an Outside IP {123.45.67.89 for example}. STATIC NAT must also map every Outside Device with an External IP {98.76.54.32 for example} to an Internal IP {192.168.1.32 for Example}. With STATIC NAT if both mappings don't exist the Internal and Outside Device cannot communicate. Obviously for someone familiar with Commercial Router NAT functionality which is DYNAMIC the STATIC NAT of the STRATIX Family is frustrating and a learning curve.
-
Personally I would leave it structured and use labels, the only drawback is the ladder viewer on the GOT. Label based programming offers a lot of things that you cannot do in a simple project, like arrays and structured data types. -
There are some basic online tutorials on the Mitsubishi website that might benefit you in learning the addressing of the controllers.
-
mcgs pro software problem is no upload project file system error. my HMI # mcgs tpc 7022kx -
Yes that is correct. it is that simple ----| X20|--------(Y30)----| It is the same as most PLC's some have built in I/O like the FX series where the I/O starts at X0-X27 (octal based so X0,1,2,3,4,5,67 then 20,21,22,23 & so on Note: On FX only base 8 any expansion cards follow on depending on the position. Q series are a bit different where there is no built in I/O so as default the addresses will be allocated as per the card fitted for example if an Input card was in slot 1 and is a 16 way card the inputs are X0 to XF (as it is 16 way card) & so on, however, it is possible to change the actual addresses in the PLC Parameters but in reality that is not normal. special cards are often 16 bit or 32 bit so again if a 32 way input card was fitted in slot 1 then the input numbers by default would be X0-X1F. -
Does this mean that if I'm to run a simple push button to LED program on a rung, the open bit would be addressed starting from X20 and output starting from Y30? Really sorry if these questions are not supposed to be asked, I'm moving from Siemens to Mitsubishi and haven't been able to get useful resources online, hence I'm having a lot of confusion -
-
You are correct Parky, therefore I haveto rewrite it in simple ladder type without label. Or you can suggest any way to convert it?
-
By Ndramountanis · Posted
I am interested in the : 9324-RL5300ENE: RSLogix 5 Offline/Online 9324-RL0300ENE: RSLogix 500 Standard Sent PM -
I know, however, the specs stipulate the structure of the IEC way, I did a lot of assembly language programs & the same rules apply, In assembly & in other higher level languages. In the case of those the variables are put into the stack i.e. the inputs to the functions are passed to the temporary variables in the stack & passed back out from the stack as returns. As Omron, Mitsubishi & probably many others the code has not changed that much, indeed probably many of the standard functions will work that way you parameterise the function with inputs & outputs Omron tend to still use physical memory like bits/words etc. & the memory map is fixed as such, the IEC convention is just a way in many cases to implement the functionality of assembler or C, pascal etc. Because even Omron still rely on the standard types of variables like Mitsubishi etc. it is almost certain that instead of using the processor stack it uses a reserved area (or possibly a new area of memory but regardless of how it does it the fb can still be considered in a way where variables are passed to it & returned, as physical inputs cannot be used as coils is the reason that there is a strict convention on what variables can be read/written to. One other thing people do not realise is that you do not have to pass variables through the FB interface you could use globals that are exposed to all code within the PLC, however, it means that an FB can only be used for one instance as if a global is used directly inside an FB all instances will write or read that variable, indeed I sometimes use a global but only in the sense of perhaps a clock pulse that all calls to the FB will need, an example is say A one second clock where each call to say a valve control FB where a variable is used as an alarm time to detect a valve reaching a position within a given time. Many people fail to realise that the introduction of the IEC 61131 is just a similar functionality of structured FBD/ST & Ladder, to achieve this the different modes are still compiled in general into what could be considered Instruction list (IL or STL) of the original code, most still use this & it does appear that Rockwell are one of the very few that introduced IEC from scratch i.e. no real compatibility with the older SLC & PLC5 but instead mimicked the variable names for example N7:xx to allow conversion, knowing Rockwell, you will probably find the underlying code is just a re-hash of the SLC & PLC 5 just as their HMI/Scada was a re-hash of the old RSV32 just look at the similarity it is almost a enhanced clone. To re-emphasise my reasoning is that regardless of the platform the IEC convention is supposed to be a standard regardless of if it is Omron/or other platform there is a reason for the in/out parameter & to me it is obvious, yes you could pass the same variable to an FB by configuring it as an input & seperately as an output but the idea is that to someone looking at the code knows instantly that data could be manipulated in more than one place. not just within the FB.
-