openACN - by Bill Florac

Back at it…..

bill — Wed, 18 Nov 2009 04:55:07 +0000

Ok, I’m unoffically quasi-back on the OpenACN project. (at least for a short time) I’m attempting to port the code over to a Freescale M52259evb platform. Things have gone OK. Some hickup. The bigess is that I can’t seem to turn off loop back on multicast sends. Still working to track this down. Otherwise, I think the MQX with the MCF2259 processor is going to be a good fit.

DMP, DMP, DMP….

bill — Tue, 17 Feb 2009 07:15:04 +0000

Well the DMP layer is a bit obscure and needs some cleanup (perhaps a lot). So after a few weeks of hiding in other project, I’m starting to make this happen. I went in a coded SDT so that DMP could “register” itself for callbacks just like SDT does with RLP. I then decide to tear all of it out and used the existing callbacks on components state changes. I had started this a while back, and have been flipping back an forth as to the best way to handle this. My solution will be to provide a DMP queue function that can be used for all the component callbacks. This allows the application to either handle the callback itself or let the DMP layer parse it and put it in a queue for the application to process when it has time.

Streaming ACN

bill — Tue, 27 Jan 2009 08:08:34 +0000

Perhaps I needed a break or perhaps because I heard BSR E1.31 has been ratified? Either way, I started work on a module for sending/receiving “Streaming DMX” or “SACN”. I havedone this once before so the port should be easy. I plan on releasing this after I 1) get it working and 2) modify it to meet the ratified version. Since I’m also the author of Wireshark dissector for this protocol I guess I can do both at the same time.

Test Applications Posted

bill — Fri, 23 Jan 2009 07:23:46 +0000

Philip reorganized the structure of the repository today so we could add a few test applications. The test application for each port do the same thing. I have test applications for linux, cygwin and an IDE complied version for MSVC Express. I am working on a NetBurner port.

The test application does not do much yet. First it uses SLP to find a Directory Agent (see openSLP if you need one). Once a DA is found you can register a component with DA and discover other components with the same DCID. If you get that far, you can select and create an SDT session with any of the other components found.

Restructure repository

bill — Thu, 22 Jan 2009 08:38:06 +0000

Philip and I are working a new directory structure for the repository. This will allow us to post some test applications. It looks like it will look something like this:

trunk/ # change to whatever name you want
  openacnsrc/ # the current tree
  builddir.mk # maybe rename "openacn.mk"?
    common/
    dmp/
    include/
    platform/
    rlp/
    sdt/
    slp/
  build-xxx-xxx # moved up a level from current
  build-yyy-yyy
  openacndoc # the optional documentation tree
  testappsrc # your test apps
  other-submodule # Not part of openacn trunk

Holding our own

bill — Tue, 20 Jan 2009 07:06:14 +0000

Not much new today. Philip has been working on making the code more C99 compliant and I cleaned up a few things to make thinks work on my end.

I need to do some looking into how much RAM/ROM we are consuming….

Bill

Test Applications

bill — Mon, 19 Jan 2009 00:09:26 +0000

FYI – I have test applications for each port. They currently are not in the repository. If anyone wants a copy, just send me an email.

Mile Post!

bill — Mon, 19 Jan 2009 00:08:07 +0000

At at mile post. Well sort of. I worked around the CYGWIN issue and now have ports to XP, cygwin, Netburner and Ubuntu (Linux). I can get instance of each running. They can register them themselves, find each other and create and maintain an SDT session with each to other! All code is posed in the repository.

cygwin

bill — Thu, 15 Jan 2009 07:00:49 +0000

I think I can use the CONFIG_RLP_SINGLE_CLIENT define to remove the need for destination address. This will allow me to continue to test on cygwin. At the moment, SDT is the only client so this should not be a problem. At some point, I plan on adding a E1.31 (streaming ACN) client. Without the destination address, we will not be able to have both at the same time.