Wanting to go wireless

[bloojoop]

in remote mode you don't need any e131 at all as it will only respond to multisync packets and play the local sequence on the sd card.  

[JonD]

I intend on getting away from E1.31 at some point, but I have had a lot of issues when I tried in the past.  My 34 port mega-tree is feed from three (maybe 4) different controllers, and I have a LOT of props with extra pixels.  Example: 98 Pixel Mini-tree built with 100ct string. Instead of cutting off the extra pixels, I just left them inside... 48 pixel snow flakes with 50ct strings... 99 pixel candy canes built with 100ct strings.  The extra pixels have always been an issue for some reason.  On my last attempt, it was suggested it might be easier just to trim the extra pixels off than deal with all the configuration issues.  I couldn't argue that suggestion, but modifying 40+ props was not high on the priority list at the time.

Between LOR residue and making the best of the recent supply chain issues, it sounds like I need to spend this year removing the duct tape and bailing wire, and try again next year.

[JonD]

Does anyone know where to pickup some M2.5 adhesive standoffs for the Raspberry Pi?  Wanting mount the Pi on top of my Meanwell power supply between the air vents.  Beginning to think M2.5s do not exist.  I have seen some forums suggest drilling the Pi to 3M, but not crazy about doing that.  Any other suggestions on how to mount the Pi to the power supply?

 You cannot view this attachment.

[jnealand]

I wonder how these wouod work.   https://www.amazon.com/SanaSight-Magnetic-Raspberry-Konnected-Accessories/dp/B0BR4KV3YW/ref=sr_1_21?crid=2VGMZRL24HKBT&keywords=standoffs+for+raspberry+pi&qid=1688572535&sprefix=standoofs+for+%2Caps%2C148&sr=8-21

I found these by searching on Amazon by searching for "standoffs for Raspberry Pi"

[jnealand]

Or here
https://www.amazon.com/100PCS-Plastic-Standoff-Locking-Adhesive/dp/B09WZWY9L3/ref=sr_1_17_sspa?crid=BU1SZ9XVJVMF&keywords=plastic+standoffs+for+raspberry+pi&qid=1688572966&sprefix=plastic+standoffs+for+raspberry+pi%2Caps%2C81&sr=8-17-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9tdGY&psc=1

[JonB256]

Jim, that made me think of all the Magnetic standoffs I have accumulated from P10 and P5 panels. With some plastic M3 nuts, they would do just the same.

[JonD]

I have some of the above M3 plastic adhesive standoffs, but minus a hammer they were not going to work.  The dimensions for the Pi openings are 2.9mm and 3mm (if spec) is too big.  I thought about sanding them down, but was hoping to find the right size.

The magnets are interesting.  I would be little concerned the magnets might slide around when moving in and out of storage.  I am leaning towards just buying a pi case and using two sided sticky tape for now, but if anyone is aware of some 2.5mm (HC-4?) adhesive standoffs please let me know.

Thanks!

[jnealand]

Jim, that made me think of all the Magnetic standoffs I have accumulated from P10 and P5 panels. With some plastic M3 nuts, they would do just the same.

I have a bag of those P10 mount too, I might try that.  I did buy some magnets with screw in hooks off Amazon and have tried mounting some 12" snowflakes on my garage door.  They did not move when opening and closing the door.  I've not committed to putting the flakes there yet, but the testing worked out fine.  Now to see what size screw fits in them.  Darn, yet another test to do.  Maybe after expo.

[JonD]

Getting a few of the new controllers running and was starting to play around.  It looks like when I place the Falcon in "Remote" mode it automatically converts over to DPP.  I was guessing I need to tell xlights to use DPP mode to match.  When I do this there is no option to assign universes to the controller.  What do I need to do continue to use the serial DMX port on the Falcon? 

