New to FPP6.2 - Interface issue, I think?

[MasterTJ]

Sooo...

Full Disclosure...I moved from 4.6 to 6.2 this year.  All new UI has me googling like a mad person...so by all means this could be an ID10T error and its just a tick box I am not seeing but I have used the "Developer" cheat code to get all options available...I think. I have almost read the new manual cover to cover to sort this out...

On 4.6 or whatever I was on before...on "Channel Output" settings, when you changed from ETH0 to WLAN0 the Channel Outputs would change...(i.e. Eth0 > F4v3 and WLAN0 > ESPixelsticks)...but on FPP 6.2 it seems to be that no matter which interface I have it on, the outputs are the same?  Is this a bug or conceptual change? 

Need to know to eliminate a possibility that FPP still thinks I have an ESPixelstick enabled that I swore I deleted and is not setup in xLights anymore.  

I have PiCap running FPP, Port 1 - 127 pixels, Port 2 87 pixels - Total of 2 unis, one 512 other 130 (per individual settings in xLights) to a total of 642 channels. I have ETH0 run to F4v3 running ver. 2.55 (Dont see anything in change notes from .55 to .59 that would cause me any issues personally) that I am able to ping and reach the UI.  Port 1 402 pixels - Port 2 450 Pixels - Total of 5 unis all 510.  In xLights I have both setup as so, No xLights full control on either.  All models are setup to the proper channels, I use the ">model 1:1" Method.  I pushed the setup to FPP Connect.  

For Some friggin reason...F4v3 Port 1 has 125 pixels that are pushing my models out...so basically my first model is starting 125 pixels further down the string than it is supposed to.  This is true on xLights Test, FPP Test but the F4v3 UI test is fine.  When I run a sequence, same thing...its missing the first 125 pixels on strand 1.  

I've spent since yesterday afternoon through tonight making minor changes...swapping out methods of model mapping, controller settings, universe/Channel assignment and nothing works.  It's like the FPP is seeing something else that uses those 125 (375 ch) between the PiCap Port 2 and F4v3 port 1.  I am at a loss...almost give up worthy. Wipe it and start over...

If anyone has a look at my screens and sees anything that would indicate what is causing those 125 pixels to be missed please speak up.  I have no idea what to do. 

Thanks guys! 

[Poporacer]

"Developer" cheat code to get all options available...I think

Be very careful with that enabling the Developer options will give you the ability to really mess things up! They did it that way intentionally. You should normally only need the Basic level and in some instances the Advanced level, Developer level can be very dangerous (and make it difficult for people to help troubleshoot)

On 4.6 or whatever I was on before...on "Channel Output" settings, when you changed from ETH0 to WLAN0 the Channel Outputs would change...(i.e. Eth0 > F4v3 and WLAN0 > ESPixelsticks)...but on FPP 6.2 it seems to be that no matter which interface I have it on, the outputs are the same?  Is this a bug or conceptual change?

I think you might be confusing something, the outputs interface is essentially identical, just some formatting changes
You cannot view this attachment.

Total of 2 unis, one 512 other 130 (per individual settings in xLights)

Is there a specific reason for the individual settings? This is not a normal configuration.

No xLights full control on either.

Is there a reason for that? Are you manually configuring some of your ports?

I use the ">model 1:1" Method. 

The visualizer method is better.

Why do you have your Falcon configured for Universes that are not even assigned to it?

[MasterTJ]

"Developer" cheat code to get all options available...I think

Be very careful with that enabling the Developer options will give you the ability to really mess things up! They did it that way intentionally. You should normally only need the Basic level and in some instances the Advanced level, Developer level can be very dangerous (and make it difficult for people to help troubleshoot)

On 4.6 or whatever I was on before...on "Channel Output" settings, when you changed from ETH0 to WLAN0 the Channel Outputs would change...(i.e. Eth0 > F4v3 and WLAN0 > ESPixelsticks)...but on FPP 6.2 it seems to be that no matter which interface I have it on, the outputs are the same?  Is this a bug or conceptual change?

