News:

Server migration complete, Welcome to version 2.1.1

+-+-

+-User

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

+-Site Stats

Members
Total Members: 15653
Latest: Kairus
New This Month: 3
New This Week: 4
New Today: 0
Stats
Total Posts: 128399
Total Topics: 15787
Most Online Today: 36
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 0
Guests: 25
Total: 25

INK1003 strips not playing nice with F16V4

Started by battle79, December 05, 2022, 03:13:41 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

battle79

Hi Everyone,

Hoping your all going well with your setups. I am wondering if anyone else has encountered problem when using a Falcon F16V4 to run INK1003 strip.

Previous year I had 16 INK1003 strips in 4 groups of 4 controlled off 4 outputs from a Pixlite4. Worked as expected last year.

Setup this year: 24 strips (bought 8 more) in 12 up/down pairs controlled off 12 outputs from Falcon V4. Added 8 strips and 6 of them have a different colour order (Red/Green flipped)

Problem 1)
No drama, just change in controller........... As soon as any of the flipped strips are changed in the controller to any other colour order, they start to randomly flicker and display random colours. Also, they affect some of the original strip from previous year and cause it to flicker also. Change it back and problem disappears. So I'm thinking I'll need to change colour order in xLights somehow for just the 6 strips that need it, just need to research how to do that.

Problem 2)
Ignoring my colour issues, I preceeded to try playing as few sequences. Basic effects with either few pixels on or all pixels on but limited color changes work perfectly, but anything with fast moving changes or everything on and more than a couple changes causes every strand to start to flicker and display random colors with a slight dominance to the colour it's meant to be.

Short of buying another Pixlite4 more the second half of the mega tree, has anyone encountered problems like this? Or has any ideas about either fault condition I'm seeing would be welcomed greatly. I'm starting to think that the timings for the INK1003 chips could be the issue, but I can't imagine that the two controllers would be that much different in the output they produce.

If your still here, thankyou for listening to my ramblings, and with any luck I can update you soon with amazing working Megatree.

Also special mention to Shane (Buzzdude) who came around and spend 5 hours today narrowing down the faults to the above two conditions.

Regards,
Rowan

Support FPP

+- Recent Topics

FPP6.2 universes by darylc
February 03, 2023, 08:48:57 PM

help getting started, next step? by netfan
February 03, 2023, 11:27:52 AM

F16v4 Ports vs Universe Configuration Question by k6ccc
February 03, 2023, 09:32:48 AM

Need Expert Advise on F16v4 Ports vs Universe Configuration by Kairus
February 03, 2023, 09:32:33 AM

Set Time/Date by darylc
February 02, 2023, 06:09:40 PM

We moved and are and selling everything (in Boise, ID) by ybjr38@yahoo.com
February 02, 2023, 02:14:59 PM

K8-PB No network on first run by rharrington76
February 02, 2023, 01:39:47 PM

Help How I use Orange Pi with FPP by tbone321
February 01, 2023, 02:41:58 PM

No network by Steve_63
January 31, 2023, 08:17:21 PM

F48V4-NS Pixel Controller using all 12 Differential SmartReceiver ports by BirdingPix
January 31, 2023, 02:26:30 PM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod