Class B class C software - Page 1
Forum section: electronics / projects

author: hamdi.tn
author_rank: Frequent Contributor
timestamp: January 24, 2016, 08:32:20 pm
content: Hi everyone,am doing some reading on the IEC-60730 and am in phase that i started the design and wrote all functional part of the software , and now am trying to make it compatible with IEC-60730. As i read "H.11.12.7 Annex H IEC 60730-1" that explain the tests that need to be done on the hardware to make sure it works just fine. i can't see much difference between the C and the B.The first thought at the very beginning of this project that we will share security phase between 2 MCU so there is no need to write in a Class B or use any class B library as our client is getting so much trouble from it on the field ( so basicly write in class A). But now am a bit confused as in no where this standard say that if you use 2 MCU you can just ignore this table (i know it sound stupid ) and the question now is should i write both MCU software in class B/C type (so both MCU should so a hardware test mentioned in annex H).The standard say at some point class C software should have ( among others structures ) : two independent and different ways of control over the secure part. Does double MCU structure count as such.Please advice.

author: hamdi.tn
author_rank: Frequent Contributor
timestamp: January 25, 2016, 08:08:12 am
content: Did i post this on the wrong category , should i post it in the micro controller section

author: Jeroen3
author_rank: Super Contributor
timestamp: January 25, 2016, 09:11:46 am
content: I was not aware of the existence of this IEC "Safety Standard for Household Appliances". I don't think there are many people following this specific IEC. And those that do are most likely not active on this forum.

author: hamdi.tn
author_rank: Frequent Contributor
timestamp: January 25, 2016, 03:25:31 pm
content: Quote from: Jeroen3 on January 25, 2016, 09:11:46 amApparentlythe thing is almost all micro-controller manufacturer have some documentation about this particular IEC so i thought it's a well know one.For sure at least there is one who kind of know about it and active in this forum

author: Phoenix
author_rank: Frequent Contributor
timestamp: January 25, 2016, 10:51:27 pm
content: I've just started trying to work with IEC60730 Annex H microcontroller stuff (couple of months). Would love to also hear from others with more experience, I'm only trying to deal with a Class B product.My interpretation is having the dual path still means you need to be compliant with the internal self-tests. And that dual path for class C means you need to be able to detect and react appropriately to failure/implausibilities when comparing the two paths. However with class B you may not need to detect a single sensor system failure so long as the other path still maintains the safety functionality.

author: hamdi.tn
author_rank: Frequent Contributor
timestamp: January 26, 2016, 09:01:57 am
content: Quote from: Phoenix on January 25, 2016, 10:51:27 pmHi, that's my interpretation too , but as i discuss this with a senior developer who use to develop such thing long ago. his point of view is that what matter the global scene and not how a single path is done. In the particular case of a double MCU configuration , if both MCU communicate in a secure way and duplicated measurement of critical sensors and MCUs compare data, there is no need to check each MCU hardware by itself. Am not sure if this is a good interpretation.

author: hamdi.tn
author_rank: Frequent Contributor
timestamp: January 29, 2016, 07:24:31 am
content: No man land for the IEC60730