navillusi

Not "Bugs" - "Features"!! Version 6 has many changes from version 5, mainly to do with the way the IEC compiler works (the IEC people have forced the changes), this will make any use of the EN/ENO compile differently to that in version 5. Check out Mitsubishi's website for more information

I had quite a few problems when using this system a while ago. I could communicate over ethernet using GX developer and the PLC's would not communicate with each other, OR I could not communicate over ethernet using GX developer and the PLC's would communicate with each other. Never both together In order for the PLC's to communicate, the system must be changed from Automatic repsonse system to IP address computation system AND the IP address of the computer must be included. As for the Power on/off, can you not toggle Y19 (initial request) in order to get the card to reset?

What software are you using to program the PLC? Medoc, GX Developer or GX IEC Developer? Medoc only lists A0J2 and GX Developer only lists A0J2H so you cannot change the cpu type easily, however, sometimes Medoc does not realise the difference in an 'H' cpu so you may be able to write directy to the new A0J2H. I'm not sure of the need to read the microcomputer area, this is usually a portion of memory laid aside for the purposes of maths & SFC, however, on a new program you have to determine how much memory is reserved for microcomputer, this is in the parameters section.

The figure quoted in Watts is the total power consumed by the card on both the 5v and 24v supplies. Total for the card, not individual channels. Add up all the 5v currents - total not to exceed PSU 5v rating, ditto for 24v currents.

SLC Devicenet card is part # 1747SDN Also available are modbus cards (Prosoft 3350MBP0) and basic RS232 cards 1747KE

This is a problem that many people come across using GX IEC Developer, unless the program has been written in GX IEC in the first place AND the symbolic code was downloaded to the processor, you may only read the code back in Melsec IL. If the PLC was not programmed with IEC, you may be better off programming with GX Developer, GPPWin, or even DOS Medoc, as with these editors you can switch between list and ladder.