I think you might be confusing something, the outputs interface is essentially identical, just some formatting changes
You cannot view this attachment.

Total of 2 unis, one 512 other 130 (per individual settings in xLights)

Is there a specific reason for the individual settings? This is not a normal configuration.

No xLights full control on either.

Is there a reason for that? Are you manually configuring some of your ports?

I use the ">model 1:1" Method.

The visualizer method is better.

Why do you have your Falcon configured for Universes that are not even assigned to it?

1.) I was looking for something to enable a change between interfaces. I don't agree with your opinion for basic settings being a catchall so to speak. To do something simple like 'enable routing between interfaces' in order to access the UI for any hardware plugged into the eth0 interface you have to enable advanced settings.  This use to be a tick box at the bottom of the networking section so I'm sure you could see my desire to unlock everything if I feel like I am not able to see a channel that might be assigned to an interface. 

2.) I dont think I'm confusing anything, I see the format of the page is changed.  But the core function of the interface drop down is not working.  When I go to the "Channel Outputs" on the Artnet/E.131/DDP tab, if I change interface from Eth0 to WLAN, my outputs don't change like they did on the previous version I was using.  The numbers don't tally up that overlap with either of my old ESPixelSticks would still be enabled but I can't rule it out because if I choose WLAN, my F4v3 is still listed.  If I refresh the page, it reverts back to Eth0. 

3.) last year when I had 2 ESPixelSticks setup, this is the only way I could get my sticks to play.  I didn't have the ESPixelSticks setup this way but had to do it with the PiCap for some reason.  I wanted to change it back to wide open 512 x 2 and test it, but I couldn't get the F4v3 working properly, which was the first step of that cleanup process.  This is why I specified there, good catch.

4.) TBH I'm still a little hazy to exactly what this does.  The xLights documentation isn't clear and I really couldn't find anything definitive on a Google search. Does this allow the push of port data from xL to FPP?  Because F4v3 isn't in my list of FPP in FPP Connect.  Should it be even though I have it setup in Bridge? Why isn't this an option on PiCap?  I could use some help gathering what this is for?  But yes, i setup the Port Data on both F4v3 and PiCap manually. 

5.) I used visualizer for the F4v3 ports originally.  It is not available for the PiCap for some reason so I have my roofline models listed to the right. 

">model 1:1", isn't this "set start channel">Ch: 1>tick "end of model" select your model? So the universe isn't even assigned here?  That's how I have those configured...except for the first model, which is manually set to Uni 3. On PiCap it works with "set start channel">"Controller: PiCap", then "> model 1" for everything after that.  This seems to work just fine, except for the first 125 pixels. 

Do you see anything that would cause the bill pixels? If not, I'm eating 125 pixels this year and setting up.  I'm too far behind to keep messing with this and I'll figure it out after the season is over.

Thanks man, I appreciate the insight and any help you can offer.

[Poporacer]

I was looking for something to enable a change between interfaces.

But going all the way to Developer could be problematic if someone isn't careful

I don't agree with your opinion for basic settings being a catchall so to speak. To do something simple like 'enable routing between interfaces' in order to access the UI for any hardware plugged into the eth0 interface you have to enable advanced settings.

But the developers decided that due to the complexity of this type of network that it should be an Advanced level setting (not developer though)

This use to be a tick box at the bottom of the networking section so I'm sure you could see my desire to unlock everything if I feel like I am not able to see a channel that might be assigned to an interface.

Yeah, that part changed and I understand the frustration that things look/behave different. I understand that you wanted to see "everything" but that everything option will allow you to make configuration changes that will make your FPP totally useless. I have helped MANY people that had an FPP that wasn't working and after spending a lot of time tracking down the problem, it was because they had made changes in the Developer mode trying to fix things and only made it worse and harder to diagnose the problem. Not saying that you did, but from experience I have seen dozens of people thinking that unlocking "Everything" will help them solve their problem only to make it worse.

When I go to the "Channel Outputs" on the Artnet/E.131/DDP tab, if I change interface from Eth0 to WLAN, my outputs don't change like they did on the previous version I was using.

