UART Plugin with seed studio EdgeBox RPI 200

[jplunkett]

Hello,

I recently obtained a Seeed Studio EdgeBox Raspberry Pi 200, and I am hoping to use QLC+ with it. The device comes with a RS485 interface which I am hoping to use with the UART plugin, but I am running into issues. I have built QLC+ from source, and I had to update the code to use the /dev/ttyACM0 port instead of the /dev/ttyAMA0 port it was defaulting to. The fixture I want to control cycles through red, green, blue, and white until I start QLC+ and then it just stays on the current color. However, I am not able to control the fixture as it just stays stuck on the color it stopped cycling at. I have added the

Code: Select all

 init_uart_clock=16000000

line to the config.txt file. Any help would be greatly appreciated! Below are some images of how I wired up the fixture to the Pi.


Link to device: https://www.seeedstudio.com/EdgeBox-RPi ... JpynEYtH_b

[GGGss]

Welcome to the community,

For the UArt interface to work, you need some settings. There are some recent posts on the forum dealing with those problems. Those solutions are all based on a standard Pi. Since your device is of the extraordinary, I'm afraid you're in the dark.
The first question would be: can you see the UArt plugin enabled in QLC+? If not, QLC+ needs to know its existence...

[mcallegari]

I have built QLC+ from source, and I had to update the code to use the /dev/ttyACM0 port instead of the /dev/ttyAMA0 port it was defaulting to.

I can't find anything in the code pointing to ttyAMA0. Can you please show me the line you changed?

[jplunkett]

I have built QLC+ from source, and I had to update the code to use the /dev/ttyACM0 port instead of the /dev/ttyAMA0 port it was defaulting to.

I can't find anything in the code pointing to ttyAMA0. Can you please show me the line you changed?

I updated the UARTPlugin init to use the ACM0 port instead of letting it determine the port to use. Before making this change, my fixture would continue in its default state of cycling through colors. After making this change, the fixture stops at a single color when launching QLC+.

Code: Select all

void UARTPlugin::init()
{
    /** Initialize the plugin variables here */
    foreach (QSerialPortInfo info, QSerialPortInfo::availablePorts())
    {
        // Only use /dev/ttyACM0
        if (info.portName() == "ttyACM0")
        {
            m_widgets << new UARTWidget(info);
            break; // Stop searching once we find /dev/ttyACM0
        }
    }
}

[jplunkett]

Welcome to the community,

For the UArt interface to work, you need some settings. There are some recent posts on the forum dealing with those problems. Those solutions are all based on a standard Pi. Since your device is of the extraordinary, I'm afraid you're in the dark.
The first question would be: can you see the UArt plugin enabled in QLC+? If not, QLC+ needs to know its existence...

Thanks for the response! I am able to see the UART plugin within QLC+ pointing to ttyACM0 which is the RS485 port interfacing with my fixture

[GGGss]

Welcome to the community,

For the UArt interface to work, you need some settings. There are some recent posts on the forum dealing with those problems. Those solutions are all based on a standard Pi. Since your device is of the extraordinary, I'm afraid you're in the dark.
The first question would be: can you see the UArt plugin enabled in QLC+? If not, QLC+ needs to know its existence...

Thanks for the response! I am able to see the UART plugin within QLC+ pointing to ttyACM0 which is the RS485 port interfacing with my fixture

Ow, boy, I don't envy you. This means hardware-signal-debug-mode-on. Do you have an oscilloscope and some resistors? How are your binary code reading skills?