I have been reading much lately about safety around PCBs and we also see a incresing numbers of PCBs @ openhardware.io which involves more than low DC power. With freeware CAD programs and cheap chinese pcb manufacturer alof of amatures like myself have the ability to create pcbs - in worst case not safe pcbs. This is what i gathered so far, so here we go:

Terms used

CREEPAGE

The shortest path between two conductive parts, or between a conductive part and the bounding surface of the equipment, measured along the surface of the insulation (Figure 1).

CLEARANCE

The shortest path between two conductive parts, or between a conductive part and the bounding surface of the equipment, measured through air (Figure 1).

A minimum clearance table for 150 and 300v [Ref]

MATERIAL GROUP / Insulant

DIN EN 60664-1 (VDE 0110-1) divides the insulants according to their CTI values in four groups. These are:
Insulant I: 600 ≤ CTI
Insulant II: 400 ≤ CTI < 600
Insulant IIIa: 175 ≤ CTI < 400
Insulant IIIb: 100 ≤ CTI < 175
[Ref][Ref]

Fr4 material (normal cheap-as PCBs) is normally 175 - 250CTI which is insulation material group IIIa. Ask your PCB house for your CTI value to be able to determine your material group.

POLLUTION LEVEL / Degree of contamination / Contamination level

The influence of the contamination is considered with the calculation of air and creepage distances by degrees of pollution.

• Contamination level 1
  No contamination or only dry, non-conductive contamination occurs. The contamination has no influence.
• Contamination level 2
  Only non-conductive contamination occurs. However, occasional temporary conductivity must be expected as a result of moisture condensation.
• Contamination level 3
  Conductive contamination occurs; dry, non-conductive contamination which becomes conductive as a result of moisture condensation may also occur.
• Contamination level 4
  Impurities in the form of conductive dust, rain or humidity result in permanent conductivity.
  [Ref]

Note that if you put a PCB inside a sealed component you get pollution level 1

ISOLATION/INSULATION

This is one of the most important parts - by knowing your isolation group/type you need to have for safety you enter this into the creepage calculator to get your creepage distance.

“Isolation means that no direct electrical connection, or conductor, exists between two or more circuits or between circuits and accessible parts.” … “You use safety isolation to isolate hazardous, or "live," voltages greater than 30V rms and 42.4V peak or 60V dc from user-accessible SELV (safety extra-low-voltage) circuits. Safety isolation also minimizes the possibility of transient voltage arc-over or -through insulation to user-touchable circuits and enclosures.”[Ref]

Isolation and insulation
Users have access to voltage and current through touchable connectors, cables, and user-interface devices you find on most products. Voltages must be less than or equal to 42.4V÷60 peak dc to meet safe limits and to be SELV. SELV circuits are considered safe to touch and are double-insulated from hazardous voltages in case of a single fault. SELV circuits are commonplace and find use in product inputs/outputs and interconnection, such as logic circuits for printers, PC keyboards, and telecommunications devices.[Ref]

There are five types of insulation: functional, basic, supplementary, double, and reinforced. Functional insulation is necessary only for the correct functioning of a product. Functional or operational insulation does not protect or isolate against electrical shock. Basic insulation is a single level of insulation that provides basic protection against shock. Supplementary insulation is an independent insulation that manufacturers apply in addition to basic insulation to reduce the risk of electrical shock in the event of a failure of basic insulation. Double insulation comprises both basic and supplementary insulation. Reinforced insulation is a single insulation system that provides electrical-shock protection equivalent to double insulation.[Ref]

Double, reinforced, and basic insulations are the most important insulation types for safety isolation. The minimum spacing requirements for safety insulation are double from hazardous live to SELV—for example, 3 mm on printed-wiring board. You use functional insulation between circuits to maintain the operation of the product, but you do not rely on it for safety isolation.

You should use basic insulation between hazardous voltage circuits, but the requirement depends on the applicable safety standard, function of the product, environment, and testing.[Ref]

When a breakdown can create a hazardous voltage on user accessible conductive parts (such as in case of insulation between mains circuits and low-voltage secondary circuits), a double or reinforced insulation is required. [Ref]

• Functional insulation is that which is only
  necessary for circuit operation. It is assumed
  to provide no safety protection.
• Basic insulation provides basic protection
  against electric shock with a single level;
  however this category does not have a
  minimum thickness specification for solid
  insulation and is assumed to be subject to
  pinholes. Safety is provided by a second level
  of protection such as Supplementary
  insulation or protective earthing.
