FPGA based pixel co...
 
Notifications
Clear all

FPGA based pixel controller

85 Posts
18 Users
0 Reactions
33.6 K Views
Posts: 6728
(@p-short)
Illustrious Member
Joined: 20 years ago

It strikes me that the project would be a lot better if it had bi-directional communications over Ethernet. Among things, this would allow you to implement ARP and ICMP (ping, at least). I'm don't know if the other E1.31 controllers here implement those protocols, but I think that they would be useful for diagnostics and maintenance. Is there any fundamental reason for limiting the implementation to the reception of one type of packet, without any ability to receive other types of packets or to transmit responses (other than that it takes a lot of design work)?


Reply
Posts: 238
Topic starter
(@ronp5683)
Reputable Member
Joined: 14 years ago

Phil,

Yes, I am probably a little lazy. However, I only have about 8000 logic elements, so I am trying to use them to support as many output types as possible. For 32 universes, I only have about 250 logic elements per universe to support all the different output types. If there were only DMX out or SPI out, I would consider putting in more resources for the Ethernet.

I agree that diagnostics and maintenance is important. The Ethernet physical has link leds, and blink for traffic. I have four LED's and could use one to indicate valid E1.31 traffic within my IP space, so I will at least add this for now. Thanks for the feedback.

Also, kingofkya, thanks for the feedback on the hubs. Your are correct that I probably don't need to do daisy chaining.


Reply
Posts: 1076
 Zeph
(@zeph)
Noble Member
Joined: 15 years ago

This will be fascinating. I'm a software type, with some electronic familiarity, but I've never dealt with FPGAs. I've read the simple descriptions of FPGA operation, but I have no experience with how you will form the higher levels of digital logic from the basic elements - receiving and decoding ethernet packages, or getting all the timing right to shift out 2811 data. A long time ago, I did wire wrap TTL circuits for simpler functionality (back in 74LS days), but the FPGA will allow you to build much fancier state machines and digital logic (and modify it to fix bugs!!). So I hope to tag along, and learn a bit, from whatever you can share about the design of your project.

I understand that you'll be using a high level design language, but I hope the software will allow outputting equivalent circuit schematics or something similar; I'd like to see how one implements these functions from latches, shift registers, simple gates, multiplexers, etc.


Reply
Posts: 1076
 Zeph
(@zeph)
Noble Member
Joined: 15 years ago

I'm thinking of a 2811 machine. From my old MSI logic days, I imagine a 512 byte static dual port memory (one port being used to fill from the ethernet). For output, there would be a 2.4 MHz clock, divided by 24 and fed into a 9 bit counter which addresses the RAM (fetching a byte every 10 us). The 8 bits of data fetched each time would be fed into 8 inputs of a 24 bit Parallel to Serial shift register, the other 16 bits would be loaded from fixed values of 1 or 0. Basically, for each 3 bit group in the 24 bit register, the first bit would be fed a 1, the second bit would be loaded from the RAM output, and the third bit would be loaded with a 0. These would be used to generate a short or long pulse (three shift register bits at 2.4 MHz produce one data bit for the 2811 at 80o KHz). Use that original clock to clock out 24 bits for every fetch from the RAM. Add a latch (loaded separately from the ethernet logic) and a down counter to stop this after 1..512 bytes have been shifted out and another timer for the pause between refreshes.And so on.

Would your logic be anything similar to that?

The big trick is that I gather you would create one set of logic which could be configured to output in various pixel protocols. If it were just a matter of building logic similar to the above for each output and selecting which one to enable I can imagine that, but I bet you would be sharing more than just the RAM between the different pixel protocol logics.


Reply
David_AVD
Posts: 991
(@david-avd)
Noble Member
Joined: 17 years ago
ronp5683 wrote:ACN 1.31 only sends the active pixels in a universe. I will also only output the active pixels for the universe.

Can you explain what is meant by this?


Reply
Page 5 / 17
Share: