<?xml version="1.0" encoding="utf-8"?>
<rss version="0.92" xml:base="http://www.opendax.org">
<channel>
 <title>OpenDAX - issues</title>
 <link>http://www.opendax.org/project/issues</link>
 <description></description>
 <language>en</language>
<item>
 <title>Trigger Condition</title>
 <link>http://www.opendax.org/node/88</link>
 <description>I need to add a trigger condition for sending master requests.  Right now the only conditional request is based on the data that the command is sending.  There should be a way to use a different piece of data to determine when to send a request.  Possibly one that allows for the module to reset it once the command has been sent.  I&#039;m thinking of a boolean tag that another module (or modbus command) could set and then once the request is sent this bit would be reset.</description>
 <pubDate>Fri, 09 May 2008 11:11:25 -0500</pubDate>
 <comments>http://www.opendax.org/node/88</comments>
 <category>Modbus Module</category>
</item>
<item>
 <title>Signal Handling</title>
 <link>http://www.opendax.org/node/75</link>
 <description>The signal handling is not good.  I need to deal with the SIGPIPE in each port thread and stop that thread when it gets one.  Then I need to have a generic signal handler for all the threads so that I know where the rest of the signals go.  BSD and Linux treat signals quite a bit differently and this will make the module more portable.</description>
 <pubDate>Thu, 14 Feb 2008 14:39:31 -0600</pubDate>
 <comments>http://www.opendax.org/node/75</comments>
 <category>Modbus Module</category>
</item>
<item>
 <title>Modbus TCP</title>
 <link>http://www.opendax.org/node/52</link>
 <description>We should add Modbus TCP client and server to the module. </description>
 <pubDate>Fri, 02 Nov 2007 07:07:25 -0500</pubDate>
 <comments>http://www.opendax.org/node/52</comments>
 <category>Modbus Module</category>
</item>
<item>
 <title>Finish RTU Slave</title>
 <link>http://www.opendax.org/node/51</link>
 <description>The module can only be a Modbus master node at this point.  It needs to be able to handle master and slave.</description>
 <pubDate>Fri, 02 Nov 2007 07:05:41 -0500</pubDate>
 <comments>http://www.opendax.org/node/51</comments>
 <category>Modbus Module</category>
</item>
<item>
 <title>Complete Function Codes</title>
 <link>http://www.opendax.org/node/50</link>
 <description>The module only implements a subset of the Modbus function codes at this point.  I don&#039;t know if we&#039;ll implement every function code in the specification but there needs to be more than the few that we have done.  A complete list is in the TODO file.</description>
 <pubDate>Fri, 02 Nov 2007 07:03:44 -0500</pubDate>
 <comments>http://www.opendax.org/node/50</comments>
 <category>Modbus Module</category>
</item>
<item>
 <title>Modbus ASCII</title>
 <link>http://www.opendax.org/node/20</link>
 <description>Implement the Modbus ASCII protocol (master and slave)
</description>
 <pubDate>Tue, 10 Jul 2007 13:54:19 -0500</pubDate>
 <comments>http://www.opendax.org/node/20</comments>
 <category>Modbus Module</category>
</item>
</channel>
</rss>
