Micromotion Smart Meter Verification Questions

I have started to implement Micromotion Meter Verification on most new meters at several of my sites.  I have a couple questions about the snap-on.

 

1.  Is there a way to see in AMS Device Manager if a Micromotion flow meter has the meter verification functionality enabled on the meter?  The only way I have found to date is to go into each flow meter and see if the snap-on works.  This takes about five minutes for each meter.  This time adds up when you have to go through a large number of meters.  The fact that I have to keep reconfiguring scheduler (question #2 below), I am doing this repeatedly.

 

2.  My second question is with the meter verification scheduler.  Every time my PC that has the scheduler running re-boots or someone closes out the meter verification snap-on, I have to re-configure the scheduler.  Is there a way the scheduler configuration can be saved so I do not have to always reconfigure?

 

3.  Third, can the meter verification scheduler be run as a service so it will automatically restart on reboots?  With monthly security updates being installed on the machine, the scheduler needs to be restarted each month after a reboot.

 

Regards,

Rob Sentz

 

  • Hi Rob,  

    Thank you very much for your questions.  Please see my responses below:

    1: There is a better way to see if the SMV feature is enabled.  If a device has Meter Verification enabled, there will be a Meter Verification button displayed in the Shortcuts group box on the Overview screen as shown in the image below:

      

    2: It sounds like there may be something wrong with your installation that is causing it to not work properly. The scheduler portion of the SNAP-ON is designed to be configured and to retain that configuration for all future uses. We have realized that there are a few issues with the scheduler and we are getting these issues resolved in version 3.1, which is in its final round of testing and bug fixes. You may want to wait until we have SNAP-ON v3.1 ready before updating from an older v2.x SNAP-ON or trying to troubleshoot. The reason is SNAP-ON v2.4 disturbs the Windows registry when it is uninstalled, breaking AMS. Leave the older SNAP-ON alone until the fix is fielded in SNAP-ON v3.1.

    3: We apologize but this is a known issue and something we are working on with the SNAP-ON v3.1 fix. We will soon have SMV SNAP-ON v3.1 ready for release

    Please let me know if you would like some more elaboration on these responses and I would be happy to help!

    Best Regards,

    Tim