darrenj said:
see the problem pierre is i have no experiance with info grabbing over any of the networks, or VB, C, or SQL.. I am just a dumb old sparky who knows enough to get himself in trouble with PLC's !!
First, you know that you don't know. Hence wisdom.
Second, You have posted your questions and comments in a way that all have understood. Hence, you can point where lies the problems.
Now, with these two you have solved 90% of your problem.
The remainding 10% comes from experience which you have none. Experience into quoting such system, that is.
To make it simple, list what THEY want.
- How many PLC
- How many networks
- What info will travel, READs and WRITEs
- How to present the info (Database?, simple text file?)
- How critical is the info. Can it be loss? Even for a few seconds? Miutes? Hours?
- What hardware is available (on the PC side... VERY IMPORTANT, NEVER let them mess with this)
- How fast do you need to implement this
Keeping these types of system seemingly complicated is just the Coders way to job security
Remember the first time you where left all alone with a PC that gave you the blue screen of death. And the guys that sowed you how complicated it was and how good they where. I guess today you'd have another version for this. Its called bull-starstarstarstarstar.
Seperated your problem into sections.
Do them one by one with excellent structure and all will be OK.
As for the quote, the Hardware cost x 2 does not apply here.
Will they give you the order if you quote them 40 hours per PLC? Then thats the price.
If not, what is the budget?
How much money would you pay for schooling on such systems IF you where garantied to have this project when you finish school.? Could that be the amount you will invest over-and-above your quote IF you bust your time estimate?