Gambit

MrPLC Member
  • Content count

    2639
  • Joined

  • Last visited

Posts posted by Gambit


  1. A board is something like a network card, serial board or any PLC communication card. One board per server should be enough but you need two ports defined per server. before you disconnect the main network is the standby server gettings it's info from the main or is it running seperatly?

  2. It shouldn't matter that you use 2 different networks. I have a test system with 4 LAN's two for the PLC connections and two for the PC redundancy. Are you using the standard netbios communication between the citect servers ? Or the TCP/IP method which is standard from V7

  3. You probably have more than one TCPIP board defined for the same server Removing the duplicate TCPIP boards will resolve this issue. Check your config with the attachment redundancy_citect.pdf

  4. I haven't used capware yet. SO i do not know which setting they use. Remember the port nr setting in GX Developer is a Hex number.!!!! so 263 should be H107. However for UDP connections you can only start from port nr H401 - 1025. Does CAPWARE use ASCII or BIN comm. Maybe it's easier if you send the capware settings you've made. Attached are port setting which I think should work but i can;t be sure unless I see the capware settings

  5. It lookes like it's not the program it can't convert but some of the text creates a problem. I downloaded the project into a PLC did a new upload of the program so I lost the text comments. Copied the global variable list from the original project and tried to convert again. attached is the result Ouput_file.zip

  6. Check if you have the EPROM or EEPROM. If it's a EEPROM you can just upload, download & verify from GX DEV as you would do normally. If It's an EPROM you will need a A6WA-28P The EPROM is called A1SNMCA-8KP The EEPROM is called A1SNMCA-8KE

  7. 1) I would still try and use GX IEC Developer and and just make two or more FB for the moters ( for instance Basic an adanced). Having different code for 100 motors is hard to maintain. If your customer doesn't like indexing etc. you can instruct the compiler to create code for each time the FB is used. 4) In IEC you have two option. Create a variable (array) with or without a device attached. For instance if you declare an array of 10 words the compiler will choose a set of 10 registers which haven't been used in the program If you declare a array of 10 words with starting adress D100. It will use D100 - D109. If you than change to the array to 20 words D100-D119 is used. 5) Really I'd rather use a system Q. Than you have Error handeling and historie on every module and CPU You can even store it to a file so that you if the customer resets the PLC you can still retrieve the info. The special funct. util lets you check directly monitor the module. And best of all sampling trace for when you need to see what a program has done to devices each scan. Still if you have a problem there many people who have a lot of expercience with Mitsubishi PLC's from Amercia, ASIA Europe There always a continent awake to solve a problem. 7) Have you tried the merge function i think that i'll work. I mostly use IEC which uses a compiler wich makes changing and copying program parts much easier. 8) You can change between FX and Q but you have to convert to A series first. Not all instruction of the FX are supported by the system Q and vice versa but most of them are. Still it's a lot easier than changing a Siemens S5 to a S7. Check out this site about upgrading paths for mitsubishi it will show you why Mitsubishi you never waste your spend money and programming efforts http://www.meau.com/eprise/main/sites/publ...ansition_Center Still I might be bias cause I work for the Dutch distributer for Mitsubishi PLC's.

  8. You should really take a look at GX IEC Developer it has many features you need. Also IQ WORKS is coming out around June which contains GDII which is the combinantion of GX Developer and GX IEC Developer. IQ WOrks also has MT Developer and GT Designer and a configration enviroment GX explorer. This will solve a few problems 1- You can program FB is GX IEC Developer. 2- The english dialogs are checked and by UK and serveral languages will be available. 3- Check the GX IEC way 4- When programming in IEC standard you work with names instead of Devices much better. The compiler handel the devices 5- There are some new possibilities with system Q. which PLC are you using? 6- Writting in ladder is faster also FB's will really shorten the programming time

  9. You can't change it from IL directly into Ladder from GX IEC Developer. However there is a little program to do this for you though. I've uploaded the manual so you can take a look how it works. However the program might have been written in GX Developer. If it contains less than 1000 steps there is a FREE version you can download. 1009en_Ladder_Converter_GB.pdf

  10. Well You don't have indirect programming like the system Q Addrset but it is possible to using indexing All you need to do is place a Z0 - Z7 after the word device. This means that the value of Z is added to the register you are using. For instance if Z0=5 than D23Z0 = D28 For instance your program would look a little like this. M8002 ------- [MOV K0 Z0] {Read serial comm unit 1} [CALL P0] {Read serial comm unit 2} [MOV K8 Z0] [CALL P0] {Read serial comm unit 3} [MOV K16 Z0] [CALL P0] FEND P0 ----[bMOV D0 D1000Z0 K8] END Unit1 info will be on D1000-D1007 Unit2 info will be on D1008-D1015 Unit3 info will be on D1016-D1023