Can't control lights from SE for lights attached to a pixie16 through a pixielink.

[Red Lily Way Christmas]

I did all the following

1. Changed pixie16 unit id in HU.
2. Used the PixeLink's web-based setup page to assign universe numbers to unit ids on each output on the pixielink that will match my props.
3. In the Sequencer's Preview Design window, set up props for DMX and set the universe numbers to match those assigned in step #2.
4. In Network Preferences, set up all of the universe numbers assigned in step #2 as E1.31, with the IP address of the PixieLink.
5. Ensured control lights checked in SE, noticed that the # universes are correct and checked. 
6. Play sequence, no lights attached turn on.

What do I need to look at to find what I missed?

[Mr. P]

Make sure the Control Panel is open, lights won't work unless the Comm Listener is running.

[Red Lily Way Christmas]

Mr P. Thanks for responding.  However, I do find that the CL is running.  Here is a portion of it showing the DMX universes opened.  I did forget to say that the lights work from the HU, and with the test button on the card, with its status light red, and while looking at the pixelink status page, activity running through it.

2022-05-07 06:08:53 509:DMX63      [INFO ] E1.31u63: E1.31 universe 63 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX62      [INFO ] E1.31u62: E1.31 universe 62 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX64      [INFO ] E1.31u64: E1.31 universe 64 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX65      [INFO ] E1.31u65: E1.31 universe 65 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX66      [INFO ] E1.31u66: E1.31 universe 66 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX67      [INFO ] E1.31u67: E1.31 universe 67 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX80      [INFO ] E1.31u80: E1.31 universe 80 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX81      [INFO ] E1.31u81: E1.31 universe 81 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX82      [INFO ] E1.31u82: E1.31 universe 82 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX83      [INFO ] E1.31u83: E1.31 universe 83 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX85      [INFO ] E1.31u85: E1.31 universe 85 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX84      [INFO ] E1.31u84: E1.31 universe 84 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX88      [INFO ] E1.31u88: E1.31 universe 88 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX86      [INFO ] E1.31u86: E1.31 universe 86 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX89      [INFO ] E1.31u89: E1.31 universe 89 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX87      [INFO ] E1.31u87: E1.31 universe 87 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX90      [INFO ] E1.31u90: E1.31 universe 90 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX91      [INFO ] E1.31u91: E1.31 universe 91 opened on 192.168.1.150/5568
2022-05-07 06:08:53  30:Listener   [INFO ] Listening on port 8837
2022-05-07 06:08:53 509:DMX92      [INFO ] E1.31u92: E1.31 universe 92 opened on 192.168.1.150/5568
2022-05-07 06:08:53 509:DMX93      [INFO ] E1.31u93: E1.31 universe 93 opened on 192.168.1.150/5568
2022-05-07 06:08:53  15:LOR-Reg    [INFO ] COM3 opened as Reg with speed 500K
2022-05-07 06:08:54  32:Listener   [INFO ] Connection accepted (127.0.0.1:47581)
2022-05-07 06:08:54   2:ReqHandler [INFO ] Client 127.0.0.1:47581 identified as Control Panel
2022-05-07 06:09:21  32:Listener   [INFO ] Connection accepted (127.0.0.1:10718)
2022-05-07 06:09:21   2:ReqHandler [INFO ] Client 127.0.0.1:10718 identified as Sequencer

 

Edited May 7, 2022 by Red Lily Way Christmas

[dibblejr]

What is your pixie16 starting Unit ID?

Do the props work in the Preview Playback window?

JR

Edited May 7, 2022 by dibblejr

[Red Lily Way Christmas]

Preview works.

I set the pixie16D in the hardware utility as 28 

The dmx universe for the props start in #40,  the same 40 and on from that in the pixielink config.

I did have the pixie16D in the HU as 40, then I realized those are hex values.   So I changed it thinking that must be it.

Now after changing it I'm in a control lights loop in the SE as it is explaining the CP needs to be up, which it is.  Maybe that is a separate problem not being able to control the lights from the SE.  But is x28 in the HU correct for universe 40 in the prop definitions.

 

Go SE  to control lights, but still nothing turning on

Edited May 8, 2022 by Red Lily Way Christmas
Update

[Jimehc]

The LOR Unit ID's on each PixieLink Port are consistent -

So On Pixielink Port 1 >

You will have first Pixie16 set to LOR Unit ID 01 (not 28 or 40) - and the second Pixie16 to Unit ID 11

with LOR Unit ID 01 Port 1 assigned as Universe 40 - the start of prop universes (that pixielink port will run through the next 31 Universes on that port) for a total of 32 LOR Unit Id's

Thus with LOR hex numbering - any LOR Unit ID above 20 - Does Not Exist on the PixieLink

Edited May 8, 2022 by Jimehc

[k6ccc]

Almost everything related to LOR networking has Unit IDs in Hex.  Also note that the DMX universe has no direct connection to the LOR Unit ID downstream of a PixieLink.  The Unit ID for the Pixie relates to the mapping in the PixieLink.  I am suspecting a Unit ID mismatch somewhere.  Can you post screen captures of the config of the prop in Preview Editor, the DMX settings in Network Preferences, the config of the PixieLink, and the config of the Pixie16.

Note, for posting screen captures, you are far better off to upload the images to a publicly reachable website, and post links to the image files rather than trying to upload the images to this system.  File storage space on this forum is VERY limited.

 

[Red Lily Way Christmas]

Thanks to all for responding.  All helped me think differently (and now correctly) on how this sets up.  It was the pixie16 ID I set.  It needed to be based on the pixielink, thus unit id 01, then 11 for the second pixie16 on this same pixielink port.

[dibblejr]

1 hour ago, Red Lily Way Christmas said:

Thanks to all for responding.  All helped me think differently (and now correctly) on how this sets up.  It was the pixie16 ID I set.  It needed to be based on the pixielink, thus unit id 01, then 11 for the second pixie16 on this same pixielink port.

Glad you got it. Thanks for the update.

JR