12:22 Jul 25, 2006 |
English language (monolingual) [PRO] Tech/Engineering - Manufacturing | |||||||
---|---|---|---|---|---|---|---|
|
| ||||||
| Selected response from: Tony M France Local time: 13:29 | ||||||
Grading comment
|
SUMMARY OF ALL EXPLANATIONS PROVIDED | ||||
---|---|---|---|---|
4 +1 | See explanation below... |
|
Discussion entries: 4 | |
---|---|
read information in “coil” and “float” blocks See explanation below... Explanation: It really is difficult to see what there is not to understand! This software can read data in blocks (a block of data could mean many things, but probably means a group of bytes, or of individual bits — it all depends on the rest of the context, which you have but I don't) There may also be other such blocks, but 2 of them are called 'coil' (something to do with a water condensing / cooling coile, perhaps?) and 'flaot' (maybe something to do with a float used to measure coolant level, for example) Is that what you wanted to know? -------------------------------------------------- Note added at 59 mins (2006-07-25 13:21:25 GMT) -------------------------------------------------- It seems as if they are saying that, in order to avoid reading too much information, or too often, certain other blocks of data might be read less often, but the important 'coil' and 'float' data should be read continuously (I take it that's what they mean by 'always') You presumably must have a lot more information about XXX than I do, so of course I'm having to use a lot of supposition here. |
| |
Grading comment
| ||
Login to enter a peer comment (or grade) |
Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.