@jvdk I agree with the point made by @evb , why would you want to wire connect the ultrasonic node rather than the usual radio connection ? You are adding levels of complexity and power demands for what reason ?
My ultrasonic water tank node (pro-mini+rfm69) is now 2 years on the same 2xAA batteries sending in levels every hour (RTC), the only problem encountered - condensation forming a drip on the face of the ultrasonic head during very low temperatures.
@Andrew-Currie Downloaded KiCad and used it to import jBoard2.brd and output .gbr files via Plots plus the .drl file. Checked using GerbView and uploaded to PCBWay. Hopefully this will now work...
@mr_red
I have a zipped snapshot of all the 3d step/wrl models that I used to build my projects so far. It was quite some work to gather them all and align with the footprints using the kicad stepup tools. It's not complete - still needs some more work:simple_smile: but it should help you or anyone else to get started into MCAD integration using FreeCAD and kicad stepup tools. Maybe it's not very easy to start when using free tools but hey they are "FREE" so we cannot ask for more. But the nice thing is that once you get used it will be really easy to do your stuff and to go forward. Oh and FreeCAD can be so powerful after you learn it - I was really amazed what you can do with it(it has it's quirks and downsides but once you master it - oh, well...).
There's also: https://www.onshape.com/ - pretty powerful this one too and it has more advanced features than FreeCAD but the downside is that it's a cloud based solution: it's free for public documents but you never know when they will go to paid accounts only so yeah...I don't really like the idea to depend on something that it's hosted and the application is not on my PC along with the documents that I create with it. Cloud solutions have their flexibility but you're locked and you depend entirely on that hosted service.
Ok, enough talking...I uploaded the zip file here: http://www.mediafire.com/file/kzh1l9uo40cpj1u/kicad_stepup_packages.zip
@nrf24_is_hard When I sent data between an Aduino and the RPi I discovered that I have to make the the receiving and the sending structs the same size AND the variables be on 4 byte boundaries. Change your char name[15] to char name[16]
Another challenge is that the number of bytes of type int are different. If I remember correctly, Arduino Uno is 2 bytes and RPi is 4 bytes.
To make matters worse, some compilers make the least significant byte the first byte of a word and others make it the last byte of a word. eg, sending the value 1 would be received as 16777216 (0x00000001 vs 0x01000000)
There are a lot more gotcha's
OSD
