News:

LATEST RELEASE:  FPP 8.5.1 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/8.5

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 16900
Latest: Mr Tinker
New This Month: 16
New This Week: 2
New Today: 2
Stats
Total Posts: 135502
Total Topics: 16992
Most Online Today: 223
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 0
Guests: 207
Total: 207

Tearing / timing issue with first received universe

Started by zaicik, February 23, 2025, 01:36:33 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

zaicik

I have an problem with my F16V5, that I initially thought was some kind of tearing but might actually be a code/firmware issue.

The first received universe seemed to be displaying ahead of the rest.
Attached are two slow-mo videos that highlight the issue: they show a clear problem around... channel 510 !

Setup:
- F16v5
- WS2811 matrices (some 16x16, 8x8, and 8x32)
- protocol is Art-Net over a direct ethernet cable
- universe size: 512 (sent from MadMapper)
- I have no more than between 320 and 512 pixels / port

Setting or removing protocol synchronization doesn't change anything.
I also tried moving things around (using different ports, swapping matrices around, changing channel numbers, adjusted the new but so far undocumented transform and transmit lags and bank speed adjustment), but none worked.

My temporary diagnosis : the F16 is struggling at exactly channel 510 of the first universe it receives (and works seamlessly from there on, i.e. over 20 universes in my current config)

I have found a hack that I'm using for now :
- on the F16V5, start universe numbering at 2
- set up a single pixel fixture in MadMapper (or your software of choice), assigned to Channel 1 of Universe 1


Did I miss something ? Or is it indeed a hardware / firmware bug ?

You cannot view this attachment.
You cannot view this attachment.


algerdes

I agree with darylc in that you should contact support@pixelcontroller.com.  

For my own curiosity - are these panels or a very tight matrix?  It appears to me to be panels with 50/50 pixels.
Sequencers: Vixen3 and xLights
Players: FPP and xSchedule Controllers:  Renards - SS24/SS16; E1.31 - San Devices E682 - Falcon F16, F4, F48 - J1Sys - DIYLEDExpress E1.31 Bridges.  Much more!

zaicik

Thanks for your replies.
I will contact support, then.

Just wanted to make sure I didn't miss anything first.

@algerdes : indeed 5050 WS2811 "flexible" panels (this a prototype for an upcoming larger build... THEN it'll be 12mm bullet strands)

zaicik

Update: 

Problem solved with support@pixelcontroller.com !

This can happen when the board doesn't receive all the universes that have been declared (which was the case in my setup, where the last universe is not always being used). 
In particular the first and last universe are critical



Also worth noting: Falcon Support replied within the hour on a Sunday. Kudos!

Support FPP

+- Recent Topics

Interactive Mini golf using FPP? by Mark_M
Today at 03:50:07 AM

Cheap Amazon pixel controller by MikeKrebs
March 23, 2025, 08:10:55 PM

Light Elf Bluetooth IP65 Laser by Kap10G
March 22, 2025, 12:45:02 PM

HA MQTT plugin for single model by s1godfrey
March 20, 2025, 08:21:46 PM

Virtual Display not working? by dkulp
March 19, 2025, 11:45:01 AM

PixelOverlay-Clock - Revisited Again by jnealand
March 18, 2025, 06:00:53 PM

PixelOverlay-Clock.php works but I have questions... by datajack
March 18, 2025, 04:38:32 AM

Backup Feature not functional by efamlights
March 16, 2025, 11:58:28 AM

WS2811, Raspberry Pi 5, GPIO, could not initialize. by Ulysse-srfc24
March 16, 2025, 05:07:48 AM

K16A-B Issue by nolatron
March 15, 2025, 01:52:26 PM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod