MI values are not saved and when the V560 starts with very high values. Visilogic.

[VictorUA]

Hello everyone. I am using V560 and visilogic V9.8.96 BUILD 0 and I have a problem the MI values in the HMI are not saved and when I reset the power on the V560 it starts with very high values. As for the ML values, they are saved without a problem, even when I reprogram the V560, they are still maintained. What can be?

 

 

Thank you.

[kratmel]

Please try to Find MI3 in your program. You can see possible overwrite this MI in other part of program.

[Cam]

Hi Victor,

 

You have a power up value set for MI 3 of 30   when ever the PLC goes through a power up cycle MI 30 will be set to 30 regardless of the value that was in that MI when power was removed.

 

The check box to the right of the DEC drop down is controlling this.  If you don't want a power up value remove the check mark in the box.

[VictorUA]

Thanks for your prompt responses. But the problem is that it did not go to 30 but to full range, that is, more than 10000. I solved the problem by disabling this:

 

Thanks,

Victor.

[kratmel]

Is it MI3 present in this Data Table Read Row PARAMETER function ?

[Ausman]

Victor, this appears to be a classic mistake where you want instant results of correct reads from your system on boot.  In most instances you need to build into your programming a delay after boot before the PLC starts acting on anything.  The delay time must be matched to the maximum time it takes for all your external sensors to stabilise, and also to a lesser extent the various digital and analogue inputs of the PLC itself depending on your HW configuration.  Also, if you have value averaging set up in the PLC, then this needs to be allowed for as well.

cheers, Aus

[VictorUA]

15 hours ago, kratmel said:

Is it MI3 present in this Data Table Read Row PARAMETER function ?

Yes, this is in the Data table.

[VictorUA]

11 hours ago, Ausman said:

Victor, this appears to be a classic mistake where you want instant results of correct reads from your system on boot.  In most instances you need to build into your programming a delay after boot before the PLC starts acting on anything.  The delay time must be matched to the maximum time it takes for all your external sensors to stabilise, and also to a lesser extent the various digital and analogue inputs of the PLC itself depending on your HW configuration.  Also, if you have value averaging set up in the PLC, then this needs to be allowed for as well.

cheers, Aus

  Thanks, what you say makes sense. For now I plan to leave it without loading this Data Table. Since I want the configuration to be set from the HMI to be saved.