Profile-UpLoad-Form-Set64rs: Difference between revisions
Jump to navigation
Jump to search
Embeddedrf (talk | contribs) |
Embeddedrf (talk | contribs) |
||
| Line 34: | Line 34: | ||
*CompileProfile > uses this array from Index=1 | *CompileProfile > uses this array from Index=1 | ||
** will not work with mdlProfileArray as is | ** will not work with mdlProfileArray as is | ||
** the array that is used for the compiling purpose has to be by nature a scratchpad > user can move it all around and if shared will cause and overwrite!!! | |||
Revision as of 19:24, 19 March 2010
Software_Design_Notes_-_MultiChannel_Set64rs
Profile Log Operation
- DataBase has fields: ProfileName | Start | Stop | ModBusAddress
- all channels in just 1 database > Why?
- when user juggles units it is best if the unit diaries follow >
- rather than changing | folder location | file name the main channel database can just change the entries in the database > this applies for everything!
- when user juggles units it is best if the unit diaries follow >
- Can be just another TABLE is the ChannelManagement database??? TableName = ProfileUpLoadLog
Other methods of channel diary management
- having separate folders forces the following:
- new folder creation when a channel comes into existence
- deletion when controller removed
- change when controller moves addresss
Design Issues
Use of mdlProfileArray
- CONCEPT: Use mdlProfileArray as a scratchpad that can then subsequently be
- uploaded to controller
- written into the ProgramMemory table of the database
- CompileProfile > uses this array from Index=1
- will not work with mdlProfileArray as is
- the array that is used for the compiling purpose has to be by nature a scratchpad > user can move it all around and if shared will cause and overwrite!!!