Artnet

[samsc]

[QUOTE=rekveld]well,

in the specs it says the bytes of the opcode are reversed (why would anyone do that ?), so I would be curious to see what the content of the 'opcode' field in your struct is.
QUOTE]

well the key to any documentation, is reading it very very closely and do exactly what your are told.
but even then documentation and ones interpretation can be incorrect.

'Reversed' opcodes would be a sign of a little endian vs big endian byte order. same as all pentium pcs.

are you sending to udp address 255.255.255.255 or 2.255.255.255?

[rekveld]

Quote:



Originally Posted by samsc


well the key to any documentation, is reading it very very closely and do exactly what your are told.
but even then documentation and ones interpretation can be incorrect.




I sure tried to read as closely as I could and do exactly what I understood ! The fact that I wonder why anyone would like to reverse bytes did not stop me from doing so myself...


Quote:



Originally Posted by samsc


'Reversed' opcodes would be a sign of a little endian vs big endian byte order. same as all pentium pcs.




that bit of information is new to me, only did programming on mac (and atari, way back), don't normally come close to pentium machines, but that has nothing to do with that I followed the specs, it says for every field whether hi or lo byte is first, that is pretty clear, although I don't understand why a protocol would mix both representations..
I guess there must be some historical reasons of some sort, some hardware reasons.. ?


Quote:



Originally Posted by samsc


are you sending to udp address 255.255.255.255 or 2.255.255.255?




as listed in the specs (page 8) I send to 2.255.255.255 (or 10.255.255.255) with the jumper).
255.255.255.255 is pretty crazy, no ?


but what the about that first 8-char string, is that 'big endian' too ?

[samsc]

i accidentally pressed edit rather than quote. so your post got broken

i use 255.255.255.255...

its the broadcast ip address. removes one more thing to go wrong.

you might have to set the sub-net mask to 255.0.0.0 to use 2.255.255.255
though i dont know...

[samsc]

it is possible that your artnet box is broken.

i did two installs in the last week, and at both one of the new boxes was broken.....

[samsc]

but what the about that first 8-char string, is that 'big endian' too ?

strings dont have endian ordering.
but shorts and long integers do.

on powerpc the number 0x1234 in hex is arranged in memory as 0x12 0x34 but on pentium its order in memory is 0x34 0x12

[rekveld]

bought two lanbox-lce's and it took me 10 minutes to get them working !
Finally, I think I deserved it, four days before my show..

anyway, thanks a lot for all your help and suggestions over the last few days.

Joost.

[samsc]

bought two lanbox-lce's and it took me 10 minutes to get them working !
Finally, I think I deserved it, four days before my show..

anyway, thanks a lot for all your help and suggestions over the last few days.

Joost.

Do you lanboxes use UDP packets?

R

[rekveld]

yes,

they recently upgraded to a new firmware for their boxes (it could even still be in beta), and the new firmware allows to write dmx directly into the 'mix' buffer of the lanbox. The udp packet is a list of dmx values, and a header containing an instruction code, the start adress and the length of the list.
This is how I used it yesterday, but these boxes can do much more: they are designed to be stand-alone controllers. I think with one lanbox-LCX and several lanbox-LCE's slaved to it you could even have a 'super-dmx-universe' of several thousand channels, the LCX keeping track of which channel should go to which box.

and I'm very happy to say that my installation yesterday worked just fine (and people liked it too..)

ciao,

Joost.