Update on status:
I had a chance to power up my motherboard. Found a missing wire, which I fixed and I was able to link the Ethernet and see the FPGA with the programmer. I am using Vixen 2.5 to test. I have been working on this since January, so I loaded my parsing code and was able to see the correct byte data in the FPGA. So I went ahead and loaded my output pixel controller, and I was able to output generic serial at 56.7K baud to another computer. Also, after the show ended, the controller output the 512 bytes of zero to turn off all the lights.
Hoping to test generic serial at 115.2K and Renard outputs, and light test this weekend.
I learned something on this forum, the Vixen Renard output DLL, maps the three special characters to pixel amplitudes (0x7D, 0x7E and 0x7F) to pixels near their value.
0x7D to 0x7C This is what I will do. Then I will not have to output two byte pixels.
0x7E to 0x80
0x7F to 0x80
Is this acceptable, it will save resources?
ronp5683 wrote:Update on status:I learned something on this forum, the Vixen Renard output DLL, maps the three special characters to pixel amplitudes (0x7D, 0x7E and 0x7F) to pixels near their value.
0x7D to 0x7C This is what I will do. Then I will not have to output two byte pixels.
0x7E to 0x80
0x7F to 0x80Is this acceptable, it will save resources?
I am using that approach as well to add Renard output to the E68x controllers. The only situation where I can see it causing an issue is if a controller needed to see one of those specific dmx values for a certain function. It's unfortunate that the 3 special characters are contiguous. Watching your project with interest, hopefully will learn about fpgas.
One situation that might come to mind is a servo controller, where those values are near the value (x80) that is often used to center the servo. It's probably OK to do this, though.
jstjohnz wrote:The only situation where I can see it causing an issue is if a controller needed to see one of those specific dmx values for a certain function.
A configurable option would allow the user the choice of altering the value (as described above) or using a Renard escape sequence. That way if there was a controller that needed to see those specific values it could, but otherwise the more streamlined format could be used.
don
ronp5683 wrote:I could use a micro controller, but it would not be fast enough to handle the full bandwidth of 100Mbit/sec Ethernet. I can easily do this within the FPGA using very few resources. Also, I can remove the limit of the Wiznet chip and handle as many ports as I want.
In the Microchip world there are parts that I think would be fast enough for this, assuming that the TCP/IP stack is specifically tailored to the application. There are a few parts in the PIC32 family that have an embedded 10/100 Ethernet MAC plus DMA channels. In this case one would use an external PHY plus an FPGA to handle just the re-transmission of packets over the serial interfaces. The cost would be a bit higher, and the integration of the PIC and FPGA logic could be a bit tricky, and would (of course) be a complete re-design. Given how far along the project is, I don't think that it's worth it now.
