Year: 2014

  • Agilent U1253A with LabView

    Agilent’s U-Series Multimeters have the ability to be talked to via an infrared interface (and some of them even feature an OLED display), either through Agilent Keysight’s slightly overpriced USB-To-IR Adapter, or by building your own. If you intent to follow the latter path, be sure to read Josip Medved’s Info about the Adapter; it covers pretty much everything you need. There’s also a YouTube-Video with a more sophisticated (and probably oversized) approach.

    LabView

    With the communication working (you might test it with Keysight’s own logging-tool), it’s probably more interesting to be able to control the device using LabView. Unfortunately, I could not find any libraries, and the documentation is limited to a post on Philipp Klaus’ blog describing the basic command set.

    Screenshot of a sample program
    A sample program constantly reading the meter’s data

    In short, the Device features 2.5 “channels”, or let’s call them data-streams; it is capable of e.g. measuring voltage and frequency of an AC source simultaneously and can additionally report the current ambient temperature; although that feature might not be of so much use. In principle, to continuously read out the data measured by the multimeter, you might want to query it’s current setting (unit, range, precision), it’s value or status (like auto-range, position of the rotary switch etc.).

    Command Set

    To find out how to talk to the device, and how to interpret it’s response, I used a Serial Analyzer in conjunction with the original software. The result is a LabView-Library that’s capable of handling a reasonable part of all passive commands (no controlling of the device so far only limited support for configuring the device so far) – the lib, however, should be considered in alpha-state and might still contain bugs. Every command sent from the computer should be terminated by a single linefeed (0x0A, “\n” etc.); the device itself terminates with carriage return and linefeed. On error, the device will return “*E\r\n”. Most of the time, the meter acts as passive command-responder, except when the user turns the rotary-switch – in that case, the device sends the switch position counting from 0 (and excluding the “off” state – which means you won’t be able to detect a “switch-off” event except with a communication timeout) preceded by a star, i.e. “*1\r\n” for Volt.

    The commands I saw on the line include:

    CommandMeaning
    *CLSallways sent to the device on the beginning of a command set. Probably resets the last read-command
    *RSTsaid to reset the meter, up to now I didn’t see any actual change in behavior
    *IDN?Request identification of the meter. Result is a string devided into 4 parts by commas, i.e.
    “Agilent Technologies,U1253A,MY12345678,V1.01”, reading the company’s name, the model- and serial number and it’s firmware version
    STAT?Returns the current device status. I could only identify two parameters so far.

    Sample:
    “000000I00012L00204001”
    (Character 17, 2 in this case, indicates the current position of the rotary switch, whereas the last digit is set to 1 when AUTO-range is enabled)
    CONF? (or)
    CONF? @#
    Request the current configuration (for channel @#) of the meter, see the next section
    FETC? (or)
    FETC? @#
    “Fetch” either the 1st display/stream/channel (or however you’d like to call it) or request a specific one (i.e. “FETC? @2” for the auxiliary reading, i.e. the frequency of an A/C voltage)

    The meter always returns a single floating point number.
    READ?Return the current meter reading, only applies to the 1st channel/stream/dataset…
    SYST:BATT?Get the meter’s battery status, returns a single floating point value in %/fully charged.

    Read configuration options

    Following a “CONF?”, the device answers with it’s current setting (i.e. voltage or frequency) and a few parameters. To request the configuration of a specific “channel”, send “CONF? @#” replacing the # with a number from 0 to 2. The type of voltage or current, or any subtype of measurement is appended to the basic setting with a semicolon. Additional parameters are separated from this basic information with a space, again separated by commas. Example: “VOLT:ACDC +1.00000000E+00,+1.00000000E-04” denotes an AC/DC voltage-measurement with a range of 1 Volt an a maximum resolution of 0.1 mV. The following table will give some more detailed information:

    OptionMeaning
    VOLT(:type)The channel will return a voltage. When configured for DC voltage, it’s just “VOLT”. For AC, AC/DC or DB(V/M) measurements, the corresponding option follows with a semicolon, i.e. “VOLT:ACDC”.

    Additional parameters are the measurement rage in Volts and the value for the last (4th) digit (i.e. the precision). These parameters will not be returned for dBV or dBM measurements.
    CURR(:type)Current measurement. Again, DC is the default without a semicolon, AC and ACDC are reported seperately.

    For the mA/A measurement range, there’s an additional measurement mode displaying the current as a percentage between 0 mA/4 mA and 20 mA, the corresponding return value is “CPER:4-20mA” or “CPER:40-20mA”.

    Parameters are range and precision.
    RESResistance, parameters are again range and precision.
    CONDConductance measurement, parameters are range and precision.
    DIODDiode measurement, this setting doesn’t seem to return any range or precision.
    CAPCapacitance, parameters as for VOLT or CURR.
    CPER:(range)“Percentage Scale”. Probably made for adjustment measurements, displays a percentage of the measured current in the range of [4..20] mA or [0..20] mA. The range is given after the semicolon, i.e. “CPER:4-20mA”. Additional parameters like for CURR.
    FREQFrequency in Hz, parameters are again range and precision. So far only seen for the second channel.
    PRESThe value of the frequency counter (channel 1). Does not return any reasonable range, only one parameter: 1 for direct counting, and 100 for a prescaler (divider) or 100.
    PULS:(type)Pulse-Width measurement. Might return either a percentage of high-value to low-value (“PULS:POUT”) or the pulse width directly (“PULS:PWID”). Ranges will show the values of the voltage measurement.
    TEMP:(type) (unit)Temperature measurement, the only supported setting for the third channel.

    Type might be either “K” or “J”, depending on the configured type of the thermocouple – or “ENV” denoting the meter’s environment measurement (channel 3).

    The only parameter is the unit, either “CEL” for Celsius or “FAR” for Fahrenheit.
    CONTContinuity measurement, similar to RES but with (if configured) audible tone on contact
    *EError, i.e. an unused channel.

    Send configuration

    Different “layers” of functionality for specific switch-positions can also be selected via Software. The device accepts two lines of configuration options after a “CLS*” command (I didn’t test it without), the possible options depend on the position of the rotary switch. An erroneous command will be acknowledged by “*E”, the configuration, however, might still be partially applied and might lead to instable operation (i.e. incomplete or overlapping data on the display). Success in changing the configuration will not trigger any response. Note that, upon selecting additional (calculated) quantities, those might become the primary reading; selecting AC-Voltage and Frequency for example will change the first channel to frequency, and reports the voltage on the second channel.

    Each switch position allows a different set of options, as can be seen in the following table:

    Rotary SwitchCommandMeaning
    0 (V/AC)
    1 (Volt)
    2 (mVolt)
    CONF:VOLT{:AC,:DC,:ACDC} (range)Change the range of the AC voltage measured, possible parameters are 5, 50, 500 and 1000 (Volt each) or 0.1, 0.5 and 1 (also Volt, valid for position 2). Omit the range parameter to enable auto-range.

    Parameters AC, DC and ACDC are only valid for switch-positions 1 and 2.
    CONF:FREQMeasure the frequency additionally to the voltage, it will become the primary reading. Auto-range only.
    CONF:PULS:(type)Measure pulse-width (primary). Possible types are PDUT/NDUT (positive/negative edged dutycycle in %) or PWID/NWID (positive/negative edged step-width in ms)
    CALC:FUNC {DBV,DBM}Set the primary channel to read calculated dB/V or dB/M values
    3 (Resistance)CONF:RES (range)Configure the resistance measurement; ranges are none (auto), 500, 5k, 50k, 500k, 5M, 50M or 500M (Ohms each of course).
    CONF:CONDMeasure conductance, only one range is supported and may not be configured (500 nS)
    CONF:CONT (range)Measure continuity; accepts the same ranges like CONF:RES
    4 (Diode)CONF:DIODStandard, set to Diode-measurement. Range is fixed to 2.1 V
    CONF:FCOU (range)Select the frequency counter function. Range is either 1 for direct counting, or 100 to select a prescaler of 1/100 to measure frequencies of up to 20 MHz
    5 (Capacitance)CONF:CAP (range)Set the range of the capacitance measurement, either none (Auto) or 10n, 100n, 1000n, 10u, 100u, 1000u, 10m or 100m (Farad each).
    CONF:TEMP (type),(unit)Switch to temperature measurement. Type is either K or J for {K/J}-Type thermocouples. Unit is either FAR-enheit or CEL-sius.
    SYST:TCOM (0, 1)Enable / Disable 0° compensation
    6 (µA)
    7 (mA/A)
    CONF:CURR{:AC,:DC,:ACDC} (range)Set the current measurement to DC, AC or AC/DC measurement and configure the range to autorange (none) or 500u, 5000u (µA) for position 6 (µA) or 0.05, 0.5 (A) for Position 7.
    CONF:CURR:PERCDisplay the measured current as a percentage – no direct range parameter!
    SYST:CPER (range)Configure the range of the Percentage Scale measurement – either “0-20” or “4-20” (mA each).
    for Additional parameters see Positions 0 to 2!
    (possibly) AllSYST:TENV (0, 1)Enable / Disable measurement of the environment temperature, will be readable on channel 3

    A few VIs exist already to configure the device using the above commands.

    Update: Configure PWM Output

    The last available switch-position (#8) will allow you to operate a PWM output with 3 Volts/peak and an instrumental precicion of 1/256 of the frequency set. The device features three commands to program the PWM output. “CQU:FREQ X” sets the output frequency to X, possible options can be taken from the manual and range from 0.5 Hz to 4.8 kHz. The pulse width can be controlled from 0.39 % to 99.609 % / total, given in values from 1 to 255. The device has two commands to set the pulse width, “CQU:PWID X” will program the pulse width and display the value in ms, where as “CQU:DCYC X” will display the duty cycle in %.

    Code

    The code including the sample program can be found on bitbucket.

  • Samba, smb.conf und Zeichensätze

    Schon mal den Fehler gemacht, die smb.conf mit einer grafischen Benutzeroberläche zu bearbeiten? Nein?

    Hier wäre das Resultat:

    Samba-Fehler

    Grund: die GUI (hier DrakSamba, z.B. in Mageia verwendet) verwendete einen anderen Zeichensatz als vorgesehen. Samba und Windows kommen mit Umlauten in UTF-8 mittlerweile ganz gut klar, DrakSamba setzte das “ü” in ISO 8859 Latin 1 (Codepoint $FC).

    Lösung: Auf der Kommandozeile bearbeiten, richtiges Encoding wählen und funktioniert!

     

  • Windows NT 4 in VMWare Player

    Manchmal braucht man eben auch alte Krücken noch, in diesem Fall Windows NT4. Glücklicherweise bringt VMWare die nötigen Treiber von Haus aus mit, und Windows NT4 hat die LSI Logic SCSI Treiber auch schon. Windows NT Workstation unterstützt bis zu 2 CPUs (obwohl VMWare etwas anderes behauptet), diese werden aber meist nicht benötigt und bringen unter Umständen (durch den Multiprozessor-Kernel) mehr Probleme als Nutzen. Die Standardeinstellung von 256MB RAM ist ausreichend, Windows NT ist mit 512 MB RAM mehr als zufrieden.
    Übrigens: wie man bei Windows NT zwei Kernel-Varianten (Multi- und Uniprozessor-Kernel) installiert, steht in der KB von VMWare.

    Ein paar Schwierigkeiten gibt es dennoch. Windows NT4 bringt normalerweise den Internet Explorer 2.0 mit. Schönes altes Ding, so ziemlich keine einzige aktuelle Website lässt sich überhaupt noch anzeigen, sehr oft antworten noch nicht mal mehr die Webserver auf seine veralteten Anfragen. Da aber sowieso die meiste noch existierende Software das Servicepack 6a voraussetzt, sollte man das auch gleich installieren.

    Wie so ziemlich alle Windows NT 4-Updates gibt es SP6a auf den Seiten des Rechenzentrums der Uni Regensburg zum download. Nach der Installation des Service Packs sollte gleich der IE6 installiert werden, den gibt’s bei WinFuture. Eine ebenso fast unerschöpfliche Quelle ist der “Windows NT 4 Webplace“.

    VMWare bringt mit seinen VMWare-Tools Grafik, Sound und Maustreiber mit. Leider funktioniert die Installation des Maustreibers nicht – dieser kann aber leicht per Hand installiert werden. 7Zip hilft dabei, das läuft auch in der neuesten Version noch auf Windows NT 4. Auf der VMWare-Tools CD wird die Installations-MSI extrahiert, darin gibt es die Maustreiber für Windows NT:

    vmmouse

    Die Dateien “vmmouse.infNTen” und “vmmouse.sysNTen” müssen jeweils mit ihrer natürlich Endung versehen werden, danach kann man in der Systemsteuerung den passenden Maustreiber installieren.

    Wer USB-Unterstützung in seiner VM haben möchte: leider scheint Woodhead’s USB-Stack (mit USB EHCI) nicht mehr zu funktionieren (angeblich hat er das mal in VMWare). Es gibt allerdings noch eine andere Möglichkeit (Nur UHCI, muss in den Einstellungen der VM auch aus USB1.1 angegeben sein!), die funktioniert. Übrigens ist es sinnvoll, auch den FAT32-Treiber zu installieren.

    Für Sound: VMWare emuliert eine Creative Ensonic PCI128. Treiber gibt’s im Netz, z.B. hier.

  • Fairphone with or without Google’s Apps

    Yep, a brand new Fairphone! One of the probably most notable differences of the “Fairphone OS” to any stock Android is, that it does not include, by default, all these little Google thingies like the Play Store, GMail, the Location Service etc.! On the other hand, Fairphone did provide a way to install that crap by downloading an approximately 100 MB sized file from some “secured source”. Fair enough.

    InstallGoogleApps
    The “Install Google Apps” widget is by default on the home screen

    Two things to check here. First, where does this download come from and second: how can I control what’s being installed, e.g. to install the Play Store and it’s bare essential dependencies, and nothing else; maybe to exchange some of the frameworks by the great replacements from the NOGAPPS project?

    By the way, there’s a really great thread about the Fairphone and it’s Hard- & Software on the XDA-Developers Forum.

    Where does this come from?

    First of all, I wanted to know where the files get downloaded. A quick search didn’t give satisfactory results. But, there’s a Firmware recovery image available for download. Looking at the APKs residing in /system/apps of that image (which saves quite some time compared to pulling that from the actual device) it is easily discoverable that this “Install Google Apps” widget belongs to FairPhoneHome.apk. The two great tools APKTool and SMALI ease up the digging a lot,  and in the end there’s the App’s string-resource XML-File that reveals the download location of the first step:

    <string name="gapps_installer_download_url">http://www.fairphone.com/externalcontent/fp_ga.zip</string>
    <string name="gapps_installer_config_file">fairphonegapps</string>
    <string name="gapps_installer_zip">.zip</string>
    <string name="gapps_installer_cfg">.cfg</string>

    fp_ga.zip contains two files, fairphonegapps.cfg and fairphonegapps.sig. fairphonegapps.sig seams to be the signature signed with the private key that belongs to the public key in FairPhoneHome.apk’s resources. Being no crypto expert, it’s not easy to tell whether this approach is secure, but a short look at the disassembly and some testing did not reveal any easy way to replace fairphonegapps.cfg.

    This file however, contains the link to the “real” GApps archive, together with it’s MD5-Hash.

    http://www.hightail.com/e?phi_action=app/directDownload&fl=SWhZekZucHZsamVFTmVLWHo4b01Eak9yZWt5UmdteDRsUjJuWENHRzVZbz0
    64c3df86f20ab9b557fd3e4fc781633f

    Well, let’s download that and have a look.

    How to change the apps being installed?

    The Archive contains the usual set of object files and bundles etc. needed to install the Google Apps. Is copied to the /system volume, the phone will “install” them on the next reboot. The installer contains some hardcoded filenames and desinations, it’s automatically issue the needed remount-command to make /system writable and does all the copying for us. As it’s inconvenient to try to replace the file being downloaded, let’s just install everything we want our own.

    The Android-SDK contains a nifty tool called “adb” that allows to connect to the underlying linux-shell of any android phone, given USB-Debugging is active and USB is set up correctly. On Windows, the right drivers will have to be installed (you might want to change “My HTC” in the driver to “Fairphone” for device id 0x0C03 if you don’t mind installing unsigned drivers). On Linux, you’ll need to modify the udev rules to include HTCs vendor ID, 0xBB4.

    Then it’s quite easy to modify the apps installed. I removed everything except the Google Play Services, it’s dependencies (Text to Speech) and the initialization app. All these have to be copied to the internal storage “SDCard”, for example into the folder “apps-install”. After that, start the terminal by issuing “adb shell”, then become root and copy the files over. This of course only works if the /system filesystem has been re-mounted writable:

    mount -o remount,rw /system
    cp -r /mnt/sdcard/apps-install/* /system/
    chmod 755 /system/addon.d/70-gapps.sh
    mount -o remount,ro /system

    When installing the face recognition service, 71-gapps-faceunlock.sh also needs to be chmodded.

    After copying, reboot the phone – Android will “optimize” your applications, and that’s it. As far as I know, one cannot use the Play Store without Google Account Services and all it’s downsides (like advertising, google only provides the setting to “ask” applications not to track users). So, if possible, use the APKDownloader extension or alternate sources like F-Droid. Unfortunately, only few developers sell their apps directly.

    (first version, changes pending)