The Cat

Not used the E1000 series HMIs yet myself but if they have the Recipe function that the original E series had why not use that - it means that you dont have to make any settings in the PLC or concern yourself with tracking of the data memory position. Recipies are stored under an identifier which makes calling them up on the HMI for monitoring or changing much easier. With fixed parameter sizes screen creation using indexing takes the grunt out of that side of things. Just need to make sure sufficient memory is available and allocated in the HMI. If its not available it should have been! Sorry! just re-read the original post and of course this does not address the retention issue described only the ease of re-establishing the date if it does get lost.

Just a little clarification about Forcing in Mitsi PLCs........ Its a while now since I've had to use Forcing but I think that the following is correct. With Medoc (and non-Q series PLCs using GX) inputs can be forced but may be overwritten such that if the input hardware is off you can force the channel on or off but if the input hardware is on the channel cannot be forced permanently off. With outputs if the channel can be forced on or off if it is not in the ladder but the program will override at the end of scan as has already been stated if it is in the ladder. Usual way round this is to use an M coil to directly drive the output and force that The same is true with GX and Q processors unless you use the Online - Debug - Forced input output registration option. With this the inputs and outputs can be properly forced irrespective of the program. As mentioned, I believe this is correct but dont have the hardware with me to be sure. Comments appreciated!

In addition to this, the F coil reference address (often referred to as annunciators) is transferred to a stack (at least in FX) to I think a maximum depth of 8. Dedicated D8*** registers hold the most recent F coil address (top of stack) and the number of filled positions in the stack. New F addresses are pushed on and the stored addresses can be popped off under program control making a useful error detection or event record. The number of filled stack positions is automatically adjusted. Stack depth, etc may vary for other models.

Sorry to be a little late into the discussion. The derateing of modules comes about because the equipment itself is rated for use in ambient temperatures across a range, often 0-55C. When turned on, the contribution of the heat dissipation generated by the modules internal circuitry (attenuating resistors, etc)combined with the ambient temperature raises the local temperature of the components used towards their maximum functional limit. Thus, the higher the ambient temperature the fewer circuits that can be active (and dissipating heat) before the working temperature of the module goes outside the specified operating temperature for the components used. Reducing the number of channels that are useable as the ambient rises is a compromise for having a high number of channels available in the module when used at lower temperatures. The lower the ambient (forced or unforced) the more channels that are available.

Hi Function F670 K29 is a bit transfer This particular instruction will copy the 3 bits starting at (M)330 to the 3 bits starting at (M)260. F671 defines the head element of transfer origin F672 number of bits to transfer F673 head element of transfer destination F670 transfer instruction Hope this helps Colin Tydeman

I think you are right Colin. If memory serves me correctly, the FX-2DA and the FX-4AD were the standard solution when FX2N was introduced until the "correct" modules were fully available.

To my understanding, the update of M and D devices cannot be changed. Certainly, the older FX range of PLCs operated only on refresh principal - I believe that subsequent models do the same. Again, older A and AnS series products (possibly not all) had a switch in the CPU that determined the operating mode. It is my belief that Q series utilises the refresh mode also but benefits from the additional refining program options such as SCAN, INITIAL, SLOW, CONSTANT. The FX programming manual or one of the A series user /fundamental manuals should explain more clearly how C and T devices work and give examples of the errors in accuracy that can occur as a result of dependancy on scan update. Updating of C and T devices refers to the setting of the "completed" coil -not the running value

Updating of devices depends on the mode of operation of the PLC and the model of PLC being used. With some versions there is no choice of operating mode, with others it is selectable. Generally, in (batch) refresh mode, M coils and register devices are updated in "real time" whereas X inputs are updated at start of scan and Y outputs, timers and counters are updated at end of scan. In direct mode, Xs and Ys are updated by reference to the device state as it is addressed by the program i.e. in real time. Other devices are as for refresh mode. Both modes have advantages and disadvantages depending on the application!

Colin Further to my previous reply, to qualify the statement regarding this function in GX, the Device Memory option works mainly as DWRSET in Medoc but depending on your processor choice, a further function DEVICE INIT is available which may be useful. If the feature is available it appears as a directory in Project Navigator. Just wanted to be clear as there is another post running in a similar vein "Saving Register Values" based more around Medoc and GX. Colin Tydeman

To refine the use of DWRSET, if you enter edit mode (F2) in that screen you can mark a specific range of registers to transferusing F3 to start and end the range. Within that range registers not to be transferred can be deselected using SHIFT-F3. I think that you can select multiple ranges (maybe). If you use this feature answer (N) to the question about transferring the whole DWR range when prompted. There is some crossover here with the current post "Data register values, how to retrieve them" although this refers to GX and GX-IEC Colin Tydeman

Ricicle I think your problem is possibly in two areas.The first is around what happens when basic maths is used in Mitsi PLCs. If you multiply two 16-bit registers together you get a 32-bit answer even if all the higher register bits are 0 so you need to view the result as 32-bit to ensure accuracy. The destination register defined in your instruction is the LS register. When you divide, if the values to be calculated are potentially 32-bit (as could be the case here) you will need to use a 32-bit divide instruction (DDIV or D/). This will cause the result to be found in the first two destination registers defined in your instruction and the remainder appearing in the next two registers (four registers used for the result of a 32-bit divide). Obviously, both these values need to be viewed as 32-bit numbers unless, as you say, the initial multiply result is less than the 16-bit limit, when all the upper registers in the 32-bit calcs will be 0. The second area is the display capability of the E150 HMI. Not sure about this as I've not used that model for some time but is it not possible to display 16-bit register values using an Analogue Object assigned as, say, D100 and to display a 32-bit register value using the notation D110L, for example? Summary 16-bit multiply D0*D1=Dn ,D(n+1) 32-bit result 16-bit divide D0/D1=Dn , D(n+1) 16-bit result , 16-bit remainder 32-bit divide (D0,D1)/(D2,D3)=[Dn,D(n+1)],[D(n+2), D(n+3)] 32-bit result , 32-bit remainder In all cases Dn is the root destination register defined in the instruction. Hope this makes sense and is of some help. The Cat

Yep! Guilty as charged. Moved onwards, upwards and sideways since then but still doing a bit.

Hello Colin Just to expand on a possible solution...... In IEC, enter Debug - Device Edit. You can then define device ranges by clicking into the shaded L/H columnand defining the root. Define your required ranges accordingly. Using the R/H mouse click in any individual cell or range of cells gives you further operational and view options. Back in the Device Edit window you can Save to / Load from files in .xls format and Upload /Download to the PLC. So, define your ranges, upload from the PLC to save current values, save to a file in a defined directory. You can then use the same route to reuse the values but obviously using the Read file and Download to PLC options instead. In GX the Device Memory option is the one to use. Regards Colin Tydeman

Not certain if it will be what you are looking for but have you tried saving the register range in Medoc's DWRset function and then uploading the file into the new PLC via the same route in that project assuming the "new" PLC is also to be programmed using Medoc.

Good day I'm new also but not to Mitsubishi. The file extensions that you mention are, I believe,from a project created in MEDOC and are the project header, monitor, name, program, parameter and print files. I would suggest that you try simply copying them all into a project in something like MEDOC 2.4 and view from there in its (probable) original form. Hope this helps.