This past week I've made two PCBs for my Tiny13 project (IR Proximity alarm), and still can't get it working quite right. The first board was a sloppy rush job, small and thin traces, couldn't do much to re-working on it, so scrapped it. The second one, I took my time, made sure I had extra room if I needed to add or change anything. Made very sure everything was the same as the breadbord circuit. Only had to reverse one LED...
The problem is noise or crosstalk on the PCB. The IR emitter flashes a little over 38kHz, the reciever module is working right, but the Tiny13 is constantly triggered. The program and circuit works great on the breadboard, but on the PCB the LEDs never stop. Put a delay loop in the wait-for-input routine, so I know it's not malfunctioning. I can pull the chip off the PCB, plug it into the breadboard circuit, works fine.
I'd post the schematic, but its kind of a rough, minimal sketch likely to generate some unpleasant responses. I'm looking for a more general reason why something could work fine on a breadboard, but have signal problems on a PCB.
The problem is noise or crosstalk on the PCB. The IR emitter flashes a little over 38kHz, the reciever module is working right, but the Tiny13 is constantly triggered. The program and circuit works great on the breadboard, but on the PCB the LEDs never stop. Put a delay loop in the wait-for-input routine, so I know it's not malfunctioning. I can pull the chip off the PCB, plug it into the breadboard circuit, works fine.
I'd post the schematic, but its kind of a rough, minimal sketch likely to generate some unpleasant responses. I'm looking for a more general reason why something could work fine on a breadboard, but have signal problems on a PCB.