Author Topic: F16v1.03 setup in XL/NC  (Read 1791 times)

Offline FireMedic4Christ

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
F16v1.03 setup in XL/NC
« on: December 02, 2015, 08:18:53 PM »
My setup:  RPi -> FPD -> F16v1.03 x3 which programmed successfully.

All ports on the FPD setup to output pixelnet and I am able to run test patterns via the FPD.

XL/NC setup has 28 universes as E 1.31. Selecting all channels on the test page and running a test does nothing. FPD in bridge mode and output to lights checked.

Am I correct to set the controllers up as E 1.31 even though I am using pixel net?
« Last Edit: December 02, 2015, 09:37:29 PM by FireMedic4Christ »

Offline jnealand

  • Hero Member
  • *****
  • Posts: 1421
    • View Profile
Re: F16v1.03 setup in XL/NC
« Reply #1 on: December 02, 2015, 08:56:55 PM »
yes, Did click on the output to lights button in the top row?  It might be good to post a screen shot of your XL/NC setup page.
Jim Nealand
Kennesaw, GA

Offline FireMedic4Christ

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
Re: F16v1.03 setup in XL/NC
« Reply #2 on: December 02, 2015, 09:39:06 PM »
yes output to lights checked and FPD in bridge mode.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: F16v1.03 setup in XL/NC
« Reply #3 on: December 03, 2015, 07:12:26 AM »
Any reason you're not running the latest v1.04 firmware?

Offline drlucas

  • Sr. Member
  • ****
  • Posts: 321
    • View Profile
Re: F16v1.03 setup in XL/NC
« Reply #4 on: December 03, 2015, 07:16:54 PM »
I see something new came out on Nov27. I will have to read up. I'm likely not touching my 1.04 setup though until Jan 2

Offline FireMedic4Christ

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
Re: F16v1.03 setup in XL/NC
« Reply #5 on: December 06, 2015, 12:41:25 AM »
I updated the firmware to what was current at the time in early November. I will look into it, but I have things working now and really don't want to risk messing it up.

The problem came down to using multicast instead of unicast. Once that change was made, everything test fine now. I still have a channel assignment issue somewhere, but I can chase that down.

Thanks to all for the guidance.

Brian