andybr

Walden If you have F2's you will have to keep Medoc., GX Developer does not support the old F series processors. We bought a number of licences for GX Developer a couple of years ago with a view to replacing Medoc but none of our technicians has ever taken to it. It may be just down to familiarity but absolutely every single one prefers to use Medoc wherever possible even if it has to be run in a window. I invariably end up having to make any changes to FX2's etc. which are not Medoc compatible myself as nobody else will ever get round to them. Andybr.

PLCer The database file should be in the Fix PDB directory and will have the extension .PDB. There will probably be more than one database file including one called Empty.PDB so you need to know which file your project is using. This can be found by opening the system configuration application (SCU). The active database is shown on the main window under the Node name. Andybr

Panic Mode As I understand it PLC code is required to open a port on an ethernet card for an A series processor even if this is only used for connection to a PC (SCADA etc). Sharing data between PLC's also requires code for this as well as code for the actual messaging. I am not an expert on the Q series and things might have changed but if it possible to use an ethernet card on an A processor without the above code I would be interested in hearing about it. Andybr

There are many ways of doing this with Mitsubishi A Series PLC's. My preferred method would be to have an ethernet card in each PLC rack but this involves quite a lot of code and a good understanding of what you are trying to do. Another option would be to use Melsecnet-B for sharing data between the PLC,s and an ethernet or serial card from the network master to the PC. This uses more hardware but would be much simpler for someone with limited experience. Andybr

PLCer The startup list for Fix32 is set up in the system configuration utility (SCU.EXE). Each "Project" must be set up as a seperate Fix Node. The files are normally all stored in the same Fix directories but you will usually only have to move the database file (PDF), driver configurations and picture files (ODF) from your development machine to your runtime machines. (Plus tag group files if you use them) Fix32 up to V6 used to come with an applet called KEYDIAG.exe which allowed you to view information on your key. I have checked the V7 CD and this does not seem to be present but it still seems to work on a V7 installation. Andybr KEYDIAG.EXE

Andriy I have checked my Medoc setup which should be the Default and my settings are:- 9600 Baud 8 Bits Odd parity 1 stop bit. I have never seen Medoc set to use 2 stop bits so you might want to try these settings.

The LED instructions were originally used for writing to the LED display on the A3 processors. When the AnA processors were developed Mitsubishi used these instructions to give access to a whole range of new instructions which were not available on the original A series (PID, Floating point maths etc.). You will need the programming manual for the AnA Dedicated Instructions to get details for most of these but the PID instructions had their own seperate manual. The same instructions were also used with the AnU processors.

Direct used to be the default mode on older Mitsubishi processors but I do not think it is even available on the current models. I always preferred to use refresh as I feel that this makes the system more predictable.

I recently installed a new ENBT card which was not recognised by Linx. I downloaded the latest EDS file from the Rockwell web site and this cured the problem. There has obviously been a recent firmware update.

This is just a guess but is the "other" A1sJ still running the MEDOC programme. When the A1sJH was released MEDOC would only recognise it as an A3 processor so your programme had to be created as an A3 project. It might be possible that the old PLC does not recognise the A1sJH as an A1sJ at all. You could try recompiling the old programme with GX developer so that both PLC,s are running programmes created with the same package.