Pixelnet Signal from the USB Dongle with Pixelnet firmware

[TexasStingray]

Does anyone is this is correct?

Can anyone tell me if what I am seeing is correct.

I am getting this output from the USB Dongle with Pixelnet firmware.

When I set channel 1 to 50% (50% of 255 is 128) thru vixen I see this.

170
85
85
170
21
93
128       <----- I assume this is the value for Channel 1
0           <----- This is the value for the Next Channel
...
...
0           <----- The value for the last channel.

Then if I set channel 1 to 0 and 2 to 25% (25% of 255 is 64) I see this thru vixen

170
85
85
170
21
93
0           <----- I assume this is the value for Channel 1
64         <----- I assume this is the value for Channel 2
0           <----- This is the value for the Next Channel
...
...
0           <----- The value for the last channel.


This is correct?

Thanks
Scott

[dpitts]

That is correct. The EtherDongle and USB Pixelnet Dongle add the bytes between the first 170 and first data byte. Those added bytes form the start sequence. The start sequence has different bytes if it is a configuration packet from utility software.

[wftxlites]

So, from Scott's example it appears that there is always two sets of 170's. Which ones data changes and is it or is it not significant? That is depending on S/W Config Utilities. Can it just be ignored assuming the values are not changing and just watch for the start at 170 to figure out where channel 1 starts. Again, assuming you are just trying to get start @ Channel #1 and all channel values.

170
85       <----- Does this change?
85       <----- Does this change?
170                        OR
21       <----- Does this change?
93       <----- Does this change?
128      <----- I assume this is the value for Channel 1
0          <----- This is the value for the Next Channel 2
...
...
0          <----- The value for the last channel 4096.

[dpitts]

I would look for the whole start sequence (from the first 170 to the 93). It is a good error check.

[wftxlites]

I would look for the whole start sequence (from the first 170 to the 93). It is a good error check.

Yes, I agree.
 
I am a bit confused because of this description in the Pixelnet document.
"So a Pixelnet packet looks like this:
start of packet Data
Value 170 sent 4096 channels of data value 170 not allowed.
Then repeat with no delays."

Clearly from the real-time example the above is not entirely correct!

Another thing is that, is there a skip in channel numbering when you get to 170 or not?

Again from the Pixelnet Document.
"Any channel data with a value 170 is translated on the software generator (vixen plugin,
LSP plugin, etc.) to 171."

[dpitts]

That document explains how software should send Pixelnet to USB Pixelnet Dongle. Not how the dongles send Pixelnet to controllers.

[wftxlites]

Ok, then no confusion in that case. I'm only interested in the decoding of the output of the dongle at this time.

Thanks

[TexasStingray]

Thanks, got it working with my Arduino Mega. Now to test the UNO.

And the UNO works also for sending the signal also.

Thanks for the Help.

[rm357]

That document explains how software should send Pixelnet to USB Pixelnet Dongle. Not how the dongles send Pixelnet to controllers.

I think this is backwards. The 170 + 4096 data is the actual data sent to the SSCs.
The additional header data is for the usb dongle and is not transmitted.
The etherdongle is a different beast as the e1.31 packet contains a much larger header...

[dpitts]

That document explains how software should send Pixelnet to USB Pixelnet Dongle. Not how the dongles send Pixelnet to controllers.

I think this is backwards. The 170 + 4096 data is the actual data sent to the SSCs.
The additional header data is for the usb dongle and is not transmitted.
The etherdongle is a different beast as the e1.31 packet contains a much larger header...

That is not my experience.

[TexasStingray]

From what everyone is saying I have drawn the following conclusion. Using the signal values i have posted this is the signal to RUN the pixelnet sequence. A different signal value will trigger special functions within the actual controller like setting the address, mode, # of nodes...

Thanks again.

Now to build my SD Card / Pixelnet Controller.

[wftxlites]

Let us know how it goes.