Ideas

Parata Data, Analytics, and IoT Ideas

Add offending parameter to the MAX software error string

We see "Vial stuck in a vial feeder" errors and other similar errors, however, when you go to the error string, either in the Max Software or by using the DRM viewer, it never tells you what the offending parameter is.  For example, if I get a "Vial stuck in vial feeder", what tripped that error?  Was it that the stage sensors were expected to be above 75 to indicate that the vial was gone, or was it the drop sensor in the labeler that was supposed have a reading below 9 indicating the vial was present at the drop location? Can we put a line in the error string indicating "Drop sensor: expected value <9, actual value XX".  This could be done for all errors and it would be a big help with troubleshooting. 

  • Guest
  • Apr 3 2019
  • Will not implement
  • Attach files
  • Jenna May commented
    May 21, 2019 14:47

    this idea belongs in the Max idea portal. This portal is for IoT only.