Friday, November 11, 2016

Getting Started with the MangOH Green and Legato 16.07 on Ubuntu 16.04.1

IMAG1544-1.jpg

The MangOH Green is a board developed by Sierra Wireless to allow for easy development with their WP modules. These modules are specifically built for mobile/cellular IoT and have both cellular and GPS radios built into the chip. The MangOH Green runs a Linux application framework called Legato. Sierra Wireless has been working hard to keep the software moving forward. This has produced a number of versions each with subtle changes, and while there is a starter's guide for Legato that document has now become partially dated. This along with the relative newness of the manGO board and unique approach there is not a lot information to be found searching online, this however has been changing. As mangOH/legato becomes more popular the online content will also become more plentiful

With first hand experience as well as great help, from both the forums and mangOH personal,  in getting my MangOH board running I have decided to document the steps I followed to get the newest virtual machine version  “mangOH Dev using Legato 16.07 on Ubuntu 16.04.1” up and running.

The first thing to mention is the password for this version of the VM has been changed from “legato” to “mangoh”. While this has not been documented this was asked on the forums and has been answered. NOTE: This is only for 16.07 but moving forward the password will either be removed altogether or remain as “mangoh”.

The overall process follows a few basic steps each of which will be further explained below. The first step is to download and install the VM from mangOH. Then the firmware on the mangOH board should be updated. In the VM the environment variables are added to the batch file, the repository is updated, legato is updated and installed on the mangOH board. Finally the timerLed demo is compiled and installed on the mangOH board and the application is started. Each of these steps are explained in better detail in the steps below. It should be noted that steps 1 - 12 should only need to be done the first time the mangOH board is used. After the first time either 11 and 12 can be used or 13 - 15 can be used to add a new application to the mangOH board. Steps 16 - 19 always needs to be done to have the Legato application started on the mangOH board.

  1. Download VM from the mangOH site
  2. Attach the mangOH board to the PC and update the firmware
    1. Download the “Generic” Windows EXE file
    2. Double click the executable (run the file with the board attached to the PC)
    3. Follow the onscreen instructions (it may take some time). If the system hangs for more than 20 minutes do a power cycle on the board and restart.
2016-11-09 17_39_39-C__Users_Kas_AppData_Local_Temp_RarSFX0_fdt.exe.png

  1. Install the VM
    1. Follow the step #4 “Prepare your computer for Legato development” in either - “mangOH Fundamentals— Windows (Linux VM) + Legato CLI
These PDFs can be found under “getting started” on at the mangOH site

In the VM
  1. Open the VM and add  “source ~/legato/packages/legato.sdk.latest/resources/configlegatoenv” to .bashrc file
    1. Open a terminal window
    2. $edit .bashrc
    3. Scroll down to the bottom of the press the “insert” key on your keyboard
    4. Add the “source…” line at the very bottom of the file (after the last “fi”)
    5. Lastly enter “:wq” this will save and exit the editor
(Note: Moving forward to to Legato 16.10 this step will no longer be needed)
2016-11-09 20_15_56-mangOH Dev using Legato 16.07 on Ubuntu 16.04.1_1-Test [Running] - Oracle VM Vir.png

  1. cd mangOH/
  2. repo sync
2016-11-09 23_33_58-mangOH Dev using Legato 16.07 on Ubuntu 16.04.1_1-Test [Running] - Oracle VM Vir.png

  1. cd legato/
  2. source ~/legato/packages/legato.sdk.latest/resources/configlegatoenv
(This step is not needed if close and then reopen the terminal)
  1. make wp85
