PCB Boards for MySensors
-
Feel free to add my board as well:
http://forum.mysensors.org/topic/1857/my-sensor-node-motherboard-mysensorsnode -
Visualising 3d gerbers is available on other sites. Why repeat the effort ? Access to the gerbers or board files would be sufficient, if accompanied by some explanation or wiki about what you can do with the provided files.
As a designer I do not mind making some documentation, but storing it in an accessible location would be nice.
Github comes to mind. Links to github and recommendations on a minimum set of documents (and "proven" compatibility with the MySensor library) would be totally acceptable for me, but I would like some guidelines.
-
Here is my version of a compact board for inclusion in the list. This board is equipped with two connectors for NRF24 (so you can choose the orientation of the radio) and uses the MySensors libs. Works in five rooms in my house now.
http://forum.mysensors.org/topic/1901/my-own-board-50mm-x-30mm/38
Eagle files are added:
selfcontained low power node v1.sch
selfcontained low power node v1.brd
BOM:
selfcontained-low-power-node-v1.csv
Schematic in PDF format:
selfcontained low power node v1.pdf
A panelised version (could be cleaner but works):
selfcontained low power node v1 panelised.brdLinks to manufacturers:
https://oshpark.com/shared_projects/unP8BmuI (single boards)
http://dirtypcbs.com/view.php?share=11770&accesskey=5f9f38337641290cf017475f1b91ff81 (panelised version)My version of Optiboot for this board assumes the flashing LED is connected to pin 8 (as is on my board):
optiboot_atmega328_8Mhz_B0.hex
And here are my settings for the board.txt file:
###############
possible upload speeds: 9600, 14400, 19200, 28800, 38400, 57600, or 115200
for 8MHz we keep this slower to avoid transmission errors.
First settings are for use without a crystal, internal oscillator at 8MHz and Brown Out Detection switched off (to save batteries even more).
Second settings are for use with an external 8MHz crystal (better stability of frequency) and Brown Out Detection switched off (to save batteries even more).
###############atmega328pO4M8i.name=atmega328p Optiboot4 8MHz - internal osc. no BOD
atmega328pO4M8i.upload.tool=arduino:avrdude
atmega328pO4M8i.upload.protocol=arduino
atmega328pO4M8i.upload.maximum_data_size=2048
atmega328pO4M8i.upload.maximum_size=32256
atmega328pO4M8i.upload.speed=38400atmega328pO4M8i.bootloader.tool=arduino:avrdude
atmega328pO4M8i.bootloader.low_fuses=0xE2
atmega328pO4M8i.bootloader.high_fuses=0xDE
atmega328pO4M8i.bootloader.extended_fuses=0x07
atmega328pO4M8i.bootloader.file=optiboot/optiboot_atmega328_8Mhz_B0.hex
atmega328pO4M8i.bootloader.unlock_bits=0x3F
atmega328pO4M8i.bootloader.lock_bits=0x0Fatmega328pO4M8i.build.board=AVR_ATMEGA328P
atmega328pO4M8i.build.mcu=atmega328p
atmega328pO4M8i.build.f_cpu=8000000L
atmega328pO4M8i.build.core=arduino:arduino
atmega328pO4M8i.build.variant=arduino:standard###############
atmega328pO4M8c.name=atmega328p Optiboot4 8MHz - crystal
atmega328pO4M8c.upload.tool=arduino:avrdude
atmega328pO4M8c.upload.protocol=arduino
atmega328pO4M8c.upload.maximum_data_size=2048
atmega328pO4M8c.upload.maximum_size=32256
atmega328pO4M8c.upload.speed=38400atmega328pO4M8c.bootloader.tool=arduino:avrdude
atmega328pO4M8c.bootloader.low_fuses=0xFF
atmega328pO4M8c.bootloader.high_fuses=0xDE
atmega328pO4M8c.bootloader.extended_fuses=0x07
atmega328pO4M8c.bootloader.file=optiboot/optiboot_atmega328_8Mhz_B0.hex
atmega328pO4M8c.bootloader.unlock_bits=0x3F
atmega328pO4M8c.bootloader.lock_bits=0x0Fatmega328pO4M8c.build.board=AVR_ATMEGA328P
atmega328pO4M8c.build.mcu=atmega328p
atmega328pO4M8c.build.f_cpu=8000000L
atmega328pO4M8c.build.core=arduino:arduino
atmega328pO4M8c.build.variant=arduino:standard##########
My IDE is the Arduino IDE 1.6.5
Under the "hardware" directory I keep the following structure (now zipped): atmega328p.zip
Original files are available on GITHUB: https://github.com/GertSanders/batterybasedsensorv2
-
Here is an AC capable board (in a first tested version, although the filename says V3), it's my first actual spin of the PCB:
AC based repeater V3.sch
AC based repeater V3.brd
AC based repeater V3 partlist.txt
AC based repeater V3.pdfFor some images, look here:
http://forum.mysensors.org/topic/2374/50mm-x-50mm-board-with-different-powering-optionsI had the boards made by DirtyPcb, a link to order some if you want to test this boards is here:
http://dirtypcbs.com/view.php?share=12146&accesskey=c3a217d7f31434a5565ecf9bdf3f7dc6I use the atmega328 with the same boot loader as my red board.
Any improvements or suggestions are welcome.
It allows use of 2 AAA batteries, or 5VDC on the VCC input, or anything between 6V and 24V DC when using the step down DC DC converter or 220V AC when using the HLK-PM01.
There is a place for a 3V3 regulator (when using 5V on the Vcc circuit).
There are jumpers to swap the signal (SDA or SCL) on 2 pins, and there are jumpers to enable I2C pull up resistors if needed.
Repository for this design: https://github.com/GertSanders/ACcapableSensor
-
@meanpenugin will you maintain the topic post as new boards pop up in the thread? It's really nice with a list. If possible and @hek approves, perhaps you also could add a MYSX compliancy line with revision (1. 0 to 1.5 and sometime even higher). That way a MYSX daugherboard developer can get an overview of compliancy. I would also be great if any additional notes on MYSX daugherboard size constraints could be somehow made visible, but that would be the responsibility of the "motherboard" designer to clarify.
-
Seems like meanpenugin has not logged on for at least 7 months ...
-
I also noticed. I think I'll flex my moderator muscles and take over the topic to keep it up2date. And relinquish my powers back to Mr penguin, should he resurface.
-
Things I would keep per board:
Titel
Short description
KiCad or Eagle files
render of the PCB itself via Mayhew Labs or other Gerber viewer)
BOM in plain text form (if provided)
Boot loader used (or I just add a TXT with the name or URL of the boot loader)
TXT with what needs to be added to BOARD.TXT if Arduino IDE is used
MYSConnector version if provided
powered by BATT (y/n)
powered by 5V (y/n)
powered by DC 6v or above (y/n)
powered by 110/220V AC (y/n)
through hole components only (y/n)
SMD components used (y/n)
images of a build proces
images of completed buildsI tried to get all that on GITHUB, but my understanding of this platform fell short, so now I keep all this in Dropbox (to share between my various platforms)
A specific MySensors site (as Henrik mentioned) would be nice.
-
Hi - yea this would be nice with a own perhaps Wiki to add and remove hardware components :)
-
How about extending the webpage where MySensors Products and Partner Products are mentioned with an entry "Usersubmitted boards"
Every board could have it's name on the left and it's own webpage with all the details.
Basic data could be pulled in from a Wiki I think, so a Wiki for all board designers to drop their stuff would indeed be nice. -
I submit my baord here with the brief info key while we're waiting for something better. I'll help to supply more details then.
Full info here: http://forum.mysensors.org/topic/2067/my-slim-2aa-battery-node/67####My Slim 2AA Battery Node Board v2.0
Schematic: Yes
Build Files: Yes
Able to Modify: Yes -
NICE! :+1:
-
Looking good! Would obsolete this thread I guess. I would encourage all active forum members who design hw to submit their design there once deployed.
Will the form also have a MYSX field? Would be nice to have in order to survey compatibilities -
Ok, just as long as it is obvious for users what/how things should be tagged, so that searches are reliable. I've got bad experience from free tagging. Risk of all kinds of variants, misspellings and misinterpretation.
-
Combined with typeahead we can give a list of propositions. Just need a list of tags to add to start with... Later I will probably extract the full typeahead-list from the database using tag in other projects.
So feel free to propose pre configured tags..
AVR, SAMD, Raspberry,...MYSX,... -
Regarding MYSX tags, I would provide tags for following versions as a minimum:
No_MYSX
MYSX1.0
MYSX1.1
MYSX1.2
MYSX1.3
MYSX1.4
MYSX1.5The designers could then tag with the version they have implemented in their hardware
If the MYSX connector specification becomes (or is) the official MySensors connector spec, then I think a dedicated field where one chooses the version supported would make more sense than a free tag field.
