Hi Has anyone successfully implemented LoRaWAN for long-range communication in a low-power IoT sensor network? I'm curious about the practical challenges and recommended configurations
Hi Camila, I have quite a lot of application experience with LoRaWAN as well as some other LPWA sensor technologies. Happy to discuss, can you share more info about your application? Indoor, outdoor? Public or private network server? Range needed, number of sensors, how frequently they'll transmit data, etc?
Hiii Mike , yes l’m working on an outdoor project with 5 sensors. They need to send data every 20 minutes, and I'm aiming for a range of 300 meters. I'm using a private network server. Can you share some basic setup tips and things I should watch out for as a beginner in this field?
@leeruns. Welcome,! We're happy to have you as a DevHead. Feel free to let us know what you're working on now and a bit about your technical background.
@Harry<3 Welcome,! We're happy to have you as a DevHead. Feel free to let us know what you're working on now and a bit about your technical background.
really? why so? this year there are a lot of very cheap 32-bit microcontrollers like STM32C0 series and CH32V series. the price is comparable to 8 bit microcontrollers
Ease of development for Win and Linux with its time-tested AVR-GCC toolchain. I found it very reliable for motion control/power electronics applications. Apart from this, I've well-tested drivers to reuse which saves time. AVR: Simplicity is ultimate sophistication,Note: I do use STM32
Yes, I am using KiCad since last 4 years. But not sure about advanced PCB design, for example high speed design. Does anyone have experience? One feature I wish kicad should have is multiple PCBs for one project.
KiCAD is a rockstar! There's nothing that limits it from high-speed design. Just that the high-speed design features like length-matching of differential pairs aren't very interactive and friendly but does the job. Also, I observed that there is a lot of room for optimization in layer switching, speed of routing etc. as the board goes denser (talking about anything above 12 layers)
The resolution for this I use is to make the design blocks modular(both in schematic and layout). Create several projects(sch and layout) of the blocks that you think is possibly repeatable. For example: a TPS5432 switching regulator block designed once following datasheet guidelines. Then as you want to include it in different main projects, add a hierarchical sheet and give the schematic path of that common repeatable block you created. You can apply the same layout multiple times as well in the board.
We use git source control here to navigate across projects i.e, different repositories and a common folder having all these modular block projects which can be used through hierarchical sheets. This partially addresses your problem by not making you do the same thing multiple times in multiple boards/projects.
Just schematic. For layout you got to do separately during that phase of the design. There is a inirect way to do that - replicate layout using KiCAD plugin(not an official feature yet). This plugin allows you to click on any component(in the layout) from the block you replicated and hit on the apply button through that plugin https://github.com/MitjaNemec/ReplicateLayout(i use a different flavor of this plugin customized for the use case)
The Arduino UNO R4 WiFi combines the processing power and exciting new peripherals of the RA4M1 microcontroller from Renesas with the wireless connectivity power of the ESP32-S3 from Espressif. On top of this, the UNO R4 WiFi offers an on-board 12x8 LED matrix, Qwiic connector, VRTC, and OFF pin, covering all potential