Additionally, can the main FPP proxy a device on another proxy?  Jim mentioned he has a Pi on all his Falcon controllers.  I envisioned that he uses the Wifi side to attach to the controller network, and plugs the controller into the ethernet side.  In theory the Main FPP should be able to proxy into the Falcon controller Pi, and setup a proxy on Falcon controller Pi to access the Falcon Management page, but is is possible to let xlights mange everything that way?  (FPP Main to FPP Falcon Controller Pi to Falcon)

[Poporacer]

It looks like when I place the Falcon in "Remote" mode it automatically converts over to DPP.

How are you determining this? There isn't a DDP mode when you are in Remote mode.

I was guessing I need to tell xlights to use DPP mode to match

That will depend on what mode you want to use when you are NOT in remote mode.

When I do this there is no option to assign universes to the controller

That is correct, I think you do not understand the Remote mode. In remote mode, the device has the sequence saved locally (this contains all the relevant channel data) and uses that data to play the sequence. The Player (AKA Master) will send sync packets to the remote to keep it in sync.
 
E1.31/DDP protocols are used for sending the channel data to devices and will contain all of the channel data and can be quite huge sometimes and cause problems. But MultiSync (Player/Remote) does not send any channel data, just very small timing signals. So when in Remote mode, the device is not using DDP or E1.31.

What do I need to do continue to use the serial DMX port on the Falcon?

Since the Falcon will have the sequence stored locally with all of the channel data, you shouldn't need to do anything different for that to work.

Additionally, can the main FPP proxy a device on another proxy?

Sort of, but I am not quite following your logic here. A proxy is a method of "bridging networks"

In theory the Main FPP should be able to proxy into the Falcon controller Pi,

Typically the Main FPP and the Falcon Controller Pis will be on the same Subnet so no need for a proxy, I don't understand why you would not have them on the same network?

is is possible to let xlights mange everything that way?

Yes, sort of... on the Falcon controller, in the FPP Proxy IP section, enter the IP address of the Pis Wi-Fi but you also have to configure the Proxy on the Falcon Controller PI so it know what to do as well.

(FPP Main to FPP Falcon Controller Pi to Falcon)

FPP Main to FPP Falcon Controller Pi-> Handled through normal networking.
Falcon Controller Pi to Falcon-> Handled through Proxy settings.

Just a FYI, networks are typically configured to only be able to communicate with devices in the same network (AKA Subnet) But if you need to communicate with devices in a different network (like a Player/Remote configuration like you have) then you have to create a "routing scheme" to get the data to the right place. A Proxy Host is one method and probably the easiest way to implement, but there are other ways as well.

[bloojoop]

@JonD , Here is a quick drawing I put together to show how to use multiple proxies like you mentioned.  The main player would NOT proxy anything.  Of course you can use any of the Pi's as a player it would not need to be a dedicated player.  In xlights you would need to configure the correct wlan0 ip address for the fpp proxy address on each controller.  Then in fpp connect, for the 'udp out' setting, it would need to be set to proxied.
You cannot view this attachment.

[JonD]

It looks like when I place the Falcon in "Remote" mode it automatically converts over to DPP.
How are you determining this? There isn't a DDP mode when you are in Remote mode.
I was guessing I need to tell xlights to use DPP mode to match
That will depend on what mode you want to use when you are NOT in remote mode.

In "Remote" mode the Falcon does not display what protocol it is using, nor does it give you an option to select a different one.  It only lists channel start numbers and pixel count.  I was guessing it was using a default protocol in this mode, and the default was DDP.

That is correct, I think you do not understand the Remote mode. In remote mode, the device has the sequence saved locally (this contains all the relevant channel data) and uses that data to play the sequence. The Player (AKA Master) will send sync packets to the remote to keep it in sync.

I think I understand what I was missing.  Doesn't matter which protocol they are using when the file is local, as it is just reading the local file.  Universes are only used to route local channels, therefore it doesn't matter what universe it is, since it is already routed. 

I was aware the files would be local, but was assuming they still needed to be in the correct data format.  Daniel suggested a while back that I could continue use E1.31, and I was thinking I still needed to configure the protocol on both sides.  Sounds like I will need to dump the E1.31 configuration if I want to go wireless, as the E1.31 protocol is not used when the file is local.

Typically the Main FPP and the Falcon Controller Pis will be on the same Subnet so no need for a proxy, I don't understand why you would not have them on the same network?

Understand you are suggesting adding the Falcon Pi wifi to the same vlan as the Main FPP controller wifi, and leave the Falcon controller on the controller vlan.  Instead of connecting the Falcon Pi wifi to the controller network and creating a new sub-vlan for the controller.  Only issue is that Linux devices with default root passwords, and network cords laying out in the yard, doesn't meet security the requirements of working from home.  Restricted access to a single FPP controller in a locked room is one thing, but adding several in the yard changes things for me. 

I have proxied several layers deep on other systems, but was going to be surprised if FPP supported that.  Just curious if any one had tried.

[JonD]

Here is a quick drawing I put together to show how to use multiple proxies like you mentioned. 

Thank you for the drawing!  I am presently accessing all the controllers using the Main/Master FPP proxy feature.  I was able to enter the real ip address of the controller, and then set the Master FPP as the proxy device and it seems to work well.  I was wondering if you could go two proxy layers deep, but it sounds like that is not possible. 

[Poporacer]

In "Remote" mode the Falcon does not display what protocol it is using, nor does it give you an option to select a different one.  It only lists channel start numbers and pixel count.  I was guessing it was using a default protocol in this mode, and the default was DDP.

That is because it is not using any protocol...continued below.

I think I understand what I was missing.  Doesn't matter which protocol they are using when the file is local, as it is just reading the local file.  Universes are only used to route local channels

Not exactly, Universes/DDP are transmission protocols to transmit channel data from one device to another and that gets converted back to raw channel data on the controller when it is received. When playing locally, it is not using either transmission protocol since the raw channel data is already there.

I was aware the files would be local, but was assuming they still needed to be in the correct data format.

Since the only thing that the controller ultimately uses is the raw channel information it is already in the correct data format. Let me see if this explains it a little better. In xLights you create a sequence and that will have the raw channel information and depending on what format you are using (DDP/E1.31) the fseq will be converted to the proper DDP/E1.31 protocol for transmission. When the controller receives the DDP/E1.31 packets, it will convert that data back to raw channel data and use that to route the information to the correct port. This is a simplified explanation of course.

Daniel suggested a while back that I could continue use E1.31

I think this suggestion was probably to use E1.31 on some controller and Multisync on others. You really can't use both (well, the Kulp Controllers can be in remote mode AND process incoming DDP data!)

Sounds like I will need to dump the E1.31 configuration if I want to go wireless, as the E1.31 protocol is not used when the file is local.

You don't need to dump anything since neither one is being used, no channel data is being transmitted. You can leave it E1.31 or DDP, this will essentially be ignored anyway.

Understand you are suggesting adding the Falcon Pi wifi to the same vlan as the Main FPP controller wifi, and leave the Falcon controller on the controller vlan

No, I don't think that is what I am suggesting. I am not following the use case for your question. 
Let me see if this is what you want to do?

You have your FPP Player in a secure location and want to control several Falcon Controllers over Wi-Fi? Or is there something more I am not understanding here?

[Poporacer]

I am presently accessing all the controllers using the Main/Master FPP proxy feature.  I was able to enter the real ip address of the controller, and then set the Master FPP as the proxy device and it seems to work well.

I am still not clear how you have things configured?
Is this how you are doing it?
You cannot view this attachment.

I was wondering if you could go two proxy layers deep, but it sounds like that is not possible. 

I don't understand why you would need two proxies deep? I think I am missing something?

Is this what you are trying to accomplish?
You cannot view this attachment.