Відео

Nice Idea, but I was already doing this 25 years ago with USB-UIRT devices (albeit not as powerful). I wish you success, but I'm just waiting(/hoping) for Hue bulbs to integrate the ability to reproduce IR signals as a standard in their bulbs.

Did you copy Electronoobs or did he copy you?

AliExpress: Quite possibly the world’s biggest distributor of Straight-to-Landfill Products™️.

Hey nice video to understand basic string manipulation! What substring is more efficient in the loop function? Thanks

They have the same issue with the new Sandisk Creator Pro Portable SSD which has a speed rating of 2000MB/s. I just purchased one and tried it with my Macbook Pro M3 formatting in APFS. The Macbook M3 has 40Gb/s usb so its not the Mac that is the bottleneck. I am getting about 960MB/s. This is nuts. Many, many creators use Macs.

I have watched 3 of your videos so far and still deciding on subscribing. So far I would suggest keeping the background music level lower because it's competing with your voice. Greetings and best wishes from Bosnia.

why does the R4 wifi have a Quick Connect I2C port if it has limited I2C speeds. The logic behind the R4 series just confuses me. Yes, I do use them for certain projects, but if they instead kept making the R3 but with an ESP32 that can work with it or an affordable ESP32 like everyone else, they might actually do better. Literally the only benefit I find is a 5v pin, but most projects could just use an ESP32 shield, and if you use the Mega, you get far more pins. The R3 with a Wifi Shield is objectively better for more projects, the way they do it with two different microcontrollers on it, it just makes it far inferior to a standard ESP32 development board for most projects because of how much more difficult it is to communicate with the board.

well, I just assumed that my R4 Wifi had the specs of an R3 but with an ESP32 and that other microcontroller that I could care less about because ESP32

do you complain to Ali about fake chips or what ?

The most terrible video about pointers.....Kinding : there's a lot out there.... Your exposé is confusing, not clear at all. Be more practical. Memory operations, via pointers, are easy you just have to keep in mind what's involved when you use them and that's all!!! The first idea is : YOUR PROGRAM NEEDS A MEMORY PLACE TO BE LOADED INTO BY THE SYSTEM THAT WILL EXECUTE IT. SO THIS SYSTEM WIIL LOAD YOUR PROGRAM IN HIS MEMORY. The second idea that goes along these pointers is : USUALLY, YOUR PROGRAM NEED SOME MEMORY THAT HE DOESN'T HAVE TO WORK ON SOME DATAS. SO IT NEEDS TO HAVE IT BY THE SYSTEM IN WHICH IT IS EXECUTED But your variable isn't a pointer that your program will use to retrieve it's value from too? Sorry but as time goes by I hear different kinda-fashioned-thing about pointer that scratch my ears... Althought pointers are not so complicated to undestand, don't need a so long video to explain it's almost the dumbest thing in computers stuff...) you just need to keep in your brain these two first main thing and, this : A so called "pointer" is a variable that store a memory cell number!!! And that's it!!!! The type that all language want you to put in front/or nearby is just a matter of language : a strong typed language is just a help for the programmer to write better/bigger programs whith ease and to let you intentionally wrtite/built it.... Assembler deals with memory adress all the time but does'nt have the ease of type C (or others...) has!! But assembler is the fastest!!! But he must request an extra memory place to work with by calling a system method. How a system can run different program in its memory if all use the memory as they want : it will be a mess!!!! And that's all it's simple common sens!!!

can you overwhelm even more ? you might apply for a fucking academy award while you're at it this yet another fucking arduino

Isn't there a better/Nicer way to get clicks than "WTF"? But, thank you for this information.

The R4 has can remember more than your goldfish? Well, depends on the goldfish.

Something smells but it's not Arduino. Phew 😅

Actually an electronics device can't be insane.

I find it too boring or old fashinoned, but I like the Arduino/C++ compiler for M5Stack products. I managed to do similar stuff with some displays and more we would buy for the Arduinos. Assigning other GPIO numbers is a bit complicated.

Love to image quality & color grading of your vids. May I ask what camera & lighting setup you are using? Thanks!

Would the RTC mismatch account for a timer triggered by holding a button to take longer than intended? For instance, instead of it taking 10 seconds, it takes 10.2 seconds?

Great video!

A programmer recently told me that Javascript is a vibes-based language. Similarly, that LOCO oscillator is a vibes-based timepiece.

