# SignalRGB sends garbage to the arduidno on launch

**URL:** <https://forum.signalrgb.com/t/signalrgb-sends-garbage-to-the-arduidno-on-launch/8822>\
**Category:** DIY Hardware\
**Created:** [October 6, 2025, 9:30pm UTC](https://forum.signalrgb.com/t/signalrgb-sends-garbage-to-the-arduidno-on-launch/8822 "2025-10-06T21:30:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zachariasz](https://avatars.discourse-cdn.com/v4/letter/z/f6c823/32.png) [@Zachariasz](https://forum.signalrgb.com/u/Zachariasz)\
**Post date:** [October 6, 2025, 9:30pm UTC](https://forum.signalrgb.com/t/signalrgb-sends-garbage-to-the-arduidno-on-launch/8822/1 "2025-10-06T21:30:41Z")

</div>

Today I noticed that SignalRGB sends some garbage sting to my arduino via serial port (namely: `[VPQ[VST[VVW[VPQ[VST[VVW[VPQ[VST[VVW[VPQ[VST[VVW[VPQ[VST[VVW[VPQ[VST[VVW[VPQ[VST[VVW[VPQ`) on launch. I would like an option to disable this behavior as it will sooner or later mess up with my protocol.

---

<div class="post-metadata">

**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\
**Post date:** [October 7, 2025, 9:03pm UTC](https://forum.signalrgb.com/t/signalrgb-sends-garbage-to-the-arduidno-on-launch/8822/2 "2025-10-07T21:03:09Z")

</div>

The team has a few theories as to what’s going on, and are looking into it.

In the meantime, do you mind submitting a ticket through [our contact page](https://signalrgb.com/contact/) so we can better track things? We might also need some log files.

Happy to look into it further!

---

<div class="post-metadata">

**Author:** ![Centrovoy](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/centrovoy/32/2063_2.png) [@Centrovoy](https://forum.signalrgb.com/u/Centrovoy)\
**Post date:** [September 21, 2026, 1:02pm UTC](https://forum.signalrgb.com/t/signalrgb-sends-garbage-to-the-arduidno-on-launch/8822/3 "2026-09-21T13:02:50Z")

</div>

Same in 2.5.74 (Win11), and worse: SignalRgb.exe keeps the port OPEN. FTDI FT230X (0403:6015) on COM3, not an RGB device: other apps get Access denied ~10 s after launch; if I release the port, it re-grabs it in 2 s (polling loop). Nothing logged, no setting. Looks like the built-in Vortx/Ministrip serial detection. It toggles DTR/RTS and writes to foreign devices, which hung my board for hours. Please match Vortx/Ministrip VID/PID only and add an option to disable serial detection.