midiboxdmx
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
midiboxdmx [2008/12/08 08:45] – philetaylor | midiboxdmx [2013/09/25 12:29] (current) – forum link updated smashtv | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
+ | Midibox DMX is a DMX512 compliant controller for Midibox created by Phil Taylor - phil@taylor.org.uk | ||
- | A DMX512 compliant controller for Midibox created by Phil Taylor - phil@taylor.org.uk | + | Originally Discussed [[http:// |
- | Originally Discussed [[http:// | + | Here is a picture of my test system, It is enclosed in an old Strand Tempus 2-12 case (I bought 4 very cheap!). |
- | Here is a picture of my test system, I will box this once I decide on an enclosure. I have also included a closeup of the only bit of extra hardware (other than MBHP modules) that is required! | + | {{:midiboxdmx:mbdmx-boxed.jpg|}} |
- | + | ||
- | {{http:// | + | |
===== Concept ===== | ===== Concept ===== | ||
Line 48: | Line 47: | ||
I have decided that after struggling with the limited memory of the PIC16F88, 352 DMX channels was just too ambitious. I have now reduced it to 256 channels. One of the main reasons for this decision is that I was missing too much IIC data and causing too many retries. I have now made the IIC handing interrupt based and buffered which seems to make it much more stable (I will be posting this update once I have tested it thoroughly.) | I have decided that after struggling with the limited memory of the PIC16F88, 352 DMX channels was just too ambitious. I have now reduced it to 256 channels. One of the main reasons for this decision is that I was missing too much IIC data and causing too many retries. I have now made the IIC handing interrupt based and buffered which seems to make it much more stable (I will be posting this update once I have tested it thoroughly.) | ||
+ | |||
+ | |||
+ | ===== ANSI E1.20-2006 RDM Support ===== | ||
+ | |||
+ | I have done some of the groundwork to providing RDM support, I have a copy of the ANSI E1.20-2006 standards document and the example C source from Wybron which give full details for creating an RDM responder. | ||
+ | |||
+ | I have also been assigned a Manufacturer ID from ESTA. The reason that manufacturer ID's are important is that much like Ethernet, every RDM device must have a UID which is unique. The manufacturer ID that I have been assigned is 4D42h As it needs a ' | ||
+ | |||
+ | ESTA were concerned about controlling the allocation of UID's and I have committed to creating a website where people can request allocations, | ||
+ | |||
===== Hardware ===== | ===== Hardware ===== | ||
- | Pretty much all of the hardware is based around standard MBHP modules, the only addition is my simple TTL Serial <-> RS485 interface the schematic of which is below. I made it on a 6x6 piece of strip (vero) board (I didn't bother with header connectors): | + | Pretty much all of the hardware is based around standard MBHP modules, the only addition is my simple TTL Serial <-> RS485 interface the schematic of which is below. I made it on a 6x6 piece of strip (vero) board (I didn't bother with header connectors) |
- | {{http://www.lansystems.co.uk/ | + | After reading the RDM spec, I realise that a simple BIAS circuit will also be required, this is only 2 extra resistors (+ 120ohm terminator) so I will post a modified circuit soon. |
+ | |||
+ | {{:midiboxdmx: | ||
+ | |||
+ | {{: | ||
Line 95: | Line 108: | ||
Pretty much everything at the moment, | Pretty much everything at the moment, | ||
- | |||
- | |||
midiboxdmx.txt · Last modified: 2013/09/25 12:29 by smashtv