Set64rs-Channel-Management-Form: Difference between revisions

From *** My Personal Wiki ***
Jump to navigation Jump to search
← Older edit
Embeddedrf (talk | contribs)
1,247 edits
Embeddedrf (talk | contribs)
1,247 edits
 
(17 intermediate revisions by the same user not shown)
Line 3: Line 3:
== Scanning Channel Installation Tool ==
== Scanning Channel Installation Tool ==


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


== DataBase Design ==
== DataBase Design ==


Fields =  Channel# NickName Installed Controller Type .... all channels in just 1 database ????
Fields =  SoftwareChannel | ModBusAddress |  NickName | Controller Type
 
== Address Setup ==
 
 
== 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  
*'''SoftwareChannel''' will be both software channel identifier and modbus address > forcing user to sync software channel & modbus address
*User can manual set / select controller modbus address using controller front panel
*'''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


'''Automated Method where computer helps'''


'''Steps'''


*Prompt User > connect unit to be installed > disconnect all other controller communication cables
* 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


*Scan address 1 - 64 until unit is found > look for valid reply


*Check to see if this address is already used: 
== Change Address Utility ==
**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
*Look to see if controller exists at the FROM address > if not flag
*Look to see if there is already a controller at TO address > if so then flag
*If address is changed successfully then change the PROFILE DIARY database entries to reflect the new address

Latest revision as of 13:07, 12 March 2010

Software_Design_Notes_-_MultiChannel_Set64rs

Scanning Channel Installation Tool[edit]

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

DataBase Design[edit]

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[edit]

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


Change Address Utility[edit]

  • Look to see if controller exists at the FROM address > if not flag
  • Look to see if there is already a controller at TO address > if so then flag
  • If address is changed successfully then change the PROFILE DIARY database entries to reflect the new address
Retrieved from "http://wiki.amarketplaceofideas.com/index.php?title=Set64rs-Channel-Management-Form&oldid=3852"