Profile-UpLoad-Form-Set64rs: Difference between revisions
Jump to navigation
Jump to search
Embeddedrf (talk | contribs) New page: Software_Design_Notes_-_MultiChannel_Set64rs == Profile Log Operation == *DataBase has fields: ProfileName | START | STOP | ModBusAddress *all channels in just 1 database > Why? ... |
Embeddedrf (talk | contribs) |
||
| Line 9: | Line 9: | ||
**when user juggles units it is best if the unit diaries follow > | **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! | ***rather than changing | folder location | file name the main channel database can just change the entries in the database > this applies for everything! | ||
== 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 | |||
Revision as of 13:21, 12 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 >
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