navillusi
MrPLC Member-
Content count
206 -
Joined
-
Last visited
Posts posted by navillusi
-
-
I have come across an old Klockner Moeller PS3 plc installed on a site and do not have any software or lead to communicate with it. What lead and software is required? Are the above still available to buy/download? Is there someone who has the required equipment who could extract the program for us (UK Midlands), so we can replace with a new? Any help is appreciated Regards -
Any Melsec instruction which is suffixed P (i.e. +P MOVP INCP) Will execute the instruction on the rising pulse of the logic proceeding it, i.e. a one shot instruction rather than executing it on every scan -
if your data types are all the same, you can use arrays, move your DUT defined variables into an array of the same dimension, this array can then be moved into your user defined function blocks as a single addressable element. Hope this answer matches your question! -
In the transfer setup in GX developer, double click the yellow box on PC side serial, you can then select com1 or usb port -
Using GX Developer is far easier than piloting a space shuttle. In fact, the default setup for comms on GX is direct to the CPU using the standard SC-09 cable, so you dont actually have to set anything up. Assume that you are using the SC-09 cable connected to the CPU RS422 port and COM1 on your PC. From a blank project select read from CPU. Next select the PLC series you are connecting to - ACPU, the next screen you get is transfer setup, you should not need to change anything on this screen, if you are unsure whether or not comms is ok, click the test comms button, if you are happy, select the OK button. The software will now connect to the PLC and you will have to select what you want to read out of the PLC by ticking the appropriate selection, i.e. Program, Parameter, Device memory etc. Click ok, follow the prompts, and the program should be transferred. -
I may be wrong, but I seem to remember that some of the panelview terminals will not accept the tag based address system of the compactlogix processors, instead file:word/bit addresses have to be used. The variables that you wish to display on the panelview must be copied into an array, e.g. data[0..10] of INT, this array is then mapped to an SLC/PLC message file in the processor, e.g. to file 7. So in the panelview it would be read the same as an SLC e.g. N7:0 -
There will always be more than one approach to something like this. You can use multiples of timer, counters etc or use the inbuilt timing relays which are available in all mitsubishi PLC's. If you are using 6 ouptuts, the temptation is to use lots of interlocked timers, which can lead to confusion. One solution is to use only one timer and use comparison instructions e.g. T0 --]/[-----------------------(T0 K100) 10 second timer --[>= T0 K0]--[<= T0 K10]-------(Y0) Turns on Y0 for 1 second out of 10 --[>= T0 K11]--[<= T0 K20]-------(Y1) Etc... --[>= T0 K21]--[<= T0 K30]-------(Y2) --[>= T0 K31]--[<= T0 K40]-------(Y3) --[>= T0 K41]--[<=T0 K50]-------(Y4) --[>= T0 K51]--[<=T0 K60]-------(Y5) As I say, there is always more than one way..... Hope it helps! -
There are significant differences between GX IEC Developer and GX Developer, but I'll try to explain the most significant difference which is the way that it handles the code that you write. In GX, what you write in ladder or list gets sent to the plc - straight forward. In GXIEC you can create your programs in any or all of the 5 IEC language editors. So say for example your program consists of 5 pou's each written in one of the editors, Lad, FBD, ST etc. What is written to the PLC is not what you see on the screen. At the end of the day, all that is written to the PLC is melsec instruction list. The PLC itself does not understand, for example, what structured text is! GXIEC contains a "compiler" which translates all your nice symbolic graphical work (which you understand) into raw instruction list (which the PLC understands). Try writing a small program in IEC and then read it back in GX and you'll see what I mean. When the compiler does its job and converts your symbolic information into List and transfers to the PLC, there is the option to also download the symbolic information (on the download project options). Thus both the list and symbolic will be transferred to the PLC, then, you will be able to come along with a blank laptop and upload the symbolic information and you will have your "IEC" graphical code uploladed. There are dangers, the most significant one is that the symbolic information is stored in a seperate area to the program code. For A&FX this memory area is straight after the program code finishes. So when someone comes along and modified the program using a different editor (medoc or GX dev), the symbolic information will be destroyed (and there is no going back!). This means that when you upload in GX IEC, there is no symbolic information to read back so it will uploac the program in instruction list. It sounds to me like this is what has hapened to you! your other question about GXDeveloper was how to toggle between device addresses and comments? If comments are stored in the GX Developer file (unlikely if you've uploaded) they can be viewed from the View - Comment menu, if they exist at all. One point that must always be remembered with the IEC developer package is correct version control! You must always go online with the latest version - i.e. one where the code generation times of the project match. -
Can you advise of the model no of the plc or card? -
I have always had to carry round two laptops, one old one for medoc and one new one for everything else - now my back will be feeling better!! Excellent piece of information Cheers -
I have never seen the option in GX developer to export the file to a text file. I know you can expport A series files to gppa format or Fx files to fxgpwin format. Can you tell me where on the menu you are getting the export function from? What version of GX Developer are you using? -
Not sure exactly what you mean between "memory and status" bits, M - Internal relays - auxilliary relays used by the cpu and are not latched (cleared at power failure or cpu reset) L - Latch relays - auxilliary relays used by the cpu and are latched (not cleared at power failure) F - Annunciators - Internal relays convenient for equipment fault / failure detection V - Edge relays (q cpu) - similar to a one-shot B - Link relays - CPU devices used to refresh LB relays in a melsecnet network S - Step relays - relays for step instructions in sequential function chart -
The number of steps is not equal to the number of rungs, neither is it equal to the number of instructions used. Each instruction that you use in the program will have a corresponding number of steps, depending upon what the instruction is, the number of steps it uses will differ, generally, the more complex the instruction, the more steps it uses, for instance: -[ ]- (contact) instruction takes 1 step -( )- (output) instruction takes 1 step [MOV] (move) instruction takes 5 steps [bMOV] (Block move) takes 9 steps [RERP] (remote IO read) takes 11 steps (these instructions are from the A series & may differ for Fx & Q) -
Step 5 is a DOS program, which will run happily under windows 95 or 98. I have had no success in getting it to work successfully under NT or 2000, I believe it something to do with the way the com port is accessed? -
A2ACPU High speed, 14K steps, 512 I/O A3ACPU High speed, 30K + 30K steps, 2048 I/O A3NCPU 30K + 30K steps, I/O max. 2048, refresh/local I dont think that the demo versions let you download to the cpu -
The device test dialog (alt+1) will give you a history of what devices you have toggled. Close the project and re-open and the history will be cleared. -
Two cases exist concerning how to choose your IP address: Joining an existing network: The System Administrator will assign it to new nodes. Creating a private network: You can choose any non-reserved IP addresses Do not use 0, 1, 127 or 255 or addresses beginning with values greater than 223 as they have special meanings Also private internet address are in the form 169.254.xxx.xxx , 10.xxx.xxx.xxx or 192.168.xxx.xxx as these addresses are guaranteed not to be in use on the internet Some IP addresses have a special or reserved meaning 0.0.0.0 The default gateway address to which packets are sent if they do not belong on the local network. 127.0.0.1 Local loopback address useful for diagnostic checks using the ping utility 224.0.0.0 Default multicast address 255.255.255.255 Limited broadcast address A broadcast to any machine on the local network The first octet of an IP address will show the class to which the address belongs:- 1 to 126 is Class A which will support upto 16,777,214 hosts 128 to 191 is Class B which will support upto 65,534 hosts 192 to 223 is Class C which will support upto 254 hosts Even when networking 254 hosts it is unlikely that they will all be in the same physical location, and therefore the network is constructed in smaller subnets An IP address can be interpreted as two fields:- netid + hostid or with a subnet mask applied netid + subnetid + hostid The subnet mask shows which bits are the netid and which are the hostid 255.255.255.0 = 11111111 11111111 11111111 00000000 255.255.0.0 =11111111 11111111 00000000 00000000 -
Forcing on Mitsubishi PLC's does not work in any way similar to that of RSLogix. If you force on an output coil (eg Y20 or M100) it will be on so long as there is no reference to it in the program code, if there is reference to it in the code, you will turn it on and then after the next scan, the plc will turn it off again. Inputs work slightly different, you can turn them off or on as many times as you like and the PLC will evaluate them in whatever condition you set. Trouble is, there's no way of knowing what inputs have been forced! For example, you have an emergency stop button that gives a 1 for healthy, you are testing and force that input to a 1 by mistake, someone presses the stop button and the plc will still think it's ok! The only way that I know of removing all of the forces is to switch the processor to reset. -
The last time that I used HMI tools, I too struggled for a while to get it to communicate. There were two problems, which look a bit simple but at the time they were causing me frustration! 1. The com port I was using was already in use with GX developer (told you it was simple!) 2. The comm port set-up of HMI tools was different to that of the serial port on the HMI, however, when I changed HMI tools to match it still did not work. What I then did was set up another connection (connection No.2) with the same comms parameters and it worked! -
In e-designer, check the location (name) of the recipe directory. HMI tools must look in the same location in order for it to read -
Try using the "MX Sheet" add in from Mitsubishi, it is an add in for excel in which you can read and write values direct from your sheet into the cpu. Works on all cpu's in the range -
Simple answer is yes, there are different communications protocols, just dont ask me to explain them as I don't know! I know of the three types, FX, A, and Q i.e an A1s uses the same protocol as a QnA but different to a Qn. As for device addresses, yes they will be the same, i.e. D, W, R, M etc but each will have a different range applicable to each cpu -
I believe that Mitsubishi will be releasing an ethernet module for the FX2N range later this year, so I am told.... -
To use the RS232 port on the terminal for printing is possible, however, it's not very nice, for a start you need a serial printer with graphics capabilities and the manuals say "Print errors may occur if large graphics blocks are printed". Printing is really only reccomended for text based screens rather than graphical based (eg trands). This does not mean that it will not work, it may just be messy! I would reccomend the following two alternative solutions: Use HMI tools to extract the trend data into a csv file and print the trend via excel. Or fit an IFC-PI card to the HMI which is a parallel printer port, this one is ok for graphics etc
SoftPLC
in Other PLCs
Posted