GX developer: multiplication before sending value on AO card...

[Mas01]

I've got a Q68DAIN (Mitsubishi Q series analogue output module). On the HMI, Basically on the screen, the user types in a value as a percentage (0-90) and this opens the water valve by the same amount. Basically, I want to multiply D620 (the value typed) by 47 before sending it out on the AO module.
I've tried doing the multiplication on the HMI (gt designer3) as a little script...the multiplication works and D620 is multiplied correctly, BUT it also multiplies the on-screen angular value by 47 which is clearly not what I want.
I prefer to do the multiplication in the code if possible...I just think it's cleaner like that... I'm not keen on "embedding" code in the HMI if it can be avoided.
Can anyone suggest what the code update should be?
Thanks

 

[parky]

Just replace the D620 with a spare "D" register, multiply D620 by 47 and store it in the new register.

 

[Mas01]

Thanks, but when I press f4 to complie the change in get an error.message "The program before correction differs from the registered program <ES:010a4070> "

Any idea why I'm getting this?

 

[Mas01]

Update....F4 works fine for code updates on MAIN, but I only get the error in the ANALOGUE window (where I'm.making the change). I'm confused.

 

[Mas01]

This is the error message I get in the ANALOGUE nL window when I try to compile using F4.

Strangely, F4 works fine in the MAIN window.

 

[Mas01]

...then when I click OK, this message pops up....

 

[Mas01]

...and finally this message pops up....

 

[parky]

It appears that the code in the analogue program differs from the original in the PLC, this happens if for some reason it did not match before you modified it, every time you compile a program it date stamps it or creates a checksum, so when you try to make an on-line change it says the original date stamp or checksum for the on-line & off line did not match.
The best thing you can do is go back to the original code (presumably you have a copy or undo the changes i.e. do not save, do a compare & see what the difference is, when you correct it & add the extra code you will have to download the program it will not let you do an on-line change, there are a number of scenarios that cause this, a change at some point was done on-line but you failed to save the changes on the PC, a change & compile was done but not downloaded.
Things to remember, first before making changes compare your file with the program in the PLC before making any changes, ensure you have a backup of the code before you do any mods (important if you have not done any mods in the last few days i.e. gone back after a weekend).
One other reason it will not do an on-line change is if the changes are larger than the on-line change settings regarding memory shifting or there are calls to subroutines you have modified, then you have to do a compile & download in stop mode.

The compare function will only show the differences as mnemonic code i.e. list mode so not ideal & could show a lot of addresses after an extra contact has been inserted as it compares actual address locations & adding just one contact shifts all the others down.
Assuming the code running in the PLC is working ok you could upload it to your file as you are in ladder mode (cannot do this in a structured project unless the symbolic information has been downloaded to the PLC), but if it sends all the comments out (line comments) then you will have a project that does not make sense.
I suggest you do a compare of that block & post the differences here perhaps could see what has happened.

 

[parky]

Here is an example where a ladder project with multiple program blocks differ when compared file against PLC, you can see there is an extra contact in the file that does not exist in the PLC.

 

[Mas01]

Thanks parky...you hit the nail on the head. All sorted now &#55357;&#56397;

 

[Mas01]

Thanks parky...you hit the nail on the head. All sorted now ��

That "??" was a thumbs-up when I typed it in my phone!
Cheers

 

[jenish thumar]

Operation function

You can also use operation function of hmi entry.
in the write value multiply by 47.
and in monitor value divide bu 47.

I think it is neat solution without doing anything in ladder program.