I'm happy to say the EKG Monitoring device just dropped for the Duino programming option. I have been learning so much about nephrology and cancer of the bladder and ways to throughly monitor ongoing symptoms. That way step by step interventions can be made to effectively monitor various symptoms. I have been looking online for awhile now, somewhat watching the development and now its here. The following links are just breadcrumbs. If anyone has any suggestions about an anchoring device for the D.O.C or how to get Edgecuts to work that would be awesome. Later!
To program an OLED Display for Sleep Baby elephant EKG Monitor
https://circuitdigest.com/microcontroller-projects/diy-handheld-game-console-using-arduino-pro-micro-and-arduboy
To create the Sleeping Baby Elephant Circuit Board for Windows download (Testing Epoxy To Seal)
https://www.nextpcb.com/?code=cirdearti
Starting any Arduino Kit For The Sleeping Baby Elephant EKG Monitor
https://create.arduino.cc/editor/shellybot/c3349cd6-f065-49a4-9946-3d5d1d8fd1a5
Offline Editor Kicad program for Edgecuts and Gerber FIle downloads
https://www.rollapp.com/app/kicad
Another Parts Library
https://library.io/libraries/16378600-Sensor
I've seen lots of people ask more or less the same question, some even exactly my problem, but I haven't seen a solution or workaround.
I'd like to make a Raspberry Pi hat. The 2x20 pin connector that connects my hat's PCB to the Pi's GPIO connector has multiple pins on the same net. They are connected internally to the Pi, and I do NOT want to connect them also externally (to avoid ground loops and other nasties; arguing about the propriety of this is no help). Specifically, for example, pin 1 and pin 17 are both on the 3.3VDC net; they are already connected inside the Pi, and I do NOT want to duplicate this circuit by connecting the pins externally. Worse, I want to route traces in the area that the autorouter insists on blocking by routing a wholly unwanted track between these two pins.
I'm aware of this:
https://easyeda.com/forum/topic/Not-Connected-feature-for-unconnected-pads-in-Footprints-with-multuple-same-numbered-pads-on-PCB-03f61e1a8ed342b7a5be79e0dab765e5
Has it been fixed/added? Is there a workaround that I'm missing?
Thanks!
...R
#PCB#









