Recent Posts

Pages: 1 ... 8 9 [10]
91
Designer Troubleshooting and Help / Re: Trouble connecting to F16V3
« Last post by tbone321 on January 20, 2019, 02:45:53 PM »
That is exactly how I was planning on setting it up. Controller connected to Pi, Pi using WiFi.


Ok, then the cabling is simple, a single Ethernet cable between the PI and the F16.  As for configuration, the only thing that you need to do on the PI is to make sure the Route Between Interfaces box on the network screen is checked.  On the F16, there is no need for WIFI to be inabled so just clear any of those settings boxes.  On the Ethernet configuration set as follows.  IP 192.168.10.75  Mask 255.255.255.0, Gateway 192.168.10.74 and DNS can also be 192.168.10.74.  These settings along with the ones currently on the PI create a show network of 192.168.10.0 capable of carrying 254 hosts.  You don't really need that many but it is easy to create that way.  Checking the Route between Interfaces box turns the PI into a small router and allows the F16 to get to the outside world.

Now the only issue is to tell the PC how to get to the F16.  If you try and access the PI, it's WIFI is on the same network as your PC so it can directly talk to it.  When you try and communicate with the F16, it is on a different network and the PC knows it needs to be routed so it sends the packet to the only path it currently knows, the default Gateway which is your home router.  The problem is that your home router knows nothing about your show network so the packets are currently dropped.  The router that needs to be used is the PI it is connected to so something needs to tell it how to get there.  There are two ways to do it. One is to set a static route on the home router.  This tells your home router how to get their and the primary advantage is that any device can on your home network can get to the show network.  The disadvantages are that not all home router let you do that and when you do, you weaken the security on your home network because now anything on the show network can also access everything on your home network.  The second way is to directly tell the PC how to get there and that is done with the route command from the cmd line.  the disadvantage is that only that PC will he able to access the show network from your home network but the advantage is that it is easy to do and maintains the security of your home network because only your PC is exposed from the show network.  Make sure that when you run cmd, that you run it as an administrator or the command will not work.  The command is route add -p 192.168.10.0 mask 255.255.255.0 192.168.1.74.  This tells the PC to send any packets for the show network to the WIFI port of your PI rather than your home router.  The -p simply makes the route persistent which means the PC keeps it after a reboot.  Give it a shot and let us know what happened.
92
Display Items / Re: DIY LED Express Power Injection
« Last post by Powelln on January 20, 2019, 02:44:49 PM »
I gave up on the power tee. I tried a few ways and never got it to work. At one point I thought it was a polarity issue and switched only to blow out pixels. I've replaced the pixels, I'm curious about Jim's idea because still only having one connection to the controller would be nice.
How do you loop power like that back? Take the power and ground leads from the end of the strands and just loop them back in to the power and ground of the beginning? Here in the pacific northwest I need waterproof.
93
Falcon PiCap / Re: Using the built-in audio jack
« Last post by Todd on January 20, 2019, 02:10:46 PM »
if you have connected your pixels directly to your gpio-pins (or with a pi-hat), then the built-in audio doesn't work anymore. You cn use a cheap usb->audio dongle to get audio again. You can buy these for a couple of dollars.
The 3.5 jack is disabled when using these methods.
94
F48 Pixel Controller / Re: power and wire
« Last post by Todd on January 20, 2019, 02:07:51 PM »
I use those when I make my own long cords. It's the brand my local home improvement center sells. They work fine.
95
Correct, you do not get "bonus" ports for doing it this way.
96
Designer Troubleshooting and Help / Re: Trouble connecting to F16V3
« Last post by K-State Fan on January 20, 2019, 02:00:23 PM »
The IP of the wired falcon needs to be on the same subnet of eth0 on the pi. I would not worry about wireless on the Falcon if that is how it is going to be hooked up but I do not have that option on mine.       
I have attached my settings if that will help you
97
Display Items / Re: DIY LED Express Power Injection
« Last post by rstehle on January 20, 2019, 01:59:27 PM »
I don't use the "Power Injection" style of tees, rather I use the standard ones.  That way I can inject power and have it go both ways on the Pixels. 
98
Display Items / Re: DIY LED Express Power Injection
« Last post by jnealand on January 20, 2019, 01:36:39 PM »
If you want more power to the star just connect the power leads at the end of the string to the power leads at the start of the string and you should be just fine.  Power flows both ways.  Keep it simple.
99
Learning Center / Re: Newbie working on first layout
« Last post by jnealand on January 20, 2019, 12:49:39 PM »
Just continue as you are until after you get some things running.  You only have 2 ports to use with the PiCap and although you can do 100 pixels on each port I would not recommend trying to put a bunch of different props on each port.  You will have enough to learn without trying to figure out how to address multiple props.  Use the KISS prinicple (Keep It Simple & Stupid) for now.  You will get the bug and want a bigger controller in the future, but you have what you need to learn now.  If you bite off to much from the get go you will probably get overly frustrated, so just get started and then grow.
100
Falcon Player Plugins / Re: FPP v2.x plugin integration
« Last post by CaptainMurdoch on January 20, 2019, 12:47:14 PM »
OK, I moved the pluginList to its own separate git repository.  This also has the advantage that users don't have to pull in the latest FPP updates to get the updated plugin list.  In the process, I converted it to a JSON file instead of JavaScript.  The only real difference as far as plugin authors are concerned is that the file uses double quotes instead of single quotes around the strings.  The file is in a new 'fpp-pluginList' git repository which can be shared for admin.

Here's the current pluginList.json file in the repository:

https://github.com/FalconChristmas/fpp-pluginList/blob/master/pluginList.json

I also converted the plugin manager page to load the installed plugin list and installed pluginInfo.json files via the new API calls and added the calls to the API help page.  I'm going to try to get the other functions (install/uninstall/upgrade) hooked up tonight and fix the version comparison issue.
Pages: 1 ... 8 9 [10]
Back to top