Recent content by multicast

To a point.. Most *should* work pretty much ok across their full range. ( for any resonable design ).. There are some DC/DC converter that wont' work well across a variable load.. This is sometimes done with things that present constant loads.. Sequenced LED's hardly are constant. A 70%...

The 'market' for the pro lighting world and the hobby market is not that different. In fact, i'd say in both a majority dont' know much about networks in general. And they just want to plug it in, an make it go. I do get this. This is essentially the reason the mandate for IPv4 is there. It...

And many now ( google / apple / large universitys ) are now disabling IPV4. We are in that messy in between time. Yes. You shoudl come and join us at the TSP!

This works until it does'nt. The signaling rate of the Hub 75 signals operate around 100-200Mhz, depending on the setup. At that rate the signal path is effectively transmission line, and the Y/T in the signal path causes all sorts of interesting reflections. This will work just fine at...

Some new modern devices and stacks do not have ipv4 capability. These particually are devices that are intended for IoT type applications.. If the standard progress's as written, these devices will never be able to be compliant with the sACN standard.. At some point ipv4 will not exisit...

Its not about removing IPv4 at all. that woudl not be good.. Its about providing the option for an ipv6 ONLY device. The way the standard as propsed written means that you can either have a IPv4 Only device or an IPv4/IPv6 device. The option to have an Ipv6 Only device is not permitted...

I have a serious concern about the mandate in the standard that says all devices SHALL ( ie MUST ) support both ipv4 and ipv6. Taking the approach of mandating ipv4 in the E1.31 protocol, is effectively making E1.31 a grand-father protocol, which will be unusable at some point in the...

The E1.31 sACN Standard has gone to its 2nd Public review. This revision of the standard is primarily about including ipv6 into the standard, and fixing a few minor errors that had arisen. You, as users of the standard are welcome to submit your comments on the standard. It closes 2 October...

Milton is the 5 pin DMX ranger. If you want too wind him up, take a 3 pin cable to a plug fest.. Technically there is no reason why the 3 pins are any worse than a 5 pin.. but its all about interop.

Sorry about the late notice for this...... The ESTA Control Protocols Group is hosting an informal round-table discussion webinar Monday evening. ( CDT ) •“Common DMX512/RDM Myths” will be broadcast on Monday, July 24 from 7:00 p.m. to 8:00 p.m., CDT. This will be 10am Tuesday AEST...

Dave from EEVblog does a bit of talk about some electrical fundementals which could be quite interesting.

I made something very similar to this, about 5 years ago, but have subsequentlly changed my methodologies. IS this somethign that folks woudl still use.

LLDP's probalby is'nt a great choice. Thats very specific to the configuraiton / managment of switches.. And the packets wont' go further than a switch.. The protocol thats being proposed is to use mDNS/DNS-sd, which is the way lots of things can get discovered. No need to reinvent the...

I'm looking to propose to the ETSA working group, Device Discovery inside of E1.31. The purpose of this would be so yoru controller ( Xlights or similar ) could actively discover the devices ( blinky speak controller that were on the network ) and then act intellegently in the way that it...