Under the fail help, fail type 7 is determined as "Fails as no I2t data is available for the devices, assume a failure by default".
I assume that the I2t data for the specific devices is not present in the data file for that particular device, in this instance Schneider Mirologic ACB's.
With no I2t data the calculation defaults to unlimited energy let through, which then fails the k2s2 > I2t test.
As such I'm left with a failure on the main supply where I'm using Schenider ACB's on both the LV supply (in this case an outgoing transformer) and on the incoming side of the main panel board.
Using the generic ACB on the LV feeder overcomes the issues, but then gives me a discrimination problem with the down stream Schneider ACB.
Why is the I2t data not included in the calculation? And how do I overcome the issues?
Schneider ACB's must be one of the most commonly used protective devices of this type.
I too have the need to produce calculations for scrutiny by a Consultant.
When will this issue be resolved? Using a Generic ACB does not satisfy the Consultant, they require the verified calculations using the devices we will be installing.
Please advise when a fix will be provided.
Does this mean that traditional Connect software is being ignored?
Not all users have the funds or inclination to adopt OpenBuildings Designer.
Paul,
I would suggest connect has been neglected for some time. I raised the issue of missing data from the Schneider range back in 2019, along with my concerns over the calculation method for Zs and cable sizing, over sized armour on SWA cables compared to the actual amount of SWA incorporated by the cable manufacturers, no Eaton IZM data.
The UI of the software hasn't changed for 20 years, I've been using connect since 1999.
Hi Paul and Stuart,
Apologies for the late response!
Based on Prduct management's response on this, I'm afraid that we do not have any immediate plans of developing Hevacomp connect, or transitting the facilities in OpenBuildings.
Thanks for raising this and I genuinely appreciate your concern!
Regards,
Krishnendu