<?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>DokuWiki fixed:firmware</title>
        <description></description>
        <link>http://tibbo.com/kb/</link>
        <image rdf:resource="http://tibbo.com/kb/lib/images/favicon.ico" />
       <dc:date>2010-09-10T10:48:22+04: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/fixed/firmware/first_bytes_lost?rev=1220954540&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/fixed/firmware/junk_trailer?rev=1220955482&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/firmware/port_65535?rev=1220957111&amp;do=diff"/>
                <rdf:li rdf:resource="http://tibbo.com/kb/fixed/firmware/settings_go_into_effect?rev=1220957210&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://tibbo.com/kb/lib/images/favicon.ico">
        <title>DokuWiki</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+04:00</dc:date>
        <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/fixed/firmware/first_bytes_lost?rev=1220954540&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-09-09T14:02:20+04:00</dc:date>
        <title>Losing the First Few Data Bytes</title>
        <link>http://tibbo.com/kb/fixed/firmware/first_bytes_lost?rev=1220954540&amp;do=diff</link>
        <description>Question: The first five bytes in the first data block received from the serial device when beginning the communication are always missing. I have also tried to reboot the DS 202 with the 'E' command, but with the same result. Why is this?

Answer: One of the most probable reasons is that both setup values - Start on any char and Use Start character are set to NO. This way, the DS doesn't have a specific char to start from, and also doesn't start on the first char and you lose a few bytes in the…</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/fixed/firmware/junk_trailer?rev=1220955482&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-09-09T14:18:02+04:00</dc:date>
        <title>My DS Sends Packets With Trailing 'Junk' Data</title>
        <link>http://tibbo.com/kb/fixed/firmware/junk_trailer?rev=1220955482&amp;do=diff</link>
        <description>Question: I have an applications which sends data in very short bursts, so the DS creates packets containing just 1 data byte. But when I inspect the packets using Ethereal or WinDump, I see that they contain a 'trailer' section with garbage data, which just makes the packet larger. Why is that?</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+04:00</dc:date>
        <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/firmware/port_65535?rev=1220957111&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-09-09T14:45:11+04:00</dc:date>
        <title>Can't set the Port Number to 65535.</title>
        <link>http://tibbo.com/kb/fixed/firmware/port_65535?rev=1220957111&amp;do=diff</link>
        <description>Question: I am trying to set the port number to 65535 but the DS100/EM100 wouldn't let me do this! Why is that?

Answer: The DS100/EM100 has two logical ports - a Data Port and a Command Port. The Data Port is used to exchange the serial data between the DS100/EM100 and the remote station (PC, another DS100, etc.). Command Port is used to setup the DS100 via the Network. The Data Port number is user-definable and can be in the range from 0 to 65534. Command Port number is fixed at 65535. This is…</description>
    </item>
    <item rdf:about="http://tibbo.com/kb/fixed/firmware/settings_go_into_effect?rev=1220957210&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-09-09T14:46:50+04:00</dc:date>
        <title>When EEPROM settings go into effect</title>
        <link>http://tibbo.com/kb/fixed/firmware/settings_go_into_effect?rev=1220957210&amp;do=diff</link>
        <description>Question: I have noticed that after I modify the Settings using the “S” command (i.e. “SBR3” to change the baudrate) the changes do not have immediate effect. When do the changes take place? Is there a way to make those changes have immediate effect?</description>
    </item>
</rdf:RDF>