Hilarious. The R4 minima actually HAS all the proper pads to place a proper crystal (so you can literally buy, and add it back yourself)... but they decided to penny pinch on that!? It's not placed on the board. If it had a proper crystal, and then the RTC based on the high speed clock, it would use normal chip power, but it should be as accurate as many other RTCs. Of course most MCUs also have their 'XTAL' pins, which allows operating the chip at very low power mode with a specific 32khz external crystal, which is nice if you want battery operation with decent timing. The R4 Wifi, well they decided they needed to sacrifice the crystal-stabilized high speed clock source entirely in order to use those pins for the LED display. Hilariously, the R4 Wifi is effectively two MCUs in one, it has an ESP32-S3 onboard as well. Because that is a chip-on-board module, it comes with its own honest-to-goodness 40Mhz crystal inside the metal can, that Arduino don't believe in. So if you can program it, the ESP32-S3 MCU's timing and RTC abilities are probably streets ahead on average better than what the RA4M1 can do, simply because the latter got gimped of all crystals by the board design. If you give these chips proper crystals on either of their high speed or low speed clock pins, they will have a reasonably accurate timing/RTC just the same as any other. For this reason all the ATMega328 Arduino Unos will be roughly accurate (as you found), operating as they are from a bog standard 16Mhz crystal. But at least they were given a crystal! If you calibrate the older Unos' frequency out (i.e, software correct the initial frequency error of the crystal as it is shipped in the board), they'll probably be just as accurate as any normal quartz watch. 10 years ago, I could forgive a lot of Arduino's design mistakes/decisions. But now, to see they can't even be bothered giving their chips proper crystals for timing? It makes it very hard to want to support them with a more expensive purchase from their shop. If I buy an ESP32 or RP2040 board from China, you know what I know? All those boards will come with a crystal...

Not using the esp32 as the MCU seems insane. Arduino software support for those of fine

ShOcK & AWE. I AM OUTRAGED (that I didn't know this). GR8T story. I haven't been this intrigued since I found out my hot sister was adopted. Just saying Commendable reporting. You R 🂡🂱🃁🃑's with us

The millis() drift is interesting. Given that it is interrupt driven, I rather suspect that any sketch which calls Arduino code where interrupts are disabled temporarily, will affect the drift too. It would be interesting to know what code you used to measure millis() on the Arduino in case something there disables the interrupts. Cheers, Norm.

Interesting. I wonder if this time variance could be calibrated in a useful way. That may depend upon the device temperature variation. Nice explanation.

I commented (and then tried again) but it got deleted. Probably because I posted a link to schematics. Anyway, what I commented was: I wonder if soldering a 32.768Khz oscillator, which are dirt cheap and common as sand, found in every cheap watch and wallclock, to pin 10 would make it drift less...

Been a while since I saw a pebble watch

No computer should be used for clock reference w/o resorting to a proper clock. I use GPS if possible (1 sec tick interrupt - or faster - such as 25Hz in some applications). Properly setup I can get the interrupt in less than 100 ns (Rasp Pi, not sure for Arduino). (Stand alone RTL, no Linux). Of course with GPS you need access to a sky view. Or, use NTP for sub 10ms accuracy. Or - get a GPS disciplined oscillator - still needs a sky view.

Fantastic video! I have no intention of using the RTC on any Arduino, yet I enjoyed the video. Very well presented!

For better comparison it would be better to depicted the deviation not in absolute values (seconds per time interval) but relative in ppm (parts per million) All in all: A good video👍

We say "point" not "dot" in english for the decimal point in the context you were using it. Pi is three point one four one five dot dot dot. It is such a minor error, sorry if you don't care. Anyway, it is so disappointing for the R4 to claim to have a RTC which doesn't actually work. At this point I don't know why you wouldn't just use a rpi pico or an esp32 (with an externl RTC module if required).

how does it compare to a ds13xx RTC module?

Esp32 + time API = good clock

You are a better electritian than a programmer:) I would go for using a interrupt pin with button press and set global variable "letsFire". Than you dont need to set delays and make loop script locking. (nothing can be done during that). Then use multiple IF's to check for cap voltage, print progress to terminal, etc. Also I if possible I would not have used non-maching states of transistor swiching outputs, as you pointed out it already made scripting confusing. Other than that - great video, good editing.

RTC sells it for me 🙂

Can we connect it to a mipi or hdmi? Thats the only real major thing ive been waiting for

would love to see GRBL built for this version of arduino.

Great fun. Thanks for showing the failures, that taught me a lot about trial and error

The reason why you had to increase your output voltage might be the lower ambient temperature outside. It naturally cools the wire and prevents firing.

Great project. Learned a lot!

All those great improvements are nice but not worth the price. I'll stick to ESP32 for now.

Does anybody know what tool is being used for the visualization at 2:52 ?

Do Esp32 Lyrat Mini next time 😊

Tbh, I don't even know why to use Arduino, especially original one. Raspberry Pi Pico is much cheaper, has choice of using more SDKs (C++ cross compiler and some tools, Arduino, Micropython, maybe FreeRTOS, Zephyr, ...), extra wifi/ble is for like 1.5EUR, it has way more RAM and Flash, less EEPROM, much faster CPU. C++ and Python code can be prototyped at PC. I like Arduino Pro Mini for some battery powered projects, but I'm getting curious about Nordic Semiconductor nRF52 line.

Esphome's remote transmitter does have a repeat option you can use instead of pasting the command repeatedly.

Great idea, I'm interested!!

Why such an exotic chip? Why not STM32?

Nice feature. Turns every phone into a universal remote! Great way to integrate control of devices like this. FYI I can't fill out your form, no Australia in the country list

Good job.. to bad you didnt make for 4 or 6 chanels.. and esp32 on hedders.

I'm happy my head can content this. Very expensive. Keep it up