Hyperion.ng - WS2812B aliexpress set does not work with Odroid N2

Hello guys,
I am struggling with making this set work with my Odroid N2. The box includes some cheap arduino clone (CH430).
I have read a lot opinions that this particular set works correctly with Hyperion on android boxes, CoreElec or LibreElec.
What is important - everything works as expected once connected to Prismatik or Ambibox on Windows machine - there is no hardware issue. The problem is only with Coreelec on Odroid N2.

Hyperion version is the latest one from repo - Hyperion 9.2.105 (2.0.0-alpha.8).
I have checked PuTTy and it looks that Odroid detects ttyUSB0, however this is rather unstable because after couple of minutes or seconds ttyUSB0 becomes unavailable and is not listed while running command /dev/tty.

My hyperion settings are:
No LED device is detected:

I believe baudrate value is correct, as I use the same in Prismatik settings in Windows environment.
When I set output path to ‘auto’ it sets the path to /dev/ttys0, which is incorrect.

Here is log:

 2021-02-02T15:46:39.072Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:141:tryOpen()) _rs232Port.open(QIODevice::ReadWrite): ttyUSB0, Baud rate [115200]bps
 2021-02-02T15:46:39.076Z [hyperiond SMOOTHING] (DEBUG) (LinearColorSmoothing.cpp:701:selectConfig()) Previous line repeats 1 times
 2021-02-02T15:46:39.076Z [hyperiond FLATBUFCONN] (INFO) Connecting to Hyperion:
 2021-02-02T15:46:39.112Z [hyperiond EFFECTENGINE] (INFO) Run effect "Rainbow swirl fast" on channel 0
 2021-02-02T15:46:39.114Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:146:tryOpen()) portName:          
 2021-02-02T15:46:39.114Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:147:tryOpen()) systemLocation:    
 2021-02-02T15:46:39.114Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:148:tryOpen()) description:       
 2021-02-02T15:46:39.114Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:149:tryOpen()) manufacturer:      
 2021-02-02T15:46:39.114Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:150:tryOpen()) productIdentifier: 0x0
 2021-02-02T15:46:39.114Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:151:tryOpen()) vendorIdentifier:  0x0
 2021-02-02T15:46:39.115Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:152:tryOpen()) serialNumber:      
 2021-02-02T15:46:39.115Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Invalid serial device name: [ttyUSB0]!'

It looks that Odroid N2 does not detect ttyUSB0 device properly. I have read that this also might have something in common with missing driver (CH340, CH341?) in the CoreElec kernel configuration.

Any ideas what exactly might be be causing the issue and what can I do to solve it?

Thank you.

Small update, I have tried once again using updated Hyperion (.106). Log is a bit different this time:

 2021-02-22T13:23:38.103Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:141:tryOpen()) _rs232Port.open(QIODevice::ReadWrite): ttyUSB0, Baud rate [115200]bps
 2021-02-22T13:23:38.139Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:146:tryOpen()) portName:          ttyUSB0
 2021-02-22T13:23:38.139Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:147:tryOpen()) systemLocation:    /dev/ttyUSB0
 2021-02-22T13:23:38.139Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:148:tryOpen()) description:       USB Serial
 2021-02-22T13:23:38.139Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:149:tryOpen()) manufacturer:      1a86
 2021-02-22T13:23:38.139Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:150:tryOpen()) productIdentifier: 0x7523
 2021-02-22T13:23:38.139Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:151:tryOpen()) vendorIdentifier:  0x1a86
 2021-02-22T13:23:38.139Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:152:tryOpen()) serialNumber:      
 2021-02-22T13:23:38.141Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) LED device: enabled
 2021-02-22T13:23:38.346Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:95:close()) Close UART: ttyUSB0
 2021-02-22T13:23:38.346Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Rs232 SerialPortError: Inappropriate ioctl for device'
 2021-02-22T13:23:38.347Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) LED device: disabled

There is Rs232 SerialPortError: Inappropriate ioctl for device’ error that is causing the problem I suppose. Any ideas if this is something solvable anyhow?

I also use a Arduino UNO CH340 clone without any issue.
I think you have some power issue.
The Arduino get his power from the USB port, the LEDs are supplied by a strong (10A?, depends of the LEDs) 5V external power supply. Do not connect the external 5V to the Arduino. Only connect Arduino GND with the external power supply GND.

The “datasheet” of Aliexpress shows 8A for 60LED/m for 5m strip.

Each LED needs 50mA:
so 50mA * 60LED/m * 5m == 15A and not 8A

You can calculate your own current draw and compare it with the power supply you got if it is enough.


Thank you for reply.
Arduino is getting power only from USB port of Odroid N2 in this case.
My connection is pretty similar to the one shown here (except Arduino powered directly from N2):


I am using 30led/m2 * 5m version so power draw is actually less than 8A.
As I stated in my previous message, there is absolutely no issue when I plug the whole set to Windows machine. Both Ambibox and Prismatik work like a charm on Windows 10. The issue is only with Odroid N2 therefore I am pretty sure this is rather software and not hardware problem.
I can only suspect that there might be some issue with the software loaded on the Arduino, not quite compatible with CoreElec or N2.

After 3 days of trying different configuration on 3 different Arduino boards I have finally managed to solve my issue.
The problem was with the faulty USB cable that was included in the set from Aliexpress. After replacing the cable everything is working as it should be.

1 Like

Thank you for reporting your reason of the issue!
It will be helpful for other users!

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.