wDMX
 
Notifications
Clear all

wDMX

33 Posts
4 Users
0 Reactions
15.8 K Views
Posts: 26
 MaxS
Topic starter
(@maxs)
Eminent Member
Joined: 19 years ago
DynamoBen wrote:You can but you will basically be creating a DMX to ACN gateway which is not going to be a trivial task. It would be best, in this case, to have someone crank out an ACN plug-in. It doesn't have to be the full ACN spec it could just be DMX-over-ACN (see my sticky). The request has been made in the Vixen plug-ins forum but not a lot of attention has been paid to it.

BTW you will need/want to buy a copy of the ACN spec from ESTA ($40).

Apparently ETC has already done exactly that, although the device is overkill. A gateway could be done though. It's designed for use with their new Net3 system, which is not proprietary. (See FAQ in the third link.)
The links are for their 4-Port gateway, but a 2-Port is also available, according to their catalogue.
Overview: http://www.etcconnect.com/product.overview.aspx?ID=20095
Documentation: http://www.etcconnect.com/docs/docs_downloads/datashts/Net3_4Port_Gateway_vA.pdf
FAQ: http://www.etcconnect.com/Community/blogs/davidlincecumsbrain/archive/2006/10/28/40.aspx

So what's up with Net 3? Why does it exist? Why did we call it that?

First off -- Net 3 is not ACN. ACN is a standard, a protocol description, a plan. Net 3 is a tool, a user experience, a tangible feature set.

But - ACN is a big part of our plan for Net 3. Most (but not all) Net 3 features are built on ACN and Net 3 supports integration with other ACN based networking solutions (when they come around!) We say Net 3 is "powered by ACN."

Net 3 remembers the past while welcoming the future. Many familiar protocols, like EDMX will work on Net 3 networks running newer hardware like Net 3 gateways.

Net 3 strives to solve real lighting problems beyond DMX distribution. See our integration with popular Media servers as an example.

Net 3 is performance tested. We use a system integration lab at ETC to test our equipment - and equipment by others - to insure an acceptable performance level is reached.

Net 3 supports expansion. This is a big difference from our previous networking protocols - we were tapped out. Net 3 is ripe with possibility.

Net 3 works with others. That's why we did not call it ETCNet 3. Net 3 supports interoperability with other ACN systems and with protocols like RDM as well.

The problem with a gateway though, is that you would have to have one on both ends, to bring the DMX-over-ACN back to the DMX devices (SSRs), as well as another wireless bridge before that if wireless was being used. It's looking like an ACN plug-in for Vixen would be the better way, but I'm not sure my programming skills are up-to-par.


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago

Correct Net3 is a "super set" of the ACN protocol. During my time there I was a member of the team developing the ACN protocol and the nodes you are referencing.

I think creating the plugin is a pretty straight forward task for anyone with any amount of ethernet programming expirence. The harder part is verification thats its is written properly...however I am willing to verify the code if someone is able to write it. You may want to "refresh" my thread in the Vixen plugin forums.


Reply
Posts: 1084
 ben
(@ben)
Noble Member
Joined: 19 years ago

Ok, I do not have any knowledge per say in this department I do want to say I will beta test and run this when needed. I am interested in going all DMX by next year and wireless DMX would be awesome!! I do not mind spending money on hardware to get this working. I want something that can be improved, not a miracle that it will work though. :p

Ben


Reply
Posts: 26
 MaxS
Topic starter
(@maxs)
Eminent Member
Joined: 19 years ago

All righty, so providing we have the ACN plug-in written, what would system set-up look like? The whole thing should be done using 802.3x (802.3af could be implemented for PoE), which is compatible with 802.11x.)

I assume it would be something like what's shown in my attachment. As for the controller boards... they would need to be able to be assigned an IP, as well as a DMX address, right? They would also need to be able to interpret the DMX-over-ACN. How would that be done?


Reply
Posts: 1084
 ben
(@ben)
Noble Member
Joined: 19 years ago

I just want to say I have 2 wireless routers and a range booster I can use to setup a network and such to test whatever with.

Ben


Reply
Posts: 26
 MaxS
Topic starter
(@maxs)
Eminent Member
Joined: 19 years ago

All right. Everything's theoretical at this point, as we have no ACN plug-in to play around with. 😉 When we do though, we'll definitely be experimenting with networking with WireShark. (It's all layered on UDP/IP.) I've been thinking about whether or not we'd want to use PoE/802.3af instead of 802.11x so you wouldn't need all of the transformers for the wireless devices. 802.3af devices are few and far between, and because of that are fairly expensive though, so it would probably be better just to include an "Always On" outlet on the external housing for the controller board so that if the end-user chose to use wireless, the unit(s) could be fairly self-contained.

http://wiki.wireshark.org/ACN

Also, to provide the optional wireless to the controller boards, a product like this one would be used:
http://www.newegg.com/Product/Product.aspx?Item=N82E16833127053

Since that's fairly expensive for 16-64 channels (however many the controller board would provide), it would also be possible to "zone" boards. A switch could be run from the adapter/bridge which could provide data to multiple boards. (The controllers wouldn't be able to be easily daisy-chained.)

BRIDGE/ADAPTER --> SWITCH --> Controller Board
-------------------------------> Controller Board
-------------------------------> Controller Board

Being able to use standard networking equipment really opens up some cool possibilities. 🙂


Reply
Posts: 1084
 ben
(@ben)
Noble Member
Joined: 19 years ago

well, I was wondering how hard it would be to recode a router if we could get to the code of it? Being that the router I have has 4 wired outputs we could se it to recieve the signal and then you could hook up each controller to that output. I have heard you can hack into those routers not to hard if you actually have to right to access it.

Ben


Reply
Posts: 26
 MaxS
Topic starter
(@maxs)
Eminent Member
Joined: 19 years ago
ben wrote:well, I was wondering how hard it would be to recode a router if we could get to the code of it? Being that the router I have has 4 wired outputs we could se it to recieve the signal and then you could hook up each controller to that output. I have heard you can hack into those routers not to hard if you actually have to right to access it.

Ben

You could use a router without messing with the firmware. If you wanted to do that, you would leave the WAN port open, and connect all of your peripherals to the four LAN ports. This works because the WAN input, let's call it eth0, routes everything through iptables or the respective firmware equivalent, and then back out eth1, which has the 4 port switch built into it. By only plugging everything into the switch, you get all of the infrastructure functionality, but you don't route things through the firmware.

The only (consumer-level) benefit in screwing with custom firmware would be to boost the wireless Tx power from the default 24mW. (On my home router I boosted it to 100mW and slapped on a custom fan and added some 9dBi gain antennas. Don't tell the FCC. ;)) Nothing custom would really need to be done though, as the ACN protocol uses the 802.11x/3x standard and is layered on UDP/IP, so it's fully compatible with all off-the-shelf networking equipment.

EDIT: I've updated the PDF layout to reflect an alternate layout.


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago

I took a look at your drawing and I'm not sure what you mean by "remote console." In an ACN system using Vixen ACN is sent directly via Ethernet, ACN capable devices would "listen" to it and decode it to dimmer levels.

Testing the network devices isn't what I am concerned about. My concern is verifying the ACN plug-in is really sending and receiving ACN. I have a number of tools available to me that will work for this. However we are missing one huge piece....the plug-in.

Once that is done developers, like me, will need to make ACN capable devices. This process will take time. The big battle here will be the cost of hardware and the difficulty in developing the firmware which is why I suggest DMX-over-ACN over full ACN.

Long term I think it makes sense to go the Ethernet/ACN route, microcontroller Ethernet communication is getting easier and less expensive each day. By this time next year it could be very cost effective and easy to make an CAN device.


Reply
Posts: 26
 MaxS
Topic starter
(@maxs)
Eminent Member
Joined: 19 years ago

"Remote Console" was meant to be a laptop or other PC running Vixen that connects to the main server. (Accessed from Add-ins -> Remote Client) This is not part of ACN, but rather standard TCP/IP information being transferred between the remote client and the server. From what I understand, ACN is a protocol in the same way that HTTP, FTP, etc. are protocols, so you should be able to send other data over the network without problems.

Also, in the drawings all of the black lines are ethernet. (Purple are 2.4GHz ISM, red are 110/115/120VAC) I know that testing the network devices isn't really a priority right now, but as I lack the skills to work on a plug-in, I'm just thinking about what else would be needed to get a networked system working. I completely agree with your last statement, in that DMX-over-ACN over ethernet is the way to go.


Reply
Page 3 / 4
Share: