advatek guru wanted

B

badger4543

Full time elf
Joined
Nov 7, 2019
Messages
166
Location
S.E Melbourne
hey just wondering if we have any pixlite mk2 controller users here that can give me a quick breakdown on how they setup/configure their seutp..
from how you setup your network, to how you punch in and configure settings to what you use to run your show...

obviously its abit of an open-ended question and a hell of a lot of variables but just looking to see if i can pick up any tip/tricks using these particular controllers..

im mainly having an issues with how i should be punching details into advatek assistant with the start chanels and univeses and how i marry these with xlights..

thanks in advance
 
I may have had to use the advatek assistant to originally set the static IP address of my controller, but I've used xLights to configure my Pixlite 16 LR for the last few years.
Start with plugging your controller into network that xLights PC is also on, then open xLights and click discover button under controllers. If it comes up your golden, you can proceed to configuring it from xLights. Choose the controller vendor and type and then you can assign elements to outputs.
Bonus of this is anytime you update your layout, you just upload config to controller from xLights.

Good Luck,
Rowan
 
battle79 said:
Start with plugging your controller into network that xLights PC is also on
Click to expand...
This is the most important part of using the older advateks. They will not run/configure via any router, proxy, or other trickery, whether that be xLights pushing configuration or Advatek assistant.
Your PC must be on the show network.
 
so i think ive cleared up my issue but just so im understanding correctly i have mine setup like this,

I run a rpi with fpp that I connect to via wifi (192.168.1.200) and use xlights to upload sequences ect..

then it goes from the rpi eth (192.168.2.200) out to the controllers pixlite 16 (192.168.2.198) and pixlite 4 (192.168.2.197) and run the show on .2. network

but xlights wont upload to the controller as they aren't on 192.168.1.XXX network but if i change the ip address off the controllers back to .1. network they will upload the outputs and then i can change the ip address back to the static .2. network??

would this be the same for all controllers if they were setup like this?

is there actually any benefit to having it setup as i do (which i think i just used that method because i copied someone's tutorial back when i got started) or would i find any issues if i just left it all on .1.
 
badger4543 said:
is there actually any benefit to having it setup as i do (which i think i just used that method because i copied someone's tutorial back when i got started) or would i find any issues if i just left it all on .1.
Click to expand...
There is no benefit in segregation of the network for such a small show. Just ensure your devices have static IPs within the 192.168.1.x range, and that these IPs will not be handed out by your router. (there will be an option about address scope etc)
You're using unicast, everything should be cabled (Pi, controllers etc) so it's all good there.

badger4543 said:
but xlights wont upload to the controller as they aren't on 192.168.1.XXX network but if i change the ip address off the controllers back to .1. network they will upload the outputs and then i can change the ip address back to the static .2. network??
Click to expand...
That is one option, the other option is to put the PC on the .2.x network when you want to modify it - which would be the better way - because that way you're not constantly changing xLights configuration.

badger4543 said:
would this be the same for all controllers if they were setup like this?
Click to expand...
This is purely a limitation of the Mk2 Advateks. The Mark 3's and other brands do not have this limitation.
 
Skymaster said:
There is no benefit in segregation of the network for such a small show. Just ensure your devices have static IPs within the 192.168.1.x range, and that these IPs will not be handed out by your router. (there will be an option about address scope etc)
You're using unicast, everything should be cabled (Pi, controllers etc) so it's all good there.


That is one option, the other option is to put the PC on the .2.x network when you want to modify it - which would be the better way - because that way you're not constantly changing xLights configuration.


This is purely a limitation of the Mk2 Advateks. The Mark 3's and other brands do not have this limitation.
Click to expand...

ok awesome i may look to update next year..
 
Skymaster said:
the other option is to put the PC on the .2.x network when you want to modify it - which would be the better way - because that way you're not constantly changing xLights configuration.
Click to expand...
Overkill warning: I run physically separate home and lights networks, each with their own IP range and network switch. In this configuration I have no problems making changes to PixLite (MkI) and PixLite MKII via Advatek Assistant from show PC. This is possible because my show PC has two Ethernet ports (the second one is from installing a PCI-E network adapter, although some PC motherboards do feature two Ethernet ports). Just have to remember to select the correct network adapter to see the controllers in Advatek Assistant.

The two ports allow my show PC to belong in both networks each with a different IP (e.g. Ethernet port 1 (Motherboard) for 192.168.1.x and Ethernet port 2 (PCI-E) for 192.168.2.x). Likely overkill but could be an option if separation is desired for future years. Also worth mentioning I do not have anything on the lights side that requires internet connectivity aside from the show PC itself. Downside is only the computer (or computers) connected to the lights network can communicate with controllers.
 
To further further the network situation. I also run a different network for my show but it uses a simple wireless router and switch configuration. The wireless router allows me to wirelessly connect to the show network from my desktop and make modifications when needed. Once the configurations are complete I will disconnect from the show network.

I have dedicated IP addresses for my controllers for both networks, the subnets are different but the last number is the same which makes it easier between the unique subnets (x.x.x.50). This allows consistent IPs so I can work on them inside when needed, or to use them for testing or whatever.
 
i think i have a system sorted now that ive wraped my head around it and pretty much got it down pat from the pc end.

i think i just forget process every year (thrid year in) and i dont turn on the computer till mid November and basically have to re learn it all again in a hurry haha.
 
You must log in or register to reply here.
Back
Top