You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi-
Are there any tricks to using e131 input vs OPC? I thought I had it working once before but now the only LED output I see is all off. The demo mode stops so I do think it is receiving some kind of data.
I see where you mentioned before that this was an 'experimental' feature - so maybe my issue is not something you've run across yet.
I'm using Lightjams, which outputs e131 & Artnet but not OPC. I've had some success with using OLA on the Beaglebone to bridge Artnet->OPC but I've been running into some addressing limitations (and some inconsistent startup states) there, so that's not been a great total solution either.
Here's the log from ./opc-server:
[main] Demo Mode Enabled
[e131] Starting UDP server on port 5568
[udp] OPC command for 28800 LEDs cannot fit in UDP packet. Use --count or --strip-count to reduce the number of required LEDs, or disable UDP server with --udp-port 0
Starting demo data thread
[render] Starting render thread for 28800 total pixels
[main] Initializing / Updating server...[tcp] Starting TCP server on 7890
Allocating buffers for 28800 pixels (691200 bytes)
frame_size1=28800
[render] Awaiting server initialization...
[demo] Starting Demo: fade
[main] Starting LEDscape...[e131] Joined multicast group 239.255.0.0 on 192.168.1.174
[e131] Joined multicast group 239.255.0.0 on 192.168.7.2
pru_init: PRU 0: data 0xb4564000 @ 8192 bytes, DMA 0xb44e4000 / 9f700000 @ 262144 bytes
pru_init: PRU 1: data 0xa4466000 @ 8192 bytes, DMA 0xa43e4000 / 9f700000 @ 262144 bytes
String PRU0 with pru/bin/ws281x-original-ledscape-pru0.bin... OK
String PRU1 with pru/bin/ws281x-original-ledscape-pru1.bin... OK
{
"outputMode": "ws281x",
"outputMapping": "original-ledscape",
"demoMode": "fade",
"ledsPerStrip": 600,
"usedStripCount": 48,
"colorChannelOrder": "BRG",
"opcTcpPort": 7890,
"opcUdpPort": 7890,
"enableInterpolation": true,
"enableDithering": true,
"enableLookupTable": true,
"lumCurvePower": 2.0000,
"whitePoint": {
"red": 0.9000,
"green": 1.0000,
"blue": 1.0000
}
}
[demo] Stopping Demo: fade
[render] fps_info={frame_avg_usec: 21223, possible_fps: 47.12, actual_fps: 0.10, sample_frames: 1}
[render] fps_info={frame_avg_usec: 24425, possible_fps: 40.94, actual_fps: 40.70, sample_frames: 407}
[render] fps_info={frame_avg_usec: 24401, possible_fps: 40.98, actual_fps: 40.90, sample_frames: 409}
[render] fps_info={frame_avg_usec: 24526, possible_fps: 40.77, actual_fps: 40.80, sample_frames: 408}
[render] fps_info={frame_avg_usec: 24434, possible_fps: 40.93, actual_fps: 40.80, sample_frames: 408}
[render] fps_info={frame_avg_usec: 24431, possible_fps: 40.93, actual_fps: 40.90, sample_frames: 409}
The text was updated successfully, but these errors were encountered:
Hi-
Are there any tricks to using e131 input vs OPC? I thought I had it working once before but now the only LED output I see is all off. The demo mode stops so I do think it is receiving some kind of data.
I see where you mentioned before that this was an 'experimental' feature - so maybe my issue is not something you've run across yet.
I'm using Lightjams, which outputs e131 & Artnet but not OPC. I've had some success with using OLA on the Beaglebone to bridge Artnet->OPC but I've been running into some addressing limitations (and some inconsistent startup states) there, so that's not been a great total solution either.
Here's the log from ./opc-server:
The text was updated successfully, but these errors were encountered: