Looks as though upgrading to hardened and chromed rods is fairly inexpensive:
So, less sagging in the middle, and maybe less vibration also.
@dbemowsk For Z I have seen solutions with motors and belts so this is possible. It is just another piece to design and the motor need to be sized for both which might be a bigger problem with Y than with Z. I have never thought about it so it is just a guess.
@chbla said in Security: 433 RFX vs Mysensors security:
@nca78 I'm still deciding what to use. Pro Mini if I don't find anything better.
I'm interested in where you buy your BME680 breakout boards, there are not so many around
This looks interesting:
Seems like it might be a lot less expensive, when fitted out, than the Shapeko XXL, but a comparable build area.
For comparison, here is the Shapeko: https://shop.carbide3d.com/products/shapeoko-xl-kit?variant=42721947206
@wes Maybe your resistors don't have a high enough power rating for the current that's running through them? i.e. holding down the button heats them up and therefore changes their resistance? That might explain the slowness to react as expected after the button is released. After release, they cool off and eventually return within their expected resistance tolerance, at which point the expected behavior finally happens.
First attempt playing with the logo. I did a manual filament change from yellow to blue. Didn't have any black PLA, only ABS, otherwise I would have used black. This is more of a lithophane style which didn't do the best, but is still okay. I want to try to figure this out using paths in inkscape and exporting them to OpenSCAD. Having some trouble with that though. I'll figure it out in time.
The picture is next to a soda can so you can get an idea of the size.
From the NRF24 datasheet:
So, you should probably choose address a bit careful.
To change base address just add a define in your sketch like this (before including MySensors.h):
#define MY_RF24_BASE_RADIO_ID 0x00,0xFC,0xE1,0xA8,0xA8
Very simple solution, but I just put up a single flow (called watchdog of course) that subscribes to "hart beat" and value topics of items I am watching (in my case via openhab, but principle is the same for vanilla mqtt) and then have a "timeout node" for each item. Timeout node triggers if no message comes in in a predefined period (per item, some send data every few minutes, some every few hours) But each arduino node has defined hart-beat interval
In my case all timeouts go to a function that formats a message in format "<itemname> not seen in <timeframe>" and that is logged and sent to an email once a day. But you can as well put it into a dashboard as Yveaux showed.
I also like use of subflows whenever possible, but in my case all is happening on one flow and in two nodes, one that connects to mqtt hearbeat and one node that triggers if no data comes in (sorry I forgot the name, but it is a default node-red node)
I havent' seen but some one had the same probleme on the forum, and found the solution:
now i can download my sketch with the raspberry pi and i'm very hapy!
AllPCB it's great with DHL shipping. At least for now. It's true that the boards final price includes shipping too but it's still cheaper via DHL. Even if I have to pay VAT it's ok (19%). For the very short time to my door which is 3-4 days that's just WOW compared with 3-4 weeks via regular shipping.
@gohan I tried smart-prototyping in the past and they are pretty ok I can say but not the best compared to PCBWay for example. For cheap services and pretty decent quality I will still opt for Elecrow for example. And for pretty decent quality and very fast shipping - AllPCB - at least for now and if their prices won't go higher in the future.
Oh and AllPCB finishes the boards in 2 days for that price. Compared to EU factories it's still the cheapest - you can't beat China when it comes to that. Here in EU for the same price that AllPCB does I get ONLY 3 boards...wtf..so yeah you get the idea.
@mfalkvidd Thx for the "quick and dirty" way. This at least is a starting point, but most things around that seem really to be hard coded (MySensorsCore.h: L77: GW Address is 0 is the point where the getNodeId() finally leads to).
But if that really works there might be a way to wrap around that - but indeed this seems to be quite complicated.
And indeed, you are right that having multiple nRF-GW's was possible ever since MySensors existed.
GW to node communication is not affected by Serial / MQTT / Ethernet interface with controller. With ethernet and MQTT you could actually connect more controllers to the same gateway, even on different computers. You can also have gateway running as a service on the RPI with radio directly on the GPIO and you can connect to is from wherever you have IP communication to the RPI (if you use the ethernet) or the MQTT broker (that could also be on another network)