LSP is very controller-centric. It worries me, because I'm not sure how you change configs (LOR term) when you move stuff around on the hardware
from year to year. But there are pros and cons to this approach. So think about setting up your entire SS Hub (pixelnet) as mapping out controllers into your pixelnet universe (or universes).
For this example, we'll map out a Lynx Express (LE) and a SSC (smart string controller) set to 128 node mode with the SSC firmware programmer.
So I think setting up in LSP is just an exercise in getting all the controllers added and configured as you want. If you happen to be using the DMX out on the SS Hub, so what ... to LSP, its all PixelNet.
The SS Hub will take care of converting some pixelnet into DMX for you.
As you set up [add] each controller, you specify the type (Light Controller for LE or RGB controller for SSC) ... and the protocol selected would always be Pixelnet (assuming use of a single SS Hub and using the DMX out for your DMX channels on the SSH DMX out) ... but you'd also specify the number of channels and the starting channel (as you want them mapped out). See the attached graphic for the optimal order for entering in this information, basically bottom up, which seems backwards to me [ and if you do it top down, you'll likely end up re-doing it unless the defaults are all correct].
So for purposes of this example, lets assume were using Pixelnet Universe 1, and Pixelnet channels 1->512 for DMX. Everything in 513->4096 is for Pixelnet (SSC/Smart String Controllers only).
Lets also assume your adding a single Lynx Express/LE and a single SSC with 128 nodes, in 128 node mode.
So the LE would be Controller Type=Light Controller + Protocol=Pixelnet/Smart Strings + Zone/Universe=1 + Number of Channels=16 [which you select controller type, specify the starting pixelnet address where you want, it'll consume 16 pixelnet channels]. IF you added additional LE controllers, you would just start each at the correct address, like 17 (instead of 1) for the 2nd LE.
So the SSC would be Controller Type=RGB Controller + Protocol=Pixelnet/Smart Strings + Zone/Universe=1 + Number of Channels=128 [ start at 513 ... it'll consume 384 channels of pixelnet from the starting address you give it ].
The SS Hub which would take a range of pixelnet (say 1->512) and duplicate that into DMX512 out on SS Hub DMX out, assuming you set the jumper on SSH to use 1-512 for DMX. Again, like RJ keeps saying its still using 1-512 for pixelnet AND DMX (all the time), but if DMX jumper enabled, its also copying 1-512 into DMX out as well. Unless you want to shadow channels for some reason (program a DMX and SSC item together) ... you would map DMX into 1->512 and pixelnet into 513->4096 .
So I think you just think of it all as pixelnet. Its just the SS Hub that converts to DMX for you. From the software side, your just sending pixelnet to the hub, regardless of what happens after the hub.
If you were to use a second dongle for just DMX, you would probably set it to Universe 2, then map your Light Controller (non SS, like LE) controllers into that instead, and select Protocol as Entec DMX Pro/Lynx instead of Pixelnet. Everything else the same, and you'd have a 512 channel DMX universe to work with on the second dongle instead.
