search

openeew / openeew-sensor

Hardware for an OpenEEW sensor
https://openeew.com/docs/build-sensor
Apache License 2.0
43 stars 12 forks source link

BOM and PCB files missing #3

Closed frankenstein91 closed 4 years ago

frankenstein91 commented 4 years ago

As far as I can see, only the circuit diagram is currently available, but the BoM and PCB files are still missing. But these files are already referred to in the documentation and on the website.

krook commented 4 years ago

@andygrillo

andygrillo commented 4 years ago

@frankenstein91 @krook yes sorry we only had a PDF schematic. Please look now- I added the eagle files :)

andygrillo commented 4 years ago

For now you can generate the BOM from the eagle schematic. I will clean up the BOM I have here and upload later today.

hildogjr commented 4 years ago

How about using KiCad as free schematic/layout software? There is also tool for cost BOM .

andygrillo commented 4 years ago

Yes I suppose we should stick to open source (although eagle is free for this size of board).

we used eagle because we were comfortable, but if you are ok with doing this board in Kicad, that would be awesome.

chronopoulos commented 4 years ago

+1 for kicad

perigoso commented 4 years ago

Would there be interest in a project conversion to Kicad? I want to contribute.

andygrillo commented 4 years ago

If you are willing to do this (great!), I will list out here my findings from testing the current board that we just got back from China. The important functions seem good (still testing), i.e. ESP32, UART interface, Ethernet, and most importantly SPI connection with ADXL355.

However would be good to take a look at the WS2812b circuit as I'm not able to get anything other than white right now using the Neopixels sample code, and there is a flicker with the brightness.

The UART header + 5v dc jack should probably be replaced with a USB port (type C). The issue is that some follks may not have a 3.3v FTDI module lying around - will make programming easier.

perigoso commented 4 years ago

Starting to work on it right away, there are some things that warrant some discussion, where should that happen?

krook commented 4 years ago

@gimbas The #sensors channel in Slack would probably be the right place.

hildogjr commented 4 years ago

I would propose to add "manf#" or "mpn" field to each part for the Manufacture Part Number. We can use it by KiCost for generate a automatic cost BOM.

andygrillo commented 4 years ago

I would propose to add "manf#" or "mpn" field to each part for the Manufacture Part Number. We can use it by KiCost for generate a automatic cost BOM.

Thats a great idea @hildogjr - please can you suggest this in a new issue ?