<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://tibbo.com/kb/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://tibbo.com/kb/feed.php">
        <title>Tibbo Knowledge Base</title>
        <description></description>
        <link>http://tibbo.com/kb/</link>
        <image rdf:resource="http://tibbo.com/kb/lib/images/favicon.ico" />
       <dc:date>2010-03-05T02:25:23+03:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://tibbo.com/kb/fixed:firmware:buffers?rev=1267621476&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/general:hardware:serial_upload?rev=1266843179&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/general:hardware:hot_device?rev=1266843119&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/general:hardware:ds_dies?rev=1266842967&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/general:hardware:determining_point_of_failure?rev=1266842844&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/general:hardware:con485?rev=1266841765&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/fixed:tdst:cannot_see_taiko_device?rev=1266840968&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/fixed:networking:default_ip?rev=1266840849&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/fixed:networking:data_split_packets?rev=1266840817&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/fixed:firmware:leds?rev=1266840434&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/fixed:vspdl?rev=1264587828&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/basic:software:fntmaker?rev=1261477049&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://tibbo.com/kb/lib/images/favicon.ico">
        <title>Tibbo Knowledge Base</title>
        <link>http://tibbo.com/kb/</link>
        <url>http://tibbo.com/kb/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://tibbo.com/kb/fixed:firmware:buffers?rev=1267621476&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-03-03T16:04:36+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>Size of the Routing Buffers and How They Affect the Device Server</title>
        <link>http://tibbo.com/kb/fixed:firmware:buffers?rev=1267621476&amp;do=diff</link>
        <description>Question: I am wondering if the capacity of the internal serial buffers of the Device Server is enough for my serial application. How much data can the buffers hold (transmit)?

Answer: Just checking the physical capacity of the serial buffers of the Device Server is not a correct approach. Several other factors must be taken into consideration. The ability of the Device Server to transmit (without losses) the serial data of a certain size also depends on the selected transport protocol and flow…</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/general:hardware:serial_upload?rev=1266843179&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-22T15:52:59+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>How to Perform a Serial Firmware Upload</title>
        <link>http://tibbo.com/kb/general:hardware:serial_upload?rev=1266843179&amp;do=diff</link>
        <description>Question: How do I perform a serial upload of new (or old) firmware?

Answer: Whenever you have a problem with either loading the wrong firmware or suspect that there are problems with the firmware which caused access problems, please try to upgrade the firmware through the serial port.  This is our fail-safe port for dealing with firmware related problems.</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/general:hardware:hot_device?rev=1266843119&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-22T15:51:59+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>My DS203 gets very hot!</title>
        <link>http://tibbo.com/kb/general:hardware:hot_device?rev=1266843119&amp;do=diff</link>
        <description>Question: When I connect the DS203 to a power source, it gets very very hot. Is it going to burn? Is it normal? Why is that?

Answer: This is normal! DON'T PANIC. :) The only reason for this is that the DS203 is a 100BaseT device. 100BaseT Ethernet devices always get very hot -- and this is to be expected.</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/general:hardware:ds_dies?rev=1266842967&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-22T15:49:27+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>My DS works fine for some time, but then dies</title>
        <link>http://tibbo.com/kb/general:hardware:ds_dies?rev=1266842967&amp;do=diff</link>
        <description>Question: I connect a DS to a power source and LAN, and configure it. All seems just fine, and things work properly. But then, after a few hours or days of work, suddenly the DS 'dies'. I can't see it in DS Manager, I can't ping it, and nothing seems to work all of a sudden. Or it works erratically -- sometimes works, sometimes doesn't.</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/general:hardware:determining_point_of_failure?rev=1266842844&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-22T15:47:24+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>So My Module / Device Server is Not Functioning Correctly, Is It Broken?</title>
        <link>http://tibbo.com/kb/general:hardware:determining_point_of_failure?rev=1266842844&amp;do=diff</link>
        <description>Question: My module / device server has been acting weird, is it broken?

Answer: Frequently, the problems encountered are not caused by hardware failure of the module itself, it could be caused by firmware and setting related reasons (incorrect settings, incorrect connections, or corrupt firmwares) or power related reasons.  Below are the suggested troubleshooting steps.</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/general:hardware:con485?rev=1266841765&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-22T15:29:25+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>Connecting a DS100B to a GigaTMS Con485</title>
        <link>http://tibbo.com/kb/general:hardware:con485?rev=1266841765&amp;do=diff</link>
        <description>Question: How do I connect a DS100B to a GigaTMS Con485 device?

