The progress bar will take approximately 15 seconds to load the demonstration version. The licensed program - goes immediately to the main Simply Modbus Read window and bypasses the Loading Demo startup window. The demo version - offers full functionality - requires a program restart to send more than six read requests or two write commands. Controls inputs that can be changed by the user are shown in yellow.
Indicators outputs shown in blue cannot be changed. Select the Server's Port to connect to. Press the Connect button and the program will attempt to connect to the Modbus Server. The program will keep trying to connect until a connection is made or the button is pressed again.
Remains on for all addresses until the Slave ID is lowered below and the box manually unchecked. Used to select which table to read from. This value is subtracted from the First Register to give the data address used in the Request. The size of the registers in the block to be read. This value should be set to 16 bit registers to read standard modbus registers.
Events: This box is checked when reading Enron events from register 32 more info History: This box is checked when reading Enron historical records from register more info These are error detection bytes.
They are not present in TCP Mode more info Exceptions for reading Enron modbus data : First Register function code minus offset register size 32 events 3 0 32 bit registers to history 3 0 32 bit registers to 1 0 1 bit coils to 3 0 16 bit registers to 3 0 32 bit registers to 3 0 32 bit registers. Before sending a message, the ethernet port needs to be physically connected to a network with Modbus servers. Press the SEND button.
The program then monitors for incoming data and displays all bytes received in the Response indicator. While receiving, the response time counts up with a progress bar.
Receiving stops when the expected response bytes are received or the time reaches the fail in value entered. The program then monitors for incoming data and displays all bytes received in the Response indicator. While receiving, the response time counts up with a progress bar.
Receiving stops when the expected response bytes are received or the time reaches the fail in value entered. The 'expected response bytes' indicator is calculated from the input settings.
The response timer stops when this many bytes are received. Use the pull-down boxes in the first column to set the data type for each value. The copy down button sets all data types to match the setting for the first value. The bytes are re-processed immediately as the settings are changed and the results are shown in the fourth column. Sending another request for a new response is not required for a recalculation.
Press the clear notes button to blank the whole notes column. Displays a 'Save As.. Empties the log contents. Pressing the button again will close the file and stop logging the results. The seconds after the start of one send request until the start of the next send request.
The seconds taken for the slave to respond to last message. The number of message responses received meeting the expected response bytes.
The number of message with an incomplete or absent response. The longest amount of seconds taken for a response not including failed responses. The average amount of seconds taken for a response not including failed responses. The shortest amount of seconds taken for a response not including failed responses. Sets all statistical values back to zero. Displays a 'Open File' dialog box to allow selecting a previously saved settings file to load. The configuration file is saved in tabbed text format tab separated values and appears like this in notepad.
The preset tabs in Notepad cause the cells with long labels to push the other columns over. Check back often for new TCP plans as they become available.
All users must update cells at least annually to help avoid using outdated cells. Zip KB. Work zone typical traffic control plans TCP.
0コメント