F16V3 with 2 expansion boards at 40 fps MAX PIXELS per output?

[BirdingPix]

I have the F16V3 controller running v2.59, with 2 white v2.00 differential expansion boards attached.  See photo.

I want to run my show at 40 fps.  The spec sheet says the max pixel count per port is 680 in order to achieve 40 fps.  I have adjusted the port configuration SLIDER as follows:

(see attached photo)

MAIN BOARD (ports 1-16) = 4 pixels  [I do not use any ports on the Main board]
1st EXPANSION BOARD (ports 17-32) = 680 pixels
2nd EXPANSION BOARD (ports 33-48) = 340 pixels  (the total has to be 1024)

Will I get 40 fps on ports 17-48 ?    My thoughts now are no, since the total exceeds 680.

So maybe I need to remove the 2nd EXPANSION BOARD, and adjust the slider to simply:

MAIN BOARD (ports 1-16) = 4 pixels 
1st EXPANSION BOARD (ports 17-32) = 1020 pixels  (the total has to be 1024)

Then limit the max number of pixels on ports 17-32 to 680 pixels MAX.  This way I will get 40 fps, correct?

I would like to use both expansion boards, but this may not be doable if I want 40 fps. 

Your replies will be very much appreciated, thank you!
Dave

[Poporacer]

Will I get 40 fps on ports 17-48 ?    My thoughts now are no, since the total exceeds 680.

The specs are per port, not per bank (or combination of banks) and your highest per port count is 680, you will get 40 fps (will your viewers even tell the difference if you don't? LOL)
The per port is not the ribbon connector but the actual port #s (1-48)

[tbone321]

I don't understand what you need to accomplish.  Exactly how many nodes are you intending to have on each string that you are connecting to these ports?  Remember that this setting is for the max number of nodes being connected to each port and your two expansion cards each have connections for 4 differential receivers and each receiver having 4 string ports giving you 16 separate string ports per expansion card for a total of 32 ports to work with.  With that in mind, you could set your Max node balance to 510 per port and would be able to connect 32 500 node strings to this controller and run it at 40 frames per second.  Where some like to fully maximize the number of nodes per port, that is not really a great idea as it maximizes the possible failure risk per port and requires power injection on every string.

[BirdingPix]

Thank you both for you replies.  I now have a better understanding of the F16V3 and the expansion ports. 

I created two test sequences, both with the same identical effects but one version was created at 20 fps and the other at 40 fps.   The sequence included some fast repeating sweeps and fast rotating effect on the Christmas Tree models.  Then I uploaded to FPPv6.2 on Raspberry Pi 3B. 

The good news was that I really was able to tell a visual difference on the Christmas Tree models tested with these two sequences.  Of course in slow moving effects, you are not going to notice any difference between the 20 fps and 40 fps sequences, and the fast spinning effects looked 'ok' at 20fps, but I really did notice how much smoother everything looked at 40 fps.  It was definitely noticeable and so I will convert all my existing sequences to 40 fps over the summer.

The other good news for me is that I proved to myself that the F16V3 with 2 expansion boards will work just fine at 40 fps across all 32 expansion string ports as long as I stayed below these string length maximums:  I set the pixels slider to 4-680-340.

In the old days with the F16v2-R, I nearly fully used all 1024 ports on almost all the string ports... feeling it was very efficient and it worked very well, and back then I had no desire nor intent to do 40 fps... I was just starting out.  It all worked out very well, and I had no issues.  Of course I use power injection everywhere and the controllers are in the garage and the differential receivers are out with the power supplies next to the show elements in the yard.

So now with converting everything to 40 fps, yes... for the F16V3 I will need to adhere to the max pixel count of 680 on ports 17-32 and max of 340 on ports 33-48.  This gives me 32 string ports which will do 40 fps.  It's not enough ports for my show, and the new F48V4 will provide me an additional 48 ports at 704 pixels per string @ 40 fps... so I am set.

I now also have a better understanding of how lower pixel counts in any string is kind of a safety net for WHEN a pixel goes bad in a string... in that there may be less pixels gone out in the Show until you notice it and fix it.  In my experiences, that is quite rare to happen once its all working and tested by Thanksgiving before my Show goes 'live'.  (I hope this good trend continues!)

On a side note question... I have many Falcon Differential Receivers_v1.00... (see photos) which I have now learned have some wrong resistor value and needs some 'end of chain' fix? 

And will these Falcon Differential Receivers_v1.00 work with my new F48V4-NS controller??

THANKS SO MUCH for your help.
Dave

[darylc]

I thought it was the smart receivers 1.00 that had the resistor problem and needed the end of chain fix.  In any case, the end of chain fix was mailed out to all those who needed it automatically a few years ago.

Yes those receivers will work on the F48V4-NS, obviously you can't chain them (not even on the end of a chain)

[Bwinter]

The good news was that I really was able to tell a visual difference on the Christmas Tree models tested with these two sequences.  Of course in slow moving effects, you are not going to notice any difference between the 20 fps and 40 fps sequences, and the fast spinning effects looked 'ok' at 20fps, but I really did notice how much smoother everything looked at 40 fps.  It was definitely noticeable and so I will convert all my existing sequences to 40 fps over the summer.

I've also definitely noticed a big difference with a higher FPS (I've even gone higher than 40FPS, and have noticed a slight improvement there also).  As you noted, it's really evident in fast-moving effects.  A good examples is the last 15 seconds of this sequence: