<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tools on Wired &amp;&amp; Coded;</title>
    <link>http://localhost:1313/categories/tools/</link>
    <description>Recent content in Tools on Wired &amp;&amp; Coded;</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 05 Jun 2014 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/categories/tools/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Voltcraft VC-870 Multimeter Used With UNI-T UT-D04 USB Cable</title>
      <link>http://localhost:1313/posts/2014/2014-06-05-voltcraft-vc-870-multimeter-used-with-uni-t-ut-d04-usb-cable/</link>
      <pubDate>Thu, 05 Jun 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-06-05-voltcraft-vc-870-multimeter-used-with-uni-t-ut-d04-usb-cable/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Target hardware:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://www.conrad.de/ce/de/product/124603/VOLTCRAFT-VC870-Digital-Multimeter-m-Leistungsmessadapter-VC800-Serie-40000-Counts-CAT-IV-600-V?ref=searchDetail&#34;&gt;VOLTCRAFT VC-870 Multimeter&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://sigrok.org/wiki/Device_cables#UNI-T_UT-D04&#34;&gt;UNI-T UT-D04 USB Cable&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;Software repository location:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/jsyk/VC870_USB_Datalog&#34;&gt;https://github.com/jsyk/VC870_USB_Datalog&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;The issue this software solves:&lt;/strong&gt; Although the Voltcraft multimeter and the UNI-T USB cable are  hardware compatible (the USB cable adapter fits into the multimeter connector perfectly), the software requirements are different. Original Voltcraft USB cable, which costs tripple the UNI-T cable by the way, mimics RS232 adapter when plugged in USB host PC. The UNI-T cable uses different chip internally and behaves like a HID device. On the other hand, UNI-T multimeters use different communication protocol over the serial line than the &lt;a href=&#34;https://github.com/jsyk/VC870_USB_Datalog/blob/master/doc/vc870_protocol.pdf?raw=true&#34;&gt;VC870 does&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Philips PM3310 Digital Storage Oscilloscope</title>
      <link>http://localhost:1313/posts/2014/2014-05-14-philips-pm3310-digital-storage-oscilloscope/</link>
      <pubDate>Wed, 14 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-05-14-philips-pm3310-digital-storage-oscilloscope/</guid>
      <description>&lt;p&gt;I got myself an old &lt;strong&gt;Philips PM3310 Digital Storage Oscilloscope&lt;/strong&gt; (DSO). The scope has a classic CRT screen, but otherwise it is a fully digital device. The scope has two channels. Analogue bandwidth of the input attenuator/amplifier is 60MHz, which is not bad at all. Sampling frequency in real-time mode, however, is only 50 Mega samples per second. Each sampling &amp;lsquo;run&amp;rsquo; after a trigger stores 256 samples into a RAM. The sample RAM has capacity for 4 independent waveforms. The 50M sampling speed allows single-shot time base up to 500ns/div, and a recurrent time base up to 5ns/div (sampling of repetitive signals in &lt;a href=&#34;http://www.tek.com/document/application-note/real-time-versus-equivalent-time-sampling&#34;&gt;equivalent time&lt;/a&gt;). The internal CPU switches between the modes as needed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Xilinx Vivado 2013.3 on Fedora 18: Working around a D-Bus bug</title>
      <link>http://localhost:1313/posts/2013/2013-11-10-xilinx-vivado-2013-3-on-fedora-18-working-around-a-d-bus-bug/</link>
      <pubDate>Sun, 10 Nov 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2013/2013-11-10-xilinx-vivado-2013-3-on-fedora-18-working-around-a-d-bus-bug/</guid>
      <description>&lt;p&gt;Running Xilinx &lt;strong&gt;Vivado 2013.3&lt;/strong&gt; (webpack license) on &lt;strong&gt;Fedora 18&lt;/strong&gt; may fail with the following error message:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ vivado&#xA;&#xA;****** Vivado v2013.3 (64-bit)&#xA;  **** SW Build 329390 on Wed Oct 16 18:26:55 MDT 2013&#xA;  **** IP Build 192953 on Wed Oct 16 08:44:02 MDT 2013&#xA;    ** Copyright 1986-1999, 2001-2013 Xilinx, Inc. All Rights Reserved.&#xA;&#xA;INFO: [Common 17-78] Attempting to get a license: Implementation&#xA;process 17688: arguments to dbus_move_error() were incorrect, assertion &amp;#34;(dest) == NULL || !dbus_error_is_set ((dest))&amp;#34; failed in file dbus-errors.c line 282.&#xA;This is normally a bug in some application using the D-Bus library.&#xA;  D-Bus not built with -rdynamic so unable to print a backtrace&#xA;Abnormal program termination (6)&#xA;Please check &amp;#39;/home/jara/hdl/hs_err_pid17688.log&amp;#39; for details&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The workaround is to make the D-Bus communication socket file &lt;strong&gt;/var/run/dbus/system_bus_socket&lt;/strong&gt; unavailable when the Xilinx tools run.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