2016-11-09 23_24_00-mangOH Dev using Legato 16.07 on Ubuntu 16.04.1_1-Test [Running] - Oracle VM Vir.png

  1. Add timerLed.adef to mangoh.sdef
    1. Open emacs
    2. file->Open file
    3. mangOH->mangOH->mangoh.sdef
    4. Under “apps:{“ add “$MANGOH_ROOT/samples/tutorials/hardwareInterfaces/gpio/timerLed.adef”
    5. Save and close emacs
2016-11-09 21_07_34-Program Manager.png



  1. instlegato wp85 192.168.2.2
2016-11-09 23_27_47-mangOH Dev using Legato 16.07 on Ubuntu 16.04.1_1-Test [Running] - Oracle VM Vir.png

  1. cd mangOh/mangOH/samples/tutorials/hardwareInterfaces/gpio/TimerLed/
  2. mkapp -t wp85 timerLed.adef
2016-11-09 23_30_20-mangOH Dev using Legato 16.07 on Ubuntu 16.04.1_1-Test [Running] - Oracle VM Vir.png

  1. app install timerLed.wp85.update 192.168.2.2
2016-11-09 23_32_00-mangOH Dev using Legato 16.07 on Ubuntu 16.04.1_1-Test [Running] - Oracle VM Vir.png

  1. ssh root@192.168.2.2
  2. app status (should see “[stopped] timerLed”)
2016-11-09 23_18_10-mangOH Dev using Legato 16.07 on Ubuntu 16.04.1_1-Test [Running] - Oracle VM Vir.png

  1. app start timerLed
2016-11-09 23_20_48-mangOH Dev using Legato 16.07 on Ubuntu 16.04.1_1-Test [Running] - Oracle VM Vir.png

  1. You should now see the LED next to SW200 and the reset switch blinking

I have tested these steps out on a new install of the VM and have not encountered any issues. If you do have any issues or or have any comments regarding the process please share them in the comments below.

I would like to mention that the constant addition of new APIs for the mangOH board have made programing the board that much easier. As someone with a background in embedded code on microcontrollers, digging into the kernel to get to the GPIOs or other ports would be a quite a feat. The mangOH team is also working to add more demos, thi would allow someone wanting to create a prototype to have numerous starting points as well as projects that they could merge to get a usable prototype for the concept they are trying to display.

As I keep working with this board I will hopefully add more blogs giving over my experience with working with the mangOH Green board.


Friday, October 28, 2016

Keysight U1282A Digital Multimeter - Review and IP67 Rating

IMAG1342-1.jpg

I would like to thank Element14 and Keysight for selecting me to review the U1282A. Keysight, formerly Agilent Technologies, is a leader in electrical test equipment. While Keysight has been steadily expanding there multimeter offering, the U1282A is the newest in their lineup and first general purpose multimeter to be IP67 rated.

Unboxing and First Impressions

The U1282A comes nicely packaged as most of Keysights multimeters do. The overall presentation when opening the box for the first time is product built to be used hard and to last. The box comes with a built in divider to keep the multimeter separate from the accessories. The leads were neatly tied up in a ziplock bag unfortunately, there was no protection to cover their sharp points. The included test leads appear stiff and at the first chance I had, I swapped them out for a pair that came with my U1272A. Next to the leads was the IR-USB connector to allow for remote data logging as well a firmware upgrades. The inclusion of the IR-USB adapter is a much welcomed decision. As a good deal of problem solving is done over an extended duration being able to record data for that duration is a big help.

IMAG1331-1.jpg
Unboxing the Keysight U1282A

Neatly folded on top of both the multimeter and accessories was the “Quick Start Guide” and certificate of calibration. It should be noted that if you ever lose your certificate of calibration and want a copy, Keysight has all the calibration data for each multimeter by serial number.

Reason for Application

I applied for the this road test because of my ongoing work reviewing new products. In this capacity the environments and issues and very wide spread. Some products work in or around water, making the IP67 rating very useful. Other products are supposed to be low power and having a second meter that can perform logging allows for DC power to be easily monitored. Still others are connected to mains power and the ability to quickly determine if the system is live or not can greatly increase the level of safety.

After watching Keysight’s promotional videos demonstrating their IP67 compliance I felt they were weak and unconvincing. Because of this I was very much interested in doing my own real world and maybe slightly exaggerated testing.

 

Another function I was interested in to exploring  was the PWM output. During testing there are times a servo or other PWM controlled device that may appear to not work. Having a known good PWM output can save many hours of troubleshooting. I as therefore curious to see if the PWM from the U1282A could be used as a test PWM for servos.

The last major U1282A function I wanted to evaluate was the Vsense. This function allows you to determine if a wire is live without making an electrical connection. This has the potential to make tasks a lot safer provided it works correctly all the time. Seeing as the number of inline devices or those attached to the mians are also increasing this would help increase the safety during my tests.

I should mention that there was never any intention to look at the accuracy of the U1282A as this is something Keysight is known for. I have only ever heard of one case where a new meter performed incorrect measurements. While this meter did have a calibration certificate this was probably a once of occurrence. I’m also sure that the are others that have reviewed the U1282A and have better means to test the accuracy and repeatability of the meter.

Sand Test

The first issue I wanted to cover was the demo videos from Keysight. As previously mentioned they seemed weak and unconvincing regarding true reliability of the meter. While Keysight did cover the meter is sand there was no attempt to move the selector dial or engage the meter in any mechanical use until after the sand was removed. Also the meter was at one point wetted before covering it with sand trapping the sand on the exteriors of the meter. This has the added benefit of reducing any penetration of sand into the selector dial and the connector terminals.

In the mentioned video the sand was promptly washed off after each time the unit was exposed to sand. In a real world situation we do not get to choose the order the meter is exposed to sand and water or how much of each. Also a bucket of water is most likely not readily available to wash off the sand before the job is completed. Whether it is possible to clean the meter or not, it would still need to be used and function without issue. It should be noted that washing off the meter would render it inoperable until it is dry due to the input warning (leads in wrong input).

In the testing I conducted the meter was completely covered with beach sand. While this may be finer than some sand commonly found, this is with in the size specification for the IP rating. This grain size would also have the potential to be blown around by the wind and into the crevices of the meter making this a valid test. After being subjected to the sand the meter was than cleaned off. This included being brushed off,  washed off with a “hose” as well as rinsed in a bucket. The complete procedure, the meter being covered as well as washed off can be seen in the videos below.
.
IMAG0145.jpgIMAG0149.jpgIMAG0152.jpg

 

Immediately it can be heard that here is a decent amount of sand in the dial. Even with the background noise of the water and wind the grinding is unmistakable. The meter was then thoroughly washed off in a bucket of water as well as with a squirt gun.

 

The meter can unmistakably be heard being ground away by the sand stuck between the selector dial and the housing. While it may be considered slightly unfair to operate the selector dial while not completely cleaned from sand, this would most likely be done in a real situation. It should be noted that even with the wind in the background the sound is unmistakable. Also while the Keysight test appeared to show no sand in the dial after being washed off, this was clearly not the case here.

While this may seem like just an annoyance this could conceivably lead to product failure. Specifically this could lead to a breach of the housing allowing water or sand into the housing.This is clearly unacceptable for the IP67 standard, any interference with the satisfactory operation of the unit is considered an issue. The wearing away can be seen in the below picture. In this case the dial was rotated a few times (> 5) producing plastic filings around the AC volts and millivolts section of the dial.

IMAG0312.jpg

Unfortunately there were only two available solutions to remove the sand. Either send the unit back to Keysight for cleaning or void any calibration warranty and clean the meter myself. Thankfully Keysight took the issue seriously and decided to consider this an “out of the box defect”. In this case the unit was repaired under warranty. I would like to mention that while this issue was being addressed by Keysight internally there was little consensus as to the classification of this issue. The product manager as well as the local FAE appeared to agree that this level of damage to the product should not occur. In contrast the design and test team appeared to be of the opinion that the testing I performed was not valid and the unit behaved as it is designed to and in accordance with the IP67 rating.

I have checked with the respective team, and we found that it is an expected behavior that the sand may ingress between the rotary switch and the top case. However, the sand will not go inside PCA level of the meter. “

After asking for further clarification due to the grinding of the plastic I received only instructions on how to send the unit back. There was no further information on how the plastic would not be ground down potentially causing a hole in the casing.

Water Test

The water test conducted by Keysight was for the most part sufficient. The meter was submerged and shaken around allowing for water to flow all over the unit. It is true that the meter was not submerged for the required 30 minutes but that was less of a concern considering others have put the meter through that testing. Also with regard to the water tight seals on the unit I don't believe I could do a better test than that conducted by Dave Jones. In his test the meter was submerged, dropped and abused in a very wet and demanding environment. Through all the testing the meter continued to work as designed.

What I have done different than all other water tests to date was to submerge the unit with all input terminals plugged with a test probe. While this would normally not be done and it does sound the input warning alarm, it was done to keep the water out of the terminals. Something I have mentioned to a number of Keysight personal (sales reps, FAEs etc.) is that plugs should be included in the kit or at least be available. The reason is that although the unit is waterproof the input warning will sound until the inputs are fully dry. While the IP67 rating ensures I will not damage my meter if it falls in water or gets wet my testing will be on hold for ~45 minutes or more until the probe terminals are completely dry. Keysight does ship their meters with dust plugs for the test leads and probes, which are sealed when in the field. in contrast to this, there are always at least 2 terminals left open to the elements for dust and water to get in, something is not making sense in this decision.

IMAG1283.jpg
IMAG1284.jpg
IMAG1290.jpgIMAG1288.jpg
U1282A with all terminals capped while the meter is submerged

Test and Results

After inserting a lead into each of the 5 terminals the unit was submerged and splashed around a bit. The unit was turned on, the selector switch was rotated. While the unit was on the input warning sounded as expected. Once the water portion was complete the unit was taken out of the bucked and an air hose was used to dry the area around the leads.

When the extra two leads were removed the input warning did not sound. This was tested in all three variations. That is in volts, milliamps and amps mode, in all cases when the leads were inserted correctly the alarm did not sound. This furthers my question why Keysight does not include plugs with the unit for those doing testing in a wet environment.

Customer service

As mentioned above testing the unit in a sandy environment resulted in the selector dial becoming contaminated with grit. Since this was a road test Keysight was looking to keep things as positive as possible. Also because the issue was reported within 30 days of receiving the unit they decided to treat it as an out of box defect.

Unfortunately the process for taking care of this was a little bit convoluted and complex. While I was offered upfront to have the unit repaired I was hoping to get more info on the IP67 rating. This additional information never did come and there is still no clarification on what he unit should or should not be able to handle.

Experience with the return

Part of the reason for such a delay in this review has to do with the repair customer service. The amount of time it took to contact the product manager or anyone that could/would seriously help me was pretty extended. The product manager then needed to contact Malaysia and as well as the design team. Eventually I was informed Keysight would cover all cost in having the unit repaired. I was graciously offered to have the unit picked up from wherever was convenient for me, at home of from the office did not matter. In order to speed up the process I had it picked up from my home as this was closer to the sales representative and would allow for faster pick up.

While the unit was picked up the same day that I was contacted by the local office the whole process in having the unit repaired took substantially longer. I the unit wa shipped back to Malaysia where it was disassembled and cleaned. Then the unit was shipped back to the local office and than to me. In all the process took 6 weeks and 5 days (June 23 - August 9). For a piece of test gear that I would potentially use daily on the job, being without it for almost 7 weeks is unacceptable.

PWM Control (Servo Control)

Having a known valid PWM output is very handy especially when testing parts sent to you for evaluation. As a product tester/evaluator I test various products and devices. One of my recent projects was a robotic hand with 6 DoF. Unfortunately there was an issue with the servos not working as they should. Using the U1282A as a calibrated and valid PWM source made it a simple matter to test whether the issue was the servo or the controller.  

For this setup a 5V supply was connected to the power and ground leads on the servo. The U1282A was connected to the signal line and ground. The servo responded as expected it should with a valid PWM signal. This demonstrated the ease with which a PWM device could be debugged with the meter.

Video of meter controlling servo and scope showing changes of width

Since some servos still demonstrated some issues, the PWM output was connected to a oscilloscope. This again verified that the output appeared to be correct. The U1282A was also connected to a U1272A which has a frequency counter as well as a PWM deconstructor. This outputs the duty cycle as well as the period. Sadly the numbers displayed by the two meters had a significant discrepancy. After mentioning this to Keysight I was informed the U1272A needed a factory reset (not sure how this affects measurements but… ). This sadly did nothing to help remove the discrepancy.

Video of meters showing different numbers

VSense

The last major function of this meter that I was intrigued by was the VSense. This functionality allows you to test if a AC wire is live without needing to make contact. When working with live mains this is a major benefit. From testing inline IoT devices to troubleshooting a water heater this can seriously save you.

Before I got a chance to really test this functionality I found that my water heater was not behaving correctly. As part of the troubleshooting I wanted to be sure the heater was powered. When measuring the voltage between what appeared to be the two terminals a very low voltage was observed (~ 1V). Thankfully before working with anything I tested the circuit with the VSense and found there was still something live. On further inspection only one breaker was fully tripped. The second pole was still connected and was thus allowing something to creep through. I may not be 100% how I measured ~1V while the system was live but I am sure that without VSense things could have gone a lot worse.

I would like to mention that getting the VSense to behave predictably takes some time. When doing some of my further testing I found that there is a need to move the meter around slowly. This is because the sense location does not appear to always register in the same location. Also there are times you will need to change between high sensitivity and low sensitivity to be sure you are measuring the correct wire. Overall though the functionality is very useful and beneficial.

Recording Measurements

Another feature I wanted to look at, indirectly linked to the meter was the ability to log data remotely. Although this is not unique to the U1282A, the U1282A does put an emphasis on data logging. I have used previous iterations of Keysights data logging software with my U1272A with mixed results. While the update was relatively reliable things got worse when trying to log data. There were often times a value or multiple values were missed. Also, in previous iterations only one meter could be used at a time necessitating opening multiple logging windows. Having multiple windows compounded with missing data made the post processing very messy and and difficult to get usable and meaningful data.

In the newest version all these issues appear to have been taken care of. You can now connect to and log from up to 9 meters at the same time. There is also an easy way to either view the history of the data as a graph or as a meter display. The export function also works better than before, giving more options. Like Tektronix, Keysight appears to be realizing that good and easy to use software can be just as important as good hardware.
2016-10-05 16_01_01-.png
Keysight PC based remote logging software logging from two meters

2016-10-05 15_54_41-Keysight Handheld Meter Logger Software-1.png2016-10-05 15_54_18-Keysight Handheld Meter Logger Software-1.png
The profiles of the connected meters as well as information on how they are connected

Conclusion

Overall this is a solid meter that as most if not all Keysight meters do, delivers good quality and is easy to use. Unfortunately from the IP67 rating as demonstrated by Keysight there is room for improvement or clarification. Most importantly the customer service experience needs a lot of help. Waiting 7 weeks to have a meter repaired is unacceptable.

If someone is looking for a meter that is reliable and delivers sound measurements, than any Keysight meter will do. The chances are someone would be choosing the U1282A for its IP67 rating. In that case I would differentiate between the IP6x and the IPx7. From the testing conducted by Dave Jones on the EEVBlog as well as my own basic testing I would say the U1282A is waterproof without an issue. Any environment that contains moisture or water the U1282A would work well in provided the unused terminals are covered. However, regarding the dust proof rating there are issues. The meter definitely has the ability to fail and the lack of clarification from within Keysight on what the meter should be able to withstand is also an issue. Lastly when the promotional video for Keysights version of IP6x involves covering the unit in sand, there should be no negative effects in doing so.

Based on these conclusions, for a wet environment I would recomend the U1282A but I would like to see Keysight add terminal dust caps to prevent water rendering the unit useless until completely dry. Unfortunately if the intended use is in an environment that contains fine grit sand (beach or desert sand) I don’t belive the U1282A will deliver what Keysight wants you to believe it will.

Update

This is a response from Keysight in relation to the delay I experienced in having the unit serviced: The repair delay you experienced wasn’t representative of typical handheld repair. Normally you’d call in, ship the unit to our local service center, it would be exchanged and you get a new one back. Due to your IP67 questions and concerns, your unit was picked up by me, returned to the factory in Malaysia, analyzed, repaired and returned which was not the normal process.  We took your feedback very serious.

Original post on Element14 can be found here