I am confused why the outputs would even change, you are not changing channel numbers just the interface that the data is being sent out, but maybe I am missing something?

I don't see this change like you mentioned. Here is 4.6 with outputs set to eth0

You cannot view this attachment.

And then changing it to wlan0

You cannot view this attachment.

They look exactly the same to me? What am I missing?

I'm still a little hazy to exactly what this does.  The xLights documentation isn't clear and I really couldn't find anything definitive on a Google search. Does this allow the push of port data from xL to FPP?

I think this is in reference to the Full xLights Control? If you don't have this enabled, then xLights will only upload the ports that you have defined and anything that isn't defined will not get "blanked out" and is useful if you have to manually configure some ports for a specialized reason. Full xLights control will make your controllers match xLights exactly and is usually the better option.

Because F4v3 isn't in my list of FPP in FPP Connect.

It typically doesn't need to be, because you use the Controller input/output upload function. FPP Connect does way more that just Input/Output configurations.

But yes, i setup the Port Data on both F4v3 and PiCap manually.

That is fine, but much easier if you let xLights do it and it eliminates a ton of problems.

I used visualizer for the F4v3 ports originally.  It is not available for the PiCap for some reason so I have my roofline models listed to the right.

I think you might have missed something? It works for me.

You cannot view this attachment.

">model 1:1", isn't this "set start channel">Ch: 1>tick "end of model" select your model? So the universe isn't even assigned here?

The Universe is actually being defined here in the background based on other settings in xLights.

Do you see anything that would cause the bill pixels? If not, I'm eating 125 pixels this year and setting up.

Not specifically, but because of your configuration (individual Universe size and model chaining) we are not seeing the entire picture with the screenshots and explanations, but if you jump in the Zoom Room, it could probably be fixed very quickly.
I know you are configuring things manually, but there are so many settings that could cause this that using xLights and Visualizer and Full xLights control eliminates almost all configuration errors.

[MasterTJ]

Hey Poporacer, 

Sorry, I just reread that and it sounded rude. I am not frustrated with you or the software in general.  Yes I was very Careful and read about anything I was changing before doing so.  

Maybe I was thinking the Network interface changing on 4.6, that is why I made the post lol.  I am racking my brain and looking at the whole setup trying to get it working.  

I am not sure on the PiCap and it not working, the Vizualizer button is just Greyed out.  

Yes, you are correct...lots of changes while troubleshooting can quickly muddy up the water.  That being said, I can put my pride aside and try the zoom room.  :-) thank you for your help.  

[Poporacer]

Sorry, I just reread that and it sounded rude.

No worries. 

Yes I was very Careful and read about anything I was changing before doing so.  

That's good, like I said, I have helped many people that have messed up FPP by changing settings while in the Developer mode.

I am racking my brain and looking at the whole setup trying to get it working. 

I would strongly suggest letting xLights manage your controllers.

I am not sure on the PiCap and it not working, the Vizualizer button is just Greyed out. 

Do you have the PiCap fully defined? (Vendor, Model, Variant like shown in my screenshot) Or do you have the Output to lights turned on?

I can put my pride aside and try the zoom room

There is no pride issue by going into the Zoom room, hell, I have gone there for help myself and I am one of the helpers. We help tons of people everyday. It is just so much easier to see the entire configuration and get immediate answers to our questions and see the results of the changes live. That way there is no back and forth over days to get the problem resolved. It usually gets resolved in just a few minutes. This time of year it is a little busy, so it might take a few minutes to get to you, but I am sure it will be much quicker than going back and forth in this forum. This might help.

[MasterTJ]

Facepalm...

I didnt have Vendor and Model filled out on the picap.  As soon as I chose FPP and PiHat...Boom Vizualizer.

Within the visualizer it is all mapped correctly. 

I checked the boxes for Full xLights Control...then uploaded models and UDP via FPP and uploaded configuration of the controllers. 

This also changed the Universes to 512 by default on the Picap...Changing the starting channel on the F4v3.  I have checked the settings on the FPP and f4v3 and they were pushed just fine.

I am at the office remoted into my home computer.  The PiCap and F4v3 are on, but I have no way to see if they are working properly.  At this point if they are not, I will go ahead and add the 125 null pixels and I will just fix this on the other side of christmas.

I will check in with resolution or not.  Thank you for showing me I am not always right hahaha.  And I heeded your warning, I will change it back to advanced settings. 

I would like to learn more about the automatic settings on the backend that happen with various settings.  When someone asks me what time it is I usually have a fully prepared explanation of how the watch was made.  This instance is no different. Is there any resources for more in depth information on the software?

[MasterTJ]

Sorry, I just reread that and it sounded rude.

No worries.

Yes I was very Careful and read about anything I was changing before doing so. 

That's good, like I said, I have helped many people that have messed up FPP by changing settings while in the Developer mode.

I am racking my brain and looking at the whole setup trying to get it working.

I would strongly suggest letting xLights manage your controllers.

I am not sure on the PiCap and it not working, the Vizualizer button is just Greyed out.

Do you have the PiCap fully defined? (Vendor, Model, Variant like shown in my screenshot) Or do you have the Output to lights turned on?

I can put my pride aside and try the zoom room

There is no pride issue by going into the Zoom room, hell, I have gone there for help myself and I am one of the helpers. We help tons of people everyday. It is just so much easier to see the entire configuration and get immediate answers to our questions and see the results of the changes live. That way there is no back and forth over days to get the problem resolved. It usually gets resolved in just a few minutes. This time of year it is a little busy, so it might take a few minutes to get to you, but I am sure it will be much quicker than going back and forth in this forum. This might help.

So yeah I am going to look at the display (scattered about my living room currently...the wife? Not a fan, my 2 yo? big fan...) and see if the changes I made just now fixed it.  Seems streamlined now.  Even my models showed up as virtual strings on the FPP hat strings...Noice.  It didnt do that on the f4v3 unfortunately...will see.  

My pride is lost mostly because I ran into something I couldn't figure out on my own...I am a pretty effective self teacher I feel like and you learn best when you figure it out on your own.  But a platform teaching is just as good.  I jumped into the zoom room before watching the video.  I will probably put zoom back on my phone and have it laying around with the airpods in once I get my show going.  If not to be much help, I will probably learn some stuff.  

Thank you for the help.  I will let you know what I find out when I get home. 

[MasterTJ]

We are all good! Everything fired up just fine and we are a go.  Rebar and a friends bucket truck are finally in my near future.  Thank you Poporacer! 

[Poporacer]

Thank you for showing me I am not always right hahaha

I am not always right either.... But you did have some ill-conceived notions, glad you were able to step back and try what I was suggesting (I might have done it a time or two?)

And I heeded your warning, I will change it back to advanced settings. 

If you are careful, then no problem, but in reality, there is nothing in the Developer view that you will need.... unless you are testing/developing the code base.

Is there any resources for more in depth information on the software?

The GitHub repository

It didnt do that on the f4v3 unfortunately...will see.  

The Falcons are limited in the number of Virtual Strings so by default it won't split them unless needed and list one entry per port.

My pride is lost mostly because I ran into something I couldn't figure out on my own

Think of it this way... There is NOTHING that you are figuring out on your own in reality... you have looked in a book, took a class etc. Figuring it out is identifying the correct resource and using that information. The Zoom Room won't fix your problem, but show you how to fix it...

I will probably put zoom back on my phone and have it laying around with the airpods in once I get my show going.  If not to be much help, I will probably learn some stuff. 

I actually learned a lot when I first started by listening to the Zoom Room while I was building my controllers and pushing pixels.

We are all good! Everything fired up just fine and we are a go.

AWESOME! That is great. Glad to help.

[MasterTJ]

Just wanted to thank you again.  Everything is working awesome and I have filled in alot of holes that I didn't know I had in my infrastructure with the guys over at xLights Zoom Room.  It is much more streamlined than it use to be which is great.  It makes the year to year changes alot easier to implement I think.  

I am glad I decided to say something before giving up on it completely and I appreciate you being patient with me and sending me in the right direction to get it sorted. 

Cheers!