I'm building a new industrial app using MODBUS/TCP talking to a DAQ unit that will have a lot of parameters and will need to be adaptable for different scenarios. For example, the units I'm connecting to have 12 inputs and 6 outputs, mapping for those may be different for each installation, and in one instance I'll be talking to 4 units together - if that's the best way to do it - each one will have identical parameters, just a different ID number and ip address. They will all be writing to a SQL Server database. Not sure if I'm better off having a Tab control with each unit on a separate tab or a different instance of the app for each one. Is one better than the other? The units will be polled every 200-500ms. 500ms seems to be more stable.
My question is this:
With so many parameters, is it better to store all them inside the application and access them through My.Settings or would I be better storing them in a database, either the SQL Server DB or maybe something like SQLite (one of my faves) or is there a better way?
Not done anything quite as big as this before and first time with MODBUS, but that bit is working a treat.
Using .Net 3.5 and VB.net 2008
My question is this:
With so many parameters, is it better to store all them inside the application and access them through My.Settings or would I be better storing them in a database, either the SQL Server DB or maybe something like SQLite (one of my faves) or is there a better way?
Not done anything quite as big as this before and first time with MODBUS, but that bit is working a treat.
Using .Net 3.5 and VB.net 2008
