Hardware

Hi i have the W5500 with pins and board this one and Arduino Uno R3 anything i need to change? i guess i don't need that 3.3 converter right? i did the change of \Ethernet\src flashed the board now i will connect the NRF24 just like you did ? same pins? anything else I should change?

Thanks for the answers. For sure it is possible to buy an ATmega and even a full-featured debugger would be acceptable compared to the effort of porting. But still, I am very biased towards the PIC without logical or economical arguments. I did not yet work with the mysensors libraries and only browsed quickly through the github repo. Maybe someone can give me a few hints to estimate the effort deeper than just claiming it as "much workload"? What I see so far is: make the C++ code compile (translate to C with clang/llvm and compile with the XC8 compiler) create a new HAL (in hal/architecture) which seems not too much effort for making it initially working Questions: Do I see it right, that there is a linux-port available? -> I would expect much more effort to port from AVR to linux than to port it to a different MCU What about the licensing? It looks like the code is GPLv2, but in the CLA it seem that contributors need to give away their rights on the contributions and that mysensors can even redistribute the code under another license - which seems completely against the principles of the GPL. Can someone explain that in more detail?

@affordabletech Have been busy soldering today. Used pro mini with regulator and LED removed + HC-SR501 with regulator and diode removed. 18650 cell for power. The NRF24 radio us one of the bad ones from with poor range. On TX it used about 4mA but only 42uA while sleeping. Battery reporting is working well. [image: eFZHxWvb.jpg]

I stumbled across this thread while searching for something related and thought I'd resurrect it to mention my HASwitchPlate project, which utilizes an ESP8266 as a MQTT-to-Nextion gateway to act as a wall-mounted scene controller. The project includes code for the ESP8266, Nextion, and home automation platforms including Home Assistant and OpenHAB. A PCB has been developed to allow running from AC power, and 3D-printable models are provided to mount the project into a single-gang work box common in North America. The end result is a scene controller you can build yourself with all the necessary components (software, electronics, and physical enclosure) ready to download.

What about something like this: https://www.cooking-hacks.com/projects/arduino-realtime-gps-gprs-vehicle-tracking

Thanks guys, I have one of those modules I will test it out. I have been playing with a combination of 0.1uF and 10uF. It has been performing decently so far. Let's see.

@mfalkvidd Thank you, I will check out the battery page.

@mfalkvidd You mean I should try 2.4.1? I will do that today or so and report back. Thanks.

Any ideas?

@bjacobse Thanks. In the end i removed the solder that was shorting out the capacitor and it now outputs 5V. Not sure how safe it is after the overheat As an experiment I cut the track to take the LED out the circuit. This reduced the current from 2mA down to a few uA.

I really don't know, I can't help you much. My sugestion would be to back down to a simpler sketch like blink, use the standard arduino ide and try everything. Just then move to more complex projects like roller shutter.

Sorry. Forget it. It was just some misunderstanding in the mycontroller UI. I just saw that my sensors were in state "NEW" in mycontroller. I had to put it into state "REGISTERED". Don't ask me, why I thought that it worked via USB — I now think, that it never really worked, maybe i read the wrong line and saw another sensor in the list.

@mfalkvidd said in Atmega328 internal temperature sensor (yes it exists!): hwCPUTemperature() sorry, stupid question maybe, but with my 328p based sensors hwCPUTemperature() is not automatically callable using just #include <MySensors.h> --> neither with 2.2.0 nor with 2.3.0 Do I have to include /hal/architecture/AVR/MyHwAVR.h ? Cannot compile it, what path should I use in the #include statement? :white_frowning_face:

@badisensors see the earlier answers here.

@neverdie It's a new J-link but I did update it to the latest version when I unboxed it. Like you say - I must be close, but something is definitely wrong. For my next test I'll try connecting wires directly to a naked NRF module. I do have some NRF Prototype modules and some different modules other than the Ebytes. At least if they all give me the same result I know the problem has got to be at the PC/Programmer end. I do also have an ST-Link V2 which I may as well have a try with.

I'm not familiar with the Adafruit bootloader. Going to have to take a look at that. For use with MySensors, you don't use a softdevice. Take a look at this thread if you haven't already: https://forum.mysensors.org/topic/9266/guide-nrf5-nrf51-nrf52-for-beginners

I don't understand. Using the Micro:bit with MySensors is something I got working in 3 minutes with the normal NRF5 capabilities built into MySensors?

so I got my nrf52840 dongle :) I was able to run mysensors node and serial gateway using MyBoardNRF5 nrf52832 board. So far so good :) I was also able to upload the sketch using usb dfu, it required minor changes to the linker script although. But from the first tests it appears that the range of the nrf52840 dongle i less than the nrf51822 board I was using before :(