|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
I hope that the rest of the team will be OK with this and we can move on.
Yes, that was what I was trying to say.
I fully agree to that approach.
When I said ' Define CP2PRUNB at 20degC." I meant to that I want to use the CP2PRUNB number that I was calculating (26.2%) at room temperature, set it as THE number to meet without saying at what temperature it is, and vendors will have to assure that they meet it at their operating temperature range spec. How they will do it, we don’t care.
Is it equivalent to your intention?
Agreeing with this, except point one should be
1. Define CP2PRUNB (independent of temperature).
Then the vendors should decide, the temperature over which their product operates, and should assure that the requirement is met over that temperature range. Interoperability will be assured if the system designers assure that the elements of their system are all specified over the needed temperature range.
Yes I familiar with it, however it actually says that you reduce that cable length and we want to ensure interoperability for up to 100m so in our case I need to address lower temperature (We don’t have issues with higher temperature above room temperature since CP2PRUNB is increased if temperature is decreased) so what is your opinion regarding the following approach:
2. Define CP2PRUNB at 20degC.
3. Supply CP2PRUNB temperature coefficients in the mandatory or informative section
4. System vendor will design their equipment to meet the requirement for their system lowest temperature point.
5. This will ensure the interoperability (?)