Blog - All Comments

RE: Arduino just announced SEVEN new products for the Arduino®︎ UNO™︎ Q board

robogary — Sun, 29 Mar 2026 00:51:06 GMT

Nice. Going all in on the Q. I wonder if some old shields will get a makeover.

RE: Arduino®︎ VENTUNO

robogary — Tue, 10 Mar 2026 03:14:06 GMT

breathtaking hardware

"VENTUNO Q enables developers and organizations to build powerful AI-powered physical systems across multiple industries."

Any possibility to have easy to use SW tools (or AI coaches) so average Joe EEs , weekend electronic warriors, etc can whip up their own wild creations ?

RE: Arduino®︎ VENTUNO

misaz — Mon, 09 Mar 2026 17:39:57 GMT

On second picture It looks like SOM + baseboard.

RE: Arduino®︎ VENTUNO

vinayyn — Mon, 09 Mar 2026 12:00:57 GMT

[View:/cfs-file/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-14c2e51a-2f9f-46c5-b06a-5ffbf7dd98de/Arduino_AE002D00_VENTUNO_22212D00_Q_2D00_FAQs_2D00_1_2D00_1.pdf:640:360]

RE: Arduino Uno Q and DIYables 3.5in color TFT Display

robogary — Wed, 21 Jan 2026 21:43:54 GMT

thanks - will be needing to reference your discoveries in the future

RE: Arduino Uno Q and DIYables 3.5in color TFT Display

DAB — Wed, 21 Jan 2026 20:24:36 GMT

Nice post.

Are you planning an application for these devices?

RE: Arduino Uno Q: Drive MCU pins directly from MPU

JWx — Tue, 20 Jan 2026 09:20:54 GMT

Interesting! You should apply for Arduino Q roadtest btw. - it would make a really interesting roadtest...

RE: Arduino Uno Q: Drive MCU pins directly from MPU

DAB — Mon, 19 Jan 2026 19:40:45 GMT

Nice post.

RE: Arduino Uno Q: Drive MCU pins directly from MPU

robogary — Mon, 19 Jan 2026 15:15:22 GMT

Thank you. Since you brought up the topic, please could you share your idea and insights: if a project uses MCU with some sort of object recognition, how would it pass desired information to the MCP ? Would a bash command be used to write to analog input pins or registers ?

RE: Arduino FSK Shield (433MHz)

Arunasstn — Wed, 15 Oct 2025 22:15:30 GMT

where found arduino library for this shield ?

RE: TinkerCad Tutorial #1 Simple Arduino LED Blink

Prajakta123 — Thu, 25 Sep 2025 18:31:30 GMT

2 pairs of led

RE: More eyes on, to explain why

kmikemoo — Sun, 03 Aug 2025 16:31:02 GMT

I didn't see anything in the code.

Do the lower LEDs start out dim or are they bright then dim? You may need to lengthen your delay to determine this. Is the lower servo fed power or ground on a common conductor to the LEDs? It could be a voltage drop issue. I'm also wondering if you might have a "leaky" MOSFET.
(I had a replacement generator controller once where OFF wasn't really OFF. Enough current leaked through the MOSFETs that the generator would start as soon as battery power was applied to the controller.)

RE: More eyes on, to explain why

beacon_dave — Sun, 03 Aug 2025 15:27:38 GMT

pinMode setup for the bottom elevator ?

RE: Arduino Analog Input scaling

JWx — Wed, 19 Mar 2025 10:20:35 GMT

according to the datasheet, internal voltage reference of RA4M1 is more like 1.4V than 1.5V

https://www.renesas.com/en/document/dst/ra4m1-group-datasheet p. 95

Internal reference voltage input channel (min, typ, max)
1.36 1.43 1.50 V

the same issue is when using Atmega328 (Vmin = 1V, Vtyp = 1.1V, Vmax=1.2V)

I have even built Arduino calibrator once to increase measurement precision when using internal reference...

maybe some external reference of known value is needed to avoid calibrating the code for given reference voltage of the given MCU?

RE: Arduino Analog Input scaling

kmikemoo — Wed, 19 Mar 2025 02:15:08 GMT

[mention:626e6e27c407492d81c7e989443cdd1c:e9ed411860ed4f2ba0265705b8793d05] So... span error based upon the expected voltage. I don't think you're measuring anything incorrectly. You are just experiencing compounding tolerances of components. IMHO. It sounds like your span error is consistent. You can correct the displayed reading with a minor correction factor in the Arduino code. It's the temperature version of you tuning your servos for your robots. If the span error is consistent between the two Arduinos, at least you know the culprit lies in the circuitry you are connecting - and it should remain consistent enough to use the same code in different microprocessors. If it is different when you go back to the Nano, it's internal to the Arduino and each microprocessor will need to be "tuned" for the sensing circuit.

Or I'm misunderstanding the problem completely. I wouldn't rule that out.