yep, you're right ... 'though the problem then is how to do it without introducing significant extra cost & sources of unreliability ...
all this was done with aircraft years ago, but they needed multiple redundancy to make it work, and got into all sorts of voting schemes ... not something we want to do !
must say, it's tempting to think in terms of some sort of overseer, that looks at the broad sweep of things & cries foul when it looks like things are going awry ... as when water flow & electrical current don't match what seems to be appropriate ...
eg: maybe we could have Cortex tell of what it's asked what to do, and the overseer could check the sum of this against what the main house-meters are saying ... sort of parity check !
I don't quite get this?Originally Posted by chris_j_hunter
The extra cost is minimal....you just need to code in checks for the certain conditions that create a dangerous situation.
Question is should it be included anyway as part of a good robust design?
yep, it should, basic good practice ... but where & how exactly to include it, given the set-up would include the solenoid, one of the Idratek relay units (an SRH, say), with Reflex, and Cortex ... not forgetting we are working on the customer side of things, not within the Idratek team ...
Last edited by chris_j_hunter; 1st January 2011 at 12:43 PM.
I don't honestly think you can....it would be best coded into the MCU inside the module.
Posting Permissions
Reply With Quote