Answer: The Con485 is a converter between RS232 and RS485 produced by GigaTMS. This article covers how to connect it to the DS100B for testing purposes.


	*  First, set a baudrate on the Con485. For example, select 9600.
	*  Make sure this baudrate is set also for the DS. This can be done in settings, or using on-the-fly commands when you open the connection.
	*  Flow Control must be “Idle or Remote”, since there is no RTS/CTS in …</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/fixed:tdst:cannot_see_taiko_device?rev=1266840968&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-22T15:16:08+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>I Connected My Device But I Still Can't See it in DS Manager</title>
        <link>http://tibbo.com/kb/fixed:tdst:cannot_see_taiko_device?rev=1266840968&amp;do=diff</link>
        <description>Tibbo makes fixed-function Device Servers and modules, but also programmable devices. This can get tricky because some devices can be either fixed-function or programmable, depending on the firmware they carry. Such dual-use devices include the DS202/203, EM202/203 and EM200.</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/fixed:networking:default_ip?rev=1266840849&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-22T15:14:09+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>Default IP Address for DS</title>
        <link>http://tibbo.com/kb/fixed:networking:default_ip?rev=1266840849&amp;do=diff</link>
        <description>Question: I don't see the DS on my LAN for some reason (using DS Manager). Can you tell me what is the original IP address of the DS so I could detect it?

Answer: The default IP address for Device Servers is usually a “loopback” address -- 127.0.0.1. It has no meaning in a LAN -- it refers to the device itself only.</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/fixed:networking:data_split_packets?rev=1266840817&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-22T15:13:37+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>My serial data gets split into several packets. What do I do?</title>
        <link>http://tibbo.com/kb/fixed:networking:data_split_packets?rev=1266840817&amp;do=diff</link>
        <description>Question: I'm trying to get Data from a Barcode terminal connected via RS232 to the Tibbo DS100. I get the Data, but I get it sometimes all in one packet and somtimes in several packets. 

How can I know that I got the last data bytes? Does the Tibbo makes a Close connection? I get some of the data in few packeges and don't know how to paste them.</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/fixed:firmware:leds?rev=1266840434&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-22T15:07:14+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>Why Do the LEDs On My Device Blink Like THIS?</title>
        <link>http://tibbo.com/kb/fixed:firmware:leds?rev=1266840434&amp;do=diff</link>
        <description>Question: I get a LED pattern on my device, and I don't understand what it means.

Answer: Tibbo has a comprehensive LED emulator, which shows the different patterns and their meaning. You may access it by clicking Here.

Note: This emulator applies to fixed firmware, where the LED signals are pre-determined. If your device is running a Tibbo BASIC application, only the developer of that application tell you what the LED signals mean (he designed them).</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/fixed:vspdl?rev=1264587828&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-01-27T13:23:48+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>Installing Tibbo Virtual Serial Port Driver under Linux</title>
        <link>http://tibbo.com/kb/fixed:vspdl?rev=1264587828&amp;do=diff</link>
        <description>0.0 Downloading VSPDL


Make sure that you are using the latest version of VSPDL.
You can always get the latest version from &lt;http://www.tibbo.com/vspdl.php&gt;

0.1 Unpacking VSPDL

0.1.0 Unpacking from RPM


[root@dvhome vspd.tmp]# rpm -ivh ./vspd-1.11-linux.i586.rpm
Preparing... ####################### [100%]
  - vspd ######################### [100%]</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/basic:software:fntmaker?rev=1261477049&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-12-22T13:17:29+03:00</dc:date>
        <dc:creator>wikisu</dc:creator>
        <title>LCD Font Maker</title>
        <link>http://tibbo.com/kb/basic:software:fntmaker?rev=1261477049&amp;do=diff</link>
        <description>FntMaker is a handy little tool we created to convert fonts from Raster Font Editor to our own format, which can be used on Tibbo BASIC devices with the LCD object.

You can download FntMaker for free in our Programmable Software section.

Usage
fntmaker filename [cut] [cut] [cut] [cut] [spacewidth] [options]

filename should be without extension. filename.txt will be used for input. filename.bin will be used for output.</description>
    </item>
</rdf:RDF>