Parameter 340 should be set to 1 and Parameter 79 set to 7 (cc-link mode) One thing that caught me out was that every time that the frequency command setting is changed (RWw1) you must set RY D (frequency setting command (RAM) and then reset it when RX D is 1

Can you provide some more data? What communications card are you using? AJ71UC24 or others? What protocol are you using? Dedicated protocol, no-protocol, bi-directional, computer link?

Micrologix 1000's can be programmed using a "starter" version of RSLogix500 which will program the Micrologix and SLC's with limited functionality, such as you can only use RS232 communication drivers. This is 9324-RL0100ENE The full version is 9324-RL0300ENE (about twice the price) RSLogix 5000 is used to program the ControlLogix, SoftLogix and CompactLogix family

Hardware reference manuals and instruction set reference can be found at www.meau.com

Rather than using the four counters, which I assume that you are using the done (finished counting) bit to trigger the events, you could use the accumulative value of the counter to trigger the events by using comparison instructions, i.e: LD> C235 K50 AND< C235 K70 ST {event one} LD> C235 K150 AND< C235 K170 ST {event two}

If you let it, the HMI will take care of all the recipe control and you will not need to write any code within the PLC to do this. The HMI will store, delete and load recipe data to its own directory, and transfer this to the PLC registers that you will have designated within the recipe. Some help from E-Designer: Current directory register: You specify here the first of four 16 bit registers where the terminal inserts the name of the recipe directory specified for the block. The name can then be presented in an ASCII object. The function always uses four registers (eight characters) irrespective of the length of the recipe directory. Recipe ctrl. block Control block to save/read/delete recipes through the controller system. Creating and transferring recipes with the controller system Through a control block in the controller system you can create, transfer and delete recipe files in the terminal. The files created from the controller program are compatible with the recipe files created from the terminal. I.e. recipe files created in the controller program can be downloaded into the terminal, and vice versa. The control block appears as follows. Under Setup/Recipe Settings you define the first register in the control block. This and the seven following registers are used as control registers. The control block is described in the following table. Ctrl reg 0 Command Command register set by the controller system. Available commands: 0: No command. 1. Save recipe to terminal. 2. Read recipe from terminal. 3. Delete recipe from terminal. 4. Create recipe directory. 5. Change recipe directory. 6. Delete recipe directory. Ctrl reg 1 Handshake Handshake register set by terminal. 0. Ready for new command. 1. OK 2. Recipe file write error. 3. Recipe file not found. Ctrl reg 2 File name char. 1-2 Name of recipe file/recipe directory in the terminal. Ctrl reg 3 File name char. 3-4 Ctrl reg 4 File name char. 5-6 Ctrl reg 5 File name char. 7-8 Ctrl reg 6 Start data register The first data register to be read/written to/from recipe file. Ctrl reg 7 Number of registers Number of registers to be read/written to/from recipe file. The following procedure must be carried out: 1. The handshake register must be 0. If not, reset the command register to 0. 2. Enter the command in the command register. 3. Wait for the ready signal or error code in the handshake register. 4. Set the command register 0. The terminal will now set the handshake register to 0. Note! Recipe directories created in E-Designer cannot be deleted in RUN mode. See also section "Recipe directory in run mode ". Limitations Recipes created in the controller system can contain a maximum of 1000 registers. Only data registers can be used. The following characters cannot be used in recipe names: ! ? < > ( ) + / * = ° % # : . [space] , and - This is really only used when you want the PLC to load & save recipes on it's own, there is another way, you can use a device within the PLC to trigger a macro in the HMI to load the recipes for you.

Remove the read only attribute after extracting them from the CD. GX Developer will not open read only files

I would suggest reading the FX Series Programming Manual II, in section 10 there are example programs for PID control and all the equations that go with it. Go to www.meau.com and look for manual number JY992D88101D

Use the "import from Medoc File" option in either FXGPWIN or GX Developer As long as your documentation exists in the medoc file, it will exist in the imported file

Attached is a packed project from IEC Developer V5, it contains a couple of examples of function blocks and how they can be used etc. (Use the "project restore" function from the extra's menu). The best way to learn IEC developer from the start is to attend a training course. If you are in the UK perhaps I could offer you one?!? TRAFFIC.pcd

There is a utility available from Rockwell called "panelview transfer utility" which is available seperately from the configuration package which will allow you to backup and restore your panelview programs but no editing/viewing/configuring etc. It is purely for transferring. I do not know exactly how much it costs but it is far cheaper than the full blown panelbuilder software, I suggest you contact your local distributor. As for the SLC package to do the same, I have never seen one.

The file you have got is probably from a newer version of RSLogix, I think we're up to version 6 now. You cannot open a file from a newer version.

If you are using a version 2.x Mac50 you are quite correct, the new display reg is greyed out, however, if it is a version 3.x you have, the box is not greyed out thus you can use the same way as an e-series. To make the screens appear as you need, you need to set the display signal in the block header to address perhaps an M coil in the PLC. If you set this coil for a second or two, the Mac will load the block with the relevant display signal. Bear in mind though you must have only one reference of a display coil in the HMI project!

From the AB website: Thus you should be able to connect the serial link from the robot direct to the DF1 port of the PLC as long as they will both talk the same protocol. What protocol does the robot use? If you use this port you will not be able to connect your PC to it for programming and diagnostics. I would suggest that you speak to AB directly to confirm that the PLC will communicate with the robot using this port

I have had a fair amount of experience of the Q series PLC (from Q00j up to Q25h) I would certainly reccomend them, size, power, cost, versatility, performance etc. So far I have no bad opinions of them!

Chris, I have a Dox 5 users manual (version4) and a Satcon 5 programming manual in PDF format if it will help. The manuals weigh more than 2mb so I cannot post them, if you let me have your email address I'll mail them to you. Ian

In the SLC instruction set, the AEX command (ASCII string extract) lets you split up an ascii string and move it elsewhere. It may be a bit long winded, but you could use this intruction to split up your !M into ! and M (you may have to use the instruction twice), when you have split it up it will reside in two seperate string registers, you may then use the ACI (Ascii string to integer) to convert it back to an integer. There is probably an easier way though!

EnvMel is the "environment of Melsoft", all it is, is a setup to ensure the correct paths etc prior to the installation, you only seem to need it on Win XP & 2000 for some reason. Oh, and when I said suitable for windows XP I meant "Supported, Tested and Certified" for Windows XP. Many programs will work on many different operating systems but it does not necessarily mean the manufacturer will support it!

I am assuming you are connecting to a mitsubishi PLC To connect the robot to the PLC, fit a C24 card (serial comms module) to the PLC, and connect the robot using the serial link. Connect your PC to the PLC using a serial cable from the PC to the programming port of the PLC (an SC-09 cable for A series or a QC20R4 cable for a Q series) You can also complete the loop by connecting the robot to the PC using the remaining centronics interface