K16a-b FPP setup

[Dunkelzahn]

It's my first time setting up a K16a-b in FPP (5.5) and it's not acting as I expect when I'm testing. 

I configured the outputs (see attachment) and then connected pixels to each output. When I go to channel testing and test 1 model at a time the pixels connected to the corresponding port don't light up but pixels from another port light up.

 

PT#	Model Name
1	PT16
2	PT15
3	PT14
4	PT13
5	PT12
6	PT11
7	PT10
8	PT9
9	nothing
10	nothing
11	PT6
12	nothing
13	PT5
14	nothing
15	nothing
16	PT4

Am I missing the obvious and setting FPP incorrectly? Also, the Test, Enter, Up, Down and Back buttons don't change anything on the oled. 

Any help would be appreciated.

[Poporacer]

I configured the outputs (see attachment)

Usually you shouldn't have to enter the port configurations manually, but for testing, it might make sense.

When I go to channel testing and test 1 model at a time

Can you post a screenshot of how you are testing, there are at least 3 ways that you could be testing.

the pixels connected to the corresponding port don't light up but pixels from another port light up.  Am I missing the obvious and setting FPP incorrectly?

Are you 100% certain you have the pixels connected to the port you think they should be?
Here are the port #s
You cannot view this attachment.

[Dunkelzahn]

Yes, the pixels are connected as shown in your pic.

I'm testing from the Display Testing page.

[Poporacer]

I'm testing from the Display Testing page.

Maybe an oversight, but did you Enable the test mode? And are your overlay pixel models created correctly? Can you post a screenshot of that page?

[Dunkelzahn]

Yes, I'm selecting the enable test mode checkbox.


As an example, this is actually outputting to PT1 instead of PT16 on the controller.

[Poporacer]

Are you using pigtails? Is it possible that they are in the wrong port? Can you take a plain string of pixels and connect them to port 1?
If you jump in Zoom Room, we can help you troubleshoot.

[dkulp]

Uhmmm... It's saying F16-B which is not a K16.   It sounds like the eeprom didn't get programmed correctly or isn't being detected.   Can you go to the Help -> Troubleshooting and scroll to the "FPP Cape Detect Log" section and let me know what it says. 

[Dunkelzahn]

FPP Cape Detect Log:    sudo journalctl -u fppcapedetect | tail -20

-- Logs begin at Sun 2022-09-25 21:35:55 PDT, end at Mon 2022-09-26 17:31:39
PDT. --
-- No entries --

[Dunkelzahn]

Update - It's working!

I went to the Zoom room and they were able to give me the file to flash the EEPROM.