• Supplementary insulation is normally used
  in conjunction with Basic insulation to
  provide a second level of protection in the
  event that the Basic level fails. A single layer
  of insulating material must have a minimum
  thickness of 0.4 mm to be considered
  Supplementary insulation.
• Double insulation is a two-level system,
  usually consisting of Basic insulation plus
  Supplementary insulation.
• Reinforced insulation is a single-insulation
  system equivalent to Double insulation. It
  also requires a minimum thickness of 0.4 mm
  for use in a single layer. [Ref]

How does this all come togheter?

The main question is how much space do I have to have between my traces/components on my PCB to make it safe? To know there are many calculators and tables online. One example is http://creepage.com/. To be able to use these calculators or to read the tables you need to figure out all this above.

For example, we want to know the space between AC traces for a PCB that can be used in all enviroments.
If we enter this into a calculator for example creepage.com we get this:

Insulation: Basic (we know it should be basic from above)
Pollution Degree 3 (for example, we want it to work in areas where condensation occurs)
Material Group IIIa or IIIb (we know it should be IIIb from above since its a normal FR-4 PCB)
Working Voltage 250 Vrms or Vdc

Creepage is 4.0 mm or 157.5 mils
We need 4.0mm between AC circuit to be on the safe side!

Also if you have a AC (primary) hazardous side and a DC low voltage/SELV ciriut if we want to have a PCB within ALL limits we need to have reinforced insulation and then hits 8mm creepage between AC and DC side.

This is a example of a AC primary and DC secondary - but the distance is not 8mm between so it does not meet the reinforced insulation rules if you have a pollution degree of 3 or more.

More about that here:

"PCB shall be constructed so that creepage distances are not less than those appropriate for the working voltage, taking into >account the material group and the pollution degree. Hence creepage distance depends of the CTI's material (Comparative Tracking Index) and pollution degree. European main standard are for Household Appliance (EN60335) and Information technology (EN 60950). As Reference value, in the worst case (Household appliance), for reinforced insulation between High voltage (220 Vrms) and low voltage (<50Vrms) on the same layer (top or bottom), you should an 8mm creepage distance between tracks (Fig. 1) as required for standard EN 60335-1-2, table 17. These distance are lower with better CTI and Pollution degree. If you can’t maintain these distances, you need a milling (cutting of material large at least 1.5mm) between the two points that do not meet the minimum safety distances (fig.2)." (Link)

Same general tip from this article

"A minimum of 8 mm separation between primary and secondary circuits also prevents problems. "

Conclusion

First of all its important to not mix AC high voltage and DC low voltage systems. These should be seperated with a "reinforced insulation".
Assuming MySensors nodes are normally in a normal indoor enviroment (Pollution dgr 2) we need to have atleast 5,0mm seperation between AC circuit and DC circuit if you are using 240v.

Also the distance inside the AC circuit between the high voltage traces should be 2,5mm since this insulation is recommended to be "basic".

Conclusion 2

If you seal your box completely (see IP classifications) to avoid contamination from your environment you can design your board with distansens from pollution degree 1. This means pretty much clearance and creepage are the same. This means you need at 250v 0.56 mm [ref] between AC circuit (basic insulation) and 3.3mm between AC high voltage and DC low voltage. This has alot to do with material quality so I would add some extra space to be sure.

Conclusion 3

If you can’t maintain creepage distances, you need a milling (cutting of material large at least 1.5mm) between the two points that do not meet the minimum safety distances.

Disclaimer:

My disclaimer is still: I can not guarantee this info is safe! I have not made any professional tests. This is DIY and do not use this if you dont know what you are doing. It may hurt or kill you and damage your property. This thread is more of a question and discussion than a statement. Do not reference this thread. My goal is to figure out the safest way to make a MySensors PCB and the info above might not be correct.

Other Links

http://www.denverpels.org/Downloads/Denver_PELS_20090915_Aldous_Insulation_Coordination.pdf)
http://blog.optimumdesign.com/clearance-and-creepage-rules-for-pcb-assembly
http://learnemc.com/pcb-layout
http://www.itesafety.com/en_e3.pdf
http://sisko.colorado.edu/CRIA/FILES/REFS/Electronics/IPC_2221A.pdf
https://en.wikipedia.org/wiki/Insulator_(electricity)

The end?

Please add your thoughts, questions and most of all knowledge to this thread. I will update the first post to make it easy to find info. Try to keep it in a amature language and avoid technical terms without explaining them.

"Update - please use https://forum.mysensors.org/topic/2740/easy-newbie-pcb-for-mysensors to discuss this PCB"

Hello!

I have created my own PCB.
This is a PCB that only contains the basic functions for MySensors but is somewhat dynamic.
The main goal was to eliminate the build time soldering wires between the Arduino Pro Mini and the Radio.
Its a PCB for all newbies that wants to do basic nodes like myself out there...

It is a PCB for all that only wants the basic part of MySensors documented in the website!
This cuts my work with one node from a couple of hours soldering wires to 20-30min

All info can be found @ https://www.openhardware.io/view/4

This post is archived!
Please use this thread to post questions:

https://forum.mysensors.org/topic/2783/in-wall-ac-dc-pcb-for-mysensors

Project can be found here:
https://www.openhardware.io/view/13/In-Wall-ACDC-Pcb-for-MySensors

Hi!

As i mentioned in another post i had this idea to stack two PCB on top of each other to fit inside a wall appliance box. This idea has evolved (see below).

Im aware of the big security risk here, and have tried to read:

• http://forum.mysensors.org/topic/1607/safe-in-wall-ac-to-dc-transformers
• http://forum.mysensors.org/topic/1540/110v-230v-ac-to-mysensors-pcb-board

EDIT 03/1/2016
After discussion on this here are the findings of this thread (as of now):

I will update this post with BOM and eagles files as soon as i get a node running.

...............................
BOM/README: http://1drv.ms/1kCzue5
GERBER: InWallMySensor3.0.rar
EAGLES: InWallMySensor3.0Eagles.rar
Build images: http://1drv.ms/1lsleox
...............................

If you are using this design, please know about the risks when you work with high power. This design has no guarantee s so use it on your own risk!

Some weeks ago I made a video with my children and i had this idea to do something with electronics... so mostly as a testproject I made a introduction video for EasyPCB. I kinda like it... but my English isnt the best in some places.

https://youtu.be/pZTy71tRa1s

Today I introduced my 5 year old to soldering...

Everything is moving along slowly...

Today i tested the relay function, the AC - DC (HLK) and if everything fitted inside the 3d box.

Found some issues with the relay... it opens ok, but I cant close it again so the relay remains open... I need to figure out (or ask) if there is something wrong with my schematics or if the relay I used was bad.

Also I have to add some mm on the 3dbox in the holes for the relay and HLK.

I have uploaded some images and the eaglesfiles - but I would not recommend to create any pcbs yet - im not satisfied with the result and things will change on the layout and other.

I think we need a thread (and it would be fun) where old and new users can post a picture with a small text with "look what I did today". Its a steal from another forum i watch but its a really fun thread to follow like-minded people in their daily work.

The rules are simple - keep it simple with one picture (or a few) with a small text including a small explanation. If you want to comment on a particular post please create a new thread ("Reply as topic") or keep it really short. The idea is to get a flow with pictures. It does absolutely not needs to be a finished project - it can be a sketch of an idea or a process of something. Anything you can take a picture off from the MySensors / Home automation world.

I hope this is not violating any forum rules and if it does, please remove - but I think this can be a fun addition to the forum.

Let me start!

Today i created a second motion detector based on Slim Node from @m26872. Its a 1mhz bootloader and modified hc-sr501(3.3v "hack"). Its currently "deployed" in my kitchen (replaced the old one) in the spice-rack above the stove... low WAF but high camouflage! Might work

Just dropping a small project i made here for the upcoming season.

Its a motion and distance combined sensor sitting besides my robotic lawn mower. Whenever there is a movement it measures the distance, and therefore I can see if my mower is out or charging.

Why not only a motion detector - well I have alot of other things happening in the shed as well (cats, children, rabbits) and i also wants to know if the mower is charging or out cutting gras.

With a small lua script in Domoticz i hope to achieve a push notise whenever its trapped outside for to long.

Its made of my EasyPCB, a Arduino Pro mini 5v, Nrf24l01+ radio, HC-SR04 distance sensor and HC-SR501 motion sensor.

Code for 2.0

// Enable debug prints
#define MY_DEBUG

// Enable and select radio type attached
#define MY_RADIO_NRF24
//#define MY_RADIO_RFM69

// #define MY_NODE_ID 12

#include <SPI.h>
#include <MySensors.h>
#include <NewPing.h>
  
#define DIGITAL_INPUT_SENSOR 3   // The digital input you attached your motion sensor.  (Only 2 and 3 generates interrupt!)
#define CHILD_ID 1   // Id of the sensor child
#define CHILD_ID_DIST 2
#define TRIGGER_PIN  6  // Arduino pin tied to trigger pin on the ultrasonic sensor.
#define ECHO_PIN     5  // Arduino pin tied to echo pin on the ultrasonic sensor.
#define MAX_DISTANCE 300 // Maximum distance we want to ping for (in centimeters). Maximum sensor distance is rated at 400-500cm.

// Initialize motion message
MyMessage msg(CHILD_ID, V_TRIPPED);

// Initialize distance message
NewPing sonar(TRIGGER_PIN, ECHO_PIN, MAX_DISTANCE); // NewPing setup of pins and maximum distance.
MyMessage msgdist(CHILD_ID_DIST, V_DISTANCE);
int lastDist;
boolean metric = true;
int oldTripped = 0;
int tripped = 0; 
unsigned long lastRequest = 0;

void setup()  
{  
  pinMode(DIGITAL_INPUT_SENSOR, INPUT);      // sets the motion sensor digital pin as input
  metric = getConfig().isMetric;
}

void presentation()  {
  // Send the sketch version information to the gateway and Controller
  sendSketchInfo("Distance and Motion", "1.3");

  // Register all sensors to gw (they will be created as child devices)
  present(CHILD_ID, S_MOTION);
  delay(100);
  present(CHILD_ID_DIST, S_DISTANCE);
}

void loop(){     

unsigned long now = millis();

//Read digital motion value
tripped = digitalRead(DIGITAL_INPUT_SENSOR);
if (tripped != oldTripped){
  lastRequest = now;
  
  // Distance?
  int dist = metric?sonar.ping_cm():sonar.ping_in();
  Serial.print("Ping: ");
  Serial.print(dist); // Convert ping time to distance in cm and print result (0 = outside set distance range)
  Serial.println(metric?" cm":" in");
  if (dist == 0){
    return; //read again if 0, because 0 is error!
  }

  if (dist != lastDist) {
      send(msgdist.set(dist));
      lastDist = dist;
  }
   // Motion?
  send(msg.set(tripped?"1":"0"));  // Send tripped value to gw 
  oldTripped = tripped;
}

if ((now - lastRequest) > (60UL * 1000UL * 60UL)){
lastRequest = now;
Serial.print("Heartbeat");
sendHeartbeat();}
}

Let me present - How NOT to deploy a MySensors Node! Here is how you do: 1) Skrew everything solid to a wall 2) Power it up and make sure you have shorted a SDA / GND or VCC on your BMP sensor just because you dont doublecheck the colors 3)Forget to enable # My debug 4)Fetch your last BMP sensor but drop it on the lawn (pitch dark outside) 5) Spend 30min with a flashligh in 5dgr C searching for the sensor and try it out once you find it. 6) Nothing works so Un-screw everything and connect it to FTDI inside at your computer, reupload the sketch with debug. - Now everything works fine (with the first sensor) for some unknown reason. 7) Skrew everything back again! Find out the BMP sensor is not working 9) Debug Serial (atleast I got to use my new logger) 10) Find out a short on the MysX connector due to bent wire.

New and old sensor - side by side.

After changing my HA and network to new location I made some changes to my workshop. Still some work in progress.

@nzbaxterman - I had the same issue with a power meter inside a metal box. I drilled a small hole trough the box, put the radio on dupont cables and outside the box and voila, worked great.

@Gerator - Nice project! How did you solve dual SPI channels for ethernet and RFM radio?

Ethernet gateway using Arduino UNO with Ethernet shield stacked JP1 should be 1-2 and JP2 2-3.

@Dirk_H - this is exactly the same for me. Are you using logic level converters?

Nice project!

@Dirk_H - I have the same issue, but I do not get softSPI to work on a Uno + Ethernet Module + RFM69. Can you confirm that softSPI works for you and Ethernet Module? What pins do you use for softSPI (analog?)

Anyone good with SPI channel analysis?

Hardware SPI (Looks great):

Software SPI (Same setup, just changed code and pins).

In the first, I can clearly see MOSI and MISO communicating on 5/6. Enable on 7.
Software SPI does not make any sense.

What im noticing is that when I connect the radio, the IRQ line on D2 is 1.0v when high and not 3.3v. Anyone who knows this is normal behaviour? Same with two different (and comfirmed working) radios. SPI logic level converter is comfirmed working and changed with same behavoir.

Edit > This is the same using normal pins and does not have anything to do with SPI. It works when not using softSPI and IRQ has this low voltage...

@mrhutchinsonmn - i dont know if this can help you but this is my homeassistant configuration with ethernet gateway:

mysensors:
  gateways:
    - device: '192.168.X.X'
      persistence_file: 'mysensors/mysensors.json'
      tcp_port: 5003 
  optimistic: false
  persistence: true
  version: '2.3'

and here is my ethernet gateway:

// Enable debug prints to serial monitor
#define MY_DEBUG

// Enable and select radio type attached
#define MY_RADIO_NRF24
#define MY_RF24_PA_LEVEL RF24_PA_MAX

// Enable gateway ethernet module type
#define MY_GATEWAY_W5100

// Enable Soft SPI for NRF radio (note different radio wiring is required)
// The W5100 ethernet module seems to have a hard time co-operate with
// radio on the same spi bus.
#if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
#define MY_SOFTSPI
#define MY_SOFT_SPI_SCK_PIN 14
#define MY_SOFT_SPI_MISO_PIN 16
#define MY_SOFT_SPI_MOSI_PIN 15
#endif

// When W5100 is connected we have to move CE/CSN pins for NRF radio
#ifndef MY_RF24_CE_PIN
#define MY_RF24_CE_PIN 5
#endif
#ifndef MY_RF24_CS_PIN
#define MY_RF24_CS_PIN 6
#endif

#define MY_IP_ADDRESS 192,168,1,8   // If this is disabled, DHCP is used to retrieve address
// Renewal period if using DHCP
//#define MY_IP_RENEWAL_INTERVAL 60000
// The port to keep open on node server mode / or port to contact in client mode
#define MY_PORT 5003

// Controller ip address. Enables client mode (default is "server" mode).
// Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
//#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 254

// The MAC address can be anything you want but should be unique on your network.
// Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
// Note that most of the Ardunio examples use  "DEAD BEEF FEED" for the MAC address.
#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0x01, 0x08 //AF-A0-F2-15-3B-1C

// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300

#include <SPI.h>

#if defined(MY_USE_UDP)
#include <EthernetUdp.h>
#endif
#include <Ethernet.h>
#include <MySensors.h>

void presentation(){
}

void setup(){
}

void loop() {
}

I have now tested all SPI lines and its logic level converter individually.
To be absolutely sure the hardware worked, I desoldered the radio and wrote a arduino program sending 5v in 5 sek over the same sofwareSPI lines and 0V over 5 sek - all behaved correctly, 3.3v and 0V.

I also swapped radio, but same same...

Not really sure how to proceed. I need to get the softwareSPI working or else I cant use it as a ethernet gateway.

Is there someone here that got RFM gateway working with softwareSPI?
I dont think its the hardware anymore...
Code:

#include <SPI.h>

// Enable debug prints to serial monitor
#define MY_DEBUG

// Enable and select radio type attached

#define MY_RADIO_RFM69
#define MY_RFM69_NEW_DRIVER
#define MY_RFM69_FREQUENCY RFM69_433MHZ // Set your frequency here
//#define MY_IS_RFM69HW

#define MY_SOFTSPI
#define MY_SOFT_SPI_SCK_PIN 14
#define MY_SOFT_SPI_MISO_PIN 16
#define MY_SOFT_SPI_MOSI_PIN 15

#define MY_RFM69_CS_PIN 6
#define MY_RFM69_IRQ_PIN 2

#define MY_SIGNING_ATSHA204
#define MY_SIGNING_ATSHA204_PIN A3
#define MY_SIGNING_REQUEST_SIGNATURES
#define MY_SIGNING_WEAK_SECURITY 

// Enable serial gateway
#define MY_GATEWAY_SERIAL

#include <MySensors.h>

void setup()
{
    // Setup locally attached sensors
}

void presentation()
{
    // Present locally attached sensors
}

void loop()
{
    // Send locally attached sensor data here
}