?? index.htm
字號:
<HTML>
<HEAD>
<META NAME="GENERATOR" Content="Microsoft Developer Studio">
<META HTTP-EQUIV="Content-Type" content="text/html; charset=iso-8859-1">
<TITLE>MODBUS RTU-TCP/IP and Allen Bradley DF1 PLC Simulator (Adroit)</TITLE>
</HEAD>
<BODY background="images\portA.gif">
<a name="Top"></a>
<H1>MODBUS RTU-TCP/IP and Allen Bradley DF1 PLC Simulator</H1>
<p>Use the back button in your browser to aid navigation</p>
<p>Contents:
<UL>
<LI><A HREF="#Overview">Overview</a>
<LI><A HREF="#Running">Running the program</a>
<LI><A HREF="#Ethernet Setup">Ethernet Setup</a>
<LI><A HREF="#RS-232 Setup">RS-232 Setup</a>
<LI><A HREF="#Protocols">Protocols</a>
<LI><A HREF="#Animation">Animation</a>
<LI><A HREF="#Juice Plant">Juice Plant</a>
<LI><A HREF="#Script Automation">Script Automation</a>
<LI><A HREF="#More">F.A.Q.</a>
</UL>
<HR>
</p>
<!------------------------------------------------------------------------------------>
<!------------------------------------- Overview ------------------------------------->
<a name="Overview"></a>
<H2>Overview</H2>
<p>This simulator was originally designed to allow testing of modbus master devices, as such it also allows
itself to use as a "virtual" PLC for training.
</p>
<p>Setting up the simulation for use will cover it's configuration for different applications in detail. The
first point we come to however is which <A HREF="#Media Types">media type</A> the simulation should use.
</p>
<h3>Purpose & features</h3>
<p>This simulator was written to allow the testing of a MODBUS RTU serial driver
without having to get 255 little MODBUS PLCs into one office. It is not, by any
means, a full implementation of the protocol; it implements only the common functions
used in MODBUS and other protocols supported here.</p>
<p align="center"><IMG SRC="images\toolbar.gif" ALT="?" BORDER=0>
</p>
<p>It surpasses the limitations in other programs we have found in the
past by:</p>
<ul>
<li>Simulate more than one RTU at once. (register values shared for all RTUs).</li>
<li>Allows editing and display of all the registers.</li>
<li>Allow scanning of registers not actually in the display.</li>
<li>Running on >1 comm ports (You have to run two copies of the program.). You need to run the
first copy; then, when you run it again, it defaults to use the next free RS-232 port.
All copies will use the same settings though.</li>
<li>A way of disabling just certain stations. (Just click on the boxes at the bottom.)</li>
<li>Load and save values you type into each register (the file is saved in the same folder) as well
as simulate changes in the values. Hotkey <CTRL>-L =Load and <CTRL>-A for sAve.</li>
<li>You can specify the MODBUS PDU length (Protocol Data Unit) to simulate RTU's with different internal
telegram buffer sizes. Hotkey <CTRL>-M</li>
<li>Display values in different formats hex/dec etc.</li>
<li>Specify responsiveness of the simulator to simulate slow hardware. Hotkey <CTRL>-S .</li>
<li>Simulate certain types of comms errors that would be hard to do in a "lab"
situation.</li>
<li>A basic comms debugger showing request/response. Hotkey : <CTRL>-C.</li>
<li>Emulation to simulate MODBUS MOSCAD RTU on modbus. Hotkey <CTRL>-S or <CTRL>-M . </li>
<li>Simulate noisy comms lines. Hotkey <CTRL>-N. </li>
</ul>
<h3>Not supported</h3>
<ul>
<li>MODBUS ASCII protocol support.</li>
<li>This application is not intended as a full implementation of MODBUS RTU nor TCP/IP not Allen-Bradley DF1,
it is not commercially supported and no liability is held for any damage or application changes made as
a result of it's use.</li>
</ul>
<HR>
<!------------------------------------------------------------------------------------>
<!----------------------------------- Running ---------------------------------------->
<a name="Running"></a>
<h2>Running this program</h2>
<p>This is not a full feature list, just the basics, which most will get in 5 minutes anyway.</p>
<ul>
<li>Launch the app, "mod_rssim.exe" and it should open the 1st free (RS-232 by default)port,
select the desired protocol (if ethernet, no serial port is used/needed), and then
click on the <b>Port Settings..."</b> button to change any settings. Settings are saved
to Windows<FONT SIZE="-1"><SUP>TM</SUP></FONT> registry.
<li><i>Serial protcols:</i>Hook up a cable (just a 2,3 and 7 crossed ,4,5 looped, and 6,8,20 looped should be fine,
hardware handshaking is not my strong side), but there is some support there.<BR>
<i>Ethernet:</i>U must have an ethernet adapter or loopback adapter installed.</li>
<li>The boxes at the bottom work like indicators to show which stations are active; the gray
outline of each box will change color (they turn off after five seconds), and clicking them
disables each station (only 60 are shown). The green background turns red to show a disabled
station. Disabled stations will still show activity, but the sim. will just not respond back.</li>
<li>Double-click on the list-view over a register, to edit it's value, double-clicking on
digital I/O just toggle them.</li>
<li>Switch between the Hex and Decimal views. (adddresses also come in hex, this is beta.)</li>
<BR><b><i>Some advanced options:</b></i>
<li>New option for starting with all devices offline added.</li>
<li><b>Load</b> will not work unless you have saved first.</li>
<li><b>Save</b> will save all the register values to a flat binary file (don't edit it, I can't)
called 'modbus.dat', (ABDATA.DAT if using the DF1 protcol) in the current folder. This is nice
to allow you to fill the registers with values, and then come back latter to the same setup.
Comms will be slow and may time out during load/save.</li>
<li>Click on <b>Animation Settings...</b> to change the color of the indicators at the bottom,
and set up some simulation data.</li>
<li><b>Zero values</b> will clear all values (also the digitals become 0).</li>
<li>The "responsiveness" setting changes the delay in the program before it responds to a valid request.</li>
<li>Report any problems after trying for at least a day to figure out what U got wrong :-)</li>
</ul>
<HR>
<!------------------------------------------------------------------------------------>
<!------------------------------- Ethernet Setup ------------------------------------->
<a name="Ethernet setup"></a>
<H2>Ethernet Setup</H2>
<p align="center"><IMG SRC="images\shot2.gif" ALT="?" BORDER=0>
</p>
<UL>
<li><b>Local IP</b> <i>Not settable,</i> the local IP or computer name.</li>
<li><b>Remote IP</b> <i>Not settable,</i> the remote IP or computer name of the 1st connected socket.</li>
<li><b># Server connections</b> The number of sockets the server will listen on.</li>
<li><b>Port (502)</b> The port number to listen on.</li>
<li><b>Station ID</b> Modbus station ID.</li>
<li><b>Responsiveness</b> Delay in milliseconds after receiving a request, before the simulator will send a response, this setting allows simulation of turn-around time on a slower card/NOE.</li>
</UL>
<p><b>Note:</b> If the station indicator button for a station is off, the simulator will not respond to data requests for that station ID, even though the client is connected.</p>
<HR>
<!------------------------------------------------------------------------------------>
<!-------------------------------- RS232 Setup --------------------------------------->
<a name="RS-232 Setup"></a>
<H2>RS-232 Setup</H2>
<p align="center"><IMG SRC="images\shot1.gif" ALT="?" BORDER=0>
</p>
<HR>
<!------------------------------------------------------------------------------------>
<!-------------------------------- Protocols --------------------------------------->
<a name="Protocols"></a>
<H2>Protocols</H2>
<p>Allows you to configure parameters for a specific protocol, the parameters that
can be changed differ per protocol, so some values shown may not have relevance. This
section goes on to explain what the parameters mean and what affect that have.</p>
<a name="ProtocolsModbus"></a>
<H4>MODBUS Protocol</H4>
<p align="center"><IMG SRC="images\advmbus.gif" ALT="?" BORDER=0>
</p>
<UL>
<li><b>Upper register limits</b> Highest register or I/O number the simulator will allow. Reading/writting registers/bits above this address give an Exception response</li>
<li><b>PDU (data portion) size</b> Max length of the data in a message frame.</li>
<li><b>Perform MOSCAD (row/table) checks</b> If this means nothing to U, do not use it.</li>
<li><b>Modify coils/regs. before responding</b> Allows the returned register value in telegrams that return the current register contents to either reflect the new values, or not in the responses.</li>
<li><b>Disable writting of coils/regs</b> .</li>
</UL>
<a name="ProtocolsJoy"></a>
<H4>JOY SCC386 Protocol</H4>
<p align="center"><IMG SRC="images\joyshot.gif" ALT="?" BORDER=0>
</p>
<HR>
<!------------------------------------------------------------------------------------>
<!-------------------------------- Animation ----------------------------------------->
<a name="Animation"></a>
<H2>Animation</H2>
<p align="center"><IMG SRC="images\anim.GIF" ALT="?" BORDER=0>
</p>
<HR>
<!------------------------------------------------------------------------------------>
<!-------------------------------- Juice Plant --------------------------------------->
<a name="Juice Plant"></a>
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -