Set64rs-Channel-Management-Form: Difference between revisions

From *** My Personal Wiki ***
Jump to navigation Jump to search
Embeddedrf (talk | contribs)
Embeddedrf (talk | contribs)
Line 29: Line 29:
** add each controller seen to the ChannelMap  
** add each controller seen to the ChannelMap  
** delete any ChannelMap address entries in the table that do show up as not having an controller connected
** delete any ChannelMap address entries in the table that do show up as not having an controller connected
== Initialization Scan ==
*Do initial scan to see which controller addresses are installed
*Stores status in the database table under INSTALLED?
'''Manual Method'''
*User looks at database and selects address
*User can manual set / select controller modbus address using controller front panel
'''Automated Method where computer helps'''
*Prompt User > connect unit to be installed > disconnect all other controller communication cables
*Scan address 1 - 64 until unit is found > look for valid reply
*Check to see if this address is already used: 
**Prompt User > This address is already in system use by NICKNAME | This address is not already in use
**Prompt User > You can Change address by clicking X Button.  ( has textbox display and button pair + number only parsing ) > verify not already in use!
**If user changes address > rescan to verify change in effect > Prompt User > change effected
*Prompt User> Store this in channel database? Click Store Channel

Revision as of 13:04, 12 March 2010

Software_Design_Notes_-_MultiChannel_Set64rs

Scanning Channel Installation Tool

  • Assume a known fully installed serial port > user uses serial port scan tool first

DataBase Design

Fields = SoftwareChannel | ModBusAddress | NickName | Controller Type


  • SoftwareChannel will be both software channel identifier and modbus address > forcing user to sync software channel & modbus address
  • ModBusAddress unit addresses
  • NickName name of channel such as "glass melting kiln"
  • ControllerType Example: set64rs > for future use to allow mixed controller usage

Installation - Address Setup

Notes System may need to preserve certain ModBus addresses for other than this software - thus:

  • a channel to modbus map is needed
  • some addresses may be skipped


Steps

  • prompt user to: Set each controller to a unique address > can use the address change utility
  • scan the port: User has 2 options
    • add each controller seen to the ChannelMap
    • delete any ChannelMap address entries in the table that do show up as not having an controller connected