@Anthony-Kelly You might try unplugging the omega from the dock and putting a small piece of jumper wire between the receive and transmit connectors of the connector the omega sits in (just be careful to get those and not power lines - a 1k resistor would work too, and be more tolerant of mistakes).
With the wire in place whatever you type in a serial terminal should echo back, without it the echo should stop. That would test the USB-serial distinctly from the Omega 2.
@Michael-Hebert if you mean panel like this https://www.adafruit.com/product/420 then I think you can not. This is not SPI device but "12 16-bit latches that allow you to drive the display with a 1:8 scan rate." as described by Adafruit. Also, "Keep in mind that these displays are designed to be driven by FPGAs or other high speed processors: they do not have built in PWM control of any kind." "you'll need 12 digital pins, and about 800 bytes of RAM to buffer the 12-bit color image." Without own driver/controller this panel is silly device.
As an idea only - try to use Arduino based board and Adafruit library as panel controller, and Omega2 as main unit and communicate them using SPI, I2C or UART.
Hey @Chris-Drake , in the mean time i got my omega2+ too. So mine had the LED permanent on when i plugged on , i had to do a firmware upgrade till i could work with it.
About your question what you could do because of a Hardware problem is, to take pictures of your hardware and check if you can see some soldering bridges etc. Post it here that we can help looking.
If we know what kind of hardware you have, we can give advice who is helpful for you. A picture says more than 1000 words!
About the buttons ... one is slide-able and the other is a press button. The first is power on/of the second is a reset button. But depending on your boards the reset button will not work with older/factory firmware.
So, has there been any movement on getting the expled to actually work? I can use the gpioctl but those are on/off, cannot control the amount of color to come through. All that comes back is "Segmentation Fault".
The blue Power LED indicates if there is power flowing to the Omega. Don't know if the flickering green leds are normal, but mine do the same, probably because there is not battery connected. You can read more about the Power Dock here.
Sometimes after upgrading from the stock firmware, it may take substantially longer to complete the boot process (I get this a lot when working in the office). But if the Omega's LED goes dark and you didn't cut power to it beforehand, it should be safe to power cycle in the case where it doesn't reboot.
If you don't mind I'll mark this topic as [Resolved] so others may be able to find this in the future.
@Tobias-Malm140 As far as I understand, the Vout pin is not a general power output, but specifically meant to power the ethernet transformers. It is switched on by the system only when the ethernet port has to be active, and is off otherwise to save power.
As we don't have the schematics of the Omega2 yet, I can't be sure - but from the datasheet of the MT7688 I would assume that Vout is connected to pin AVDD33_TX_P0.
So not seeing any voltage present on Vout is not necessarily a sign of the Omega not working, but just that it has not (yet) switched on the ethernet.
The case of @ccs-hello seems different, it appears his Omega2 actually has a part missing, so Vout is not connected physically to anything. Most likely, a ethernet expansion would not work correctly with his Omega2.
Yes it looks good. As i see you could use it also without an omega. Connect your Alarm door switch with your strip power source and beside your computer you could control it with the IR Control.
After when you get your omega you can use this tutorial to control your LED Strip.
Oh, ok. I will order it and reply here if it worked or not, thank you for the tipp
Thanks for the reply. The device must indeed have been running some processor-intensive stuff, though I don't know what! I have not yet figured out how to run anything yet, and the device was well past boot-up. Since the thing only acted weird that one time, I'll consider it a fluke.