• Author Author: mcb1
  • Date Created: Date Created
  • Views 2152 views
  • Likes 5 likes
  • Comments 11 comments
Related
Recommended

U1282A Road Test Part 2 (PC Software)

mcb1

This blog continues from my original review here  RoadTest the Keysight U1282A Digital Multimeter - Review

 

 

 

Following some testing using an Android Tablet and Bluetooth connection, I thought I'd see what the PC software offers.

 

Keysight Handheld Meter Logger ver_3_1_51130_01

While the Android version downloads and installs and just works, the PC version has a few issues.

 

1.     The install gives you (the PC Owner) no control over where it will be installed.

          I have a 64bit Win7 machine and yet it gets dumped into C:\ProgramFiles.

 

2.    Despite being an Administrator, it went throught the program and then the install spat the dummy with this error.

           image

     So start again and then right click and select "Run as Admin" to prevent this error.

     I've seen this behaviour before and I'm blaming Microsoft, but I'm sure it's not all their doing.

 

     I did also note the odd Agilent label on some files.

     It's been a while since keysight aquired the Agilent label, and this software has migrated with at least one upgrade, so perhaps it's time to check the naming on the install files.

 

 

3.     I captured some data using the Android App and decided that they should be able to be imported into the PC version.

          ( https://www.element14.com/community/community/applications/industrial-automation/blog/2016/05/16/keysight-u1282a-vehicle…  )

          On the tablet, I backed up the database and then transferred the file across to the PC directory where I keep all the info relating to challenges/Road Tests, etc.

    

          When you go to look for the files the default location is the users documents, and despite the ability to select a directory, you can't save it.

          There are three tabs and for each one you have to go through the point and click to select the directory.

          Most windows File open Dialogue boxes allow you type the path or cut and paste into it, but not this software.

 

          So eventually I gave up and dumped the copy into the directory it wanted, BUT it won't recognise it.!!!!

          Surely it can't be too hard to add this into the settings menu and let the user save the directory he wants to use.

 

 

4.     The Logging directory has to be under the Users Documents. You have no ability to point it to a shared drive, or anywhere else.

          image

     By now I'm starting to tire of software that is well down the version list just not being friendly to it's users.

 

 

5.     I accidently clicked on the Reports tab and it provided some piccys then a windows error sound caught my attention (luckily the sound was on).

          This error dialogue was in the background.

          image

          I didn't want a newer version so I clicked No .... guess it didn't like that because it responded with some more error boxes.

 

imageimage

          and then it cried enough ... image

 

          So my foray into the world of KeysightHandheldMeterLogger_3_1_51130_01 ended and I'm not impressed!

 

 

I've used an earlier version with the Insulation Resistance Tester but I didn't try the import function.

At this point in time I'm going to uninstall ver 3.15 xx and install an earlier version to see if I can get around some of these issues.

I suspect it will be similar for the directories, but who knows.

 

 

 

Impressions

Overall the look of the software is pixelated/soft as if it really doesn't belong on a large PC screen.

I was so looking forward to importing the data captured yesterday and then having a closer look at it.

 

Yes you can export/save the data as a CSV but can you bring it back into the software?

What if you need to send a tech into the field to capture the data, but need to analyse it somewhere else?.

It may be that the Tech focused on one part and missed another part of the capture that is more relevant.

 

The other minor point was that the temperature of the meter is promonently displayed in the upper right corner.

None of the data saves I have done captured that information, yet the calibration is based upon 23 degC at 80% humidity.

Surely it makes sense to capture that information as well.

 

The features of this meter to Engineers is the Logging abilities, yet IMO the software is letting that down.

Sure the Android App and bluetooth connectivity makes it extremely versatile, but capturing the data is only part of the equation.

 

I'm stuck with how do I mark the review

image

Does the Logging software fall into "Support materials", or "Demo Software"?

 

I decided to mark down the Support materials since the meter itself works.

Because the Android App works, I have only marked it down to 8.

The PC version works but needs some work, so I think this is a fair score.

 

If someone from Keysight wants to make contact, I'm happy to discuss some options and take a much closer look.

These meters deserve to have the software match their capabilities.

 

Mark

  • in reply to mcb1

    "Software should be written to capture each error and act accordingly"

    I would argue that it has done.

     

    It displayed enough information for a help desk to identify the problem and for a software engineer to determine what is wrong, the a manager to make a commercial decision if the code needs enhancing. What you describe as horrid error messages, I would say is a useful series that allows us to diagnose the problem. Pretty errors are fine but make the software engineers job harder.

     

    Without knowing the code, I can tell you it is trying to save then open a Word document, the coder likely checked to see if Office was installed and then tried to save the document. They will have likely tested it with the current and previous versions of office. Your setup is MSWorks which probably has a whole different set of error messages and failure modes. For example that choice dialogue is not actually in the Keysight code, it's MSWorks.

     

    Unlike embedded code or safety critical code, desktop applications can rarely know their environment or all possible error states. If they did, you probably could not afford it. The best we can do is test on the mainstream options. This is why the likes of MS want us to upgrade, supporting multiple platforms and versions is costing us all.

  • in reply to Workshopshed

    It's always challenging  ... the user deliberately chooses to ignore the "required" message.

    No I chose one of the two options.

    BUT that is a copout and IMO lazy programming.

    Software should be written to capture each error and act accordingly.

     

    It did have multiple other report options showing and at worst the software should just say "sorry no report options available", rather than throw it's toys out the cot and terminate.

     

    Mark

  • Good job Mark,

     

    You got a  lot further than I would have.

    My current frustration levels are very low and I have little tolerance for idiot error messages.

     

    DAB

  • It's always challenging when you are writing software that uses 3rd party tools when generating reports and then the user deliberately chooses to ignore the "required" message.

  • in reply to michaelkellett

    I never rate anything with a 10

    To be fair the category wasn't really appropriate to the Meter ... so I sort of ignored it.

     

    They have published the software commands to talk directly to the meter, so your approach would work.

     

     

    i wonder if this is in some ways more about the slow motion failure of Windows in the technical computing area.

    I'm not sure you can blame Microsoft for this.

    I've installed other software and not had the same issues as this installer did. It could be they are using the Installer and it has the issues.

    However you cannot blame MS for the throwing the toys out the cot when it couldn't get it's way with a report ... simply tell the user and move on.

     

    The other aspects aren't really MS's fault either, these are software features (or lack of) but could be a hangover from Agilent.

     

    From what I hear they are approachable so maybe there may be an opportunity to right the wrongs ... we'll have to see.

    Mark