P. Short wrote:Are you planning on using or losing the d-light boot loader?
Phil:
That's a very good question seeing how I do not know what the boot loader does. Will you please explain what a boot loader does or used for, and make a recommendation on what I should do. All the help is greatly appreciated.
Thanks.
My understanding is that the code in the d-light is divided into two pieces. The first piece, which I call the boot loader, is always present in the controller and is never over-written or updated. The purpose of this code is to start up the processor, perhaps do some sanity checks, jumpe into the operational firmware, and on occasion download new operational firmware. The second piece of code is the operational firmware, which does everything associated with dimming, is designed to be updated from time to time as enhancements and changes are introduced and bugs are fixed. The usual reason for dividing the code into two pieces is to make sure that there is always code in the device that is capable of starting up the processor and receiving a new operational firmware download, even after a previous download/update failed due to a power glitch or other problem.
The Renard firmware is currently designed as one single blob of code, since the PIC16F688 doesn't provide any mechanism for the firmware to update itself. What I was thinking is that you would probably want to write a new version of the operational firmware that still works with the original d-light boot-loader. This assumes that you can make the new firmware interface to that boot-loader as needed, and that the PC program for downloading new operational firmware does not prove to be a problem.
Of course, I'm hoping that Daryl will chime in (either in public or privately) if I'm totally off-base.
We use boot loaders at work. Here are a couple of reasons this is desirable.
One is that no special hardware or programmer is needed. You just use the same method to communicate as you normally would. Second is that you can use any protocol you want, from simple to complex. We sent a few carriage returns out and measured the bit widths and adjusted the master clock frequency until the bit width measured correctly.
You can also ignore the UART and use two pins and use a clocking method that allows you to go as fast as the slowest hardware will go. We used an Atmel processor and found that it was four times quicker to program a boot loader and have the processor clock in the rest of the code.
With a boot loader, on some processors, you can also load test code into RAM and execute out of RAM. This allows you to run this code once and once power is removed, so is the code. You could write a boot loader that moves itself to RAM and then can program all of the flash.
I would recommend that you remove the D-Light supplied PIC and replace it with a blank PIC. You will not be able to use our bootloader. However, they are a "nice to have"!
Anyone still working on this? I'm guessing it's a dead issue.
I certainly have interest in it being done.
d-Light would eliminate this totally if he would just add DMX control to the programming like LOR has done on their controllers. Granted DMX would not let one to use the fancy features of the product but it would allow it to be used in many other environments including Vixen. 🙂
What features would be lost if the DMX protocol was to run a D-light board?
Macrosill wrote:What features would be lost if the DMX protocol was to run a D-light board?
DMX is basically a ON/OFF/Dimmable function protocol.
The Twinkle and other similar fancy functions would be suppressed.
However those functions can be simulated in software and are planned to be included in some commercial packages.
LOR allready supports DMX on its line of controllers. The board senses whether it is being controlled by DMX or the LOR/d-Light protocol. Physically the connections remain the same to the units. DMX is the protocol used by the professional stage lighting community. Many spot lights, lasers, motor controls and other specialty items use DMX to control their features.
By having DMX support you can use software like Vixen to control the LOR protocol controllers.
Tom
One thought that comes to my mind would be to create a daughterboard that would plug into the PIC slots (as long as they are removable) to adapt/change them to the Renard Spec. I would draw something like this up - but - don't have a board to test with.
As I look at the boards - it appears that they use 18F pics for each of the 8 channels.
Of course, if someone wrote an dlight (lor) plugin for vixen.... that would also solve the issue!
MrChristmas2000 wrote:DMX is basically a ON/OFF/Dimmable function protocol.The Twinkle and other similar fancy functions would be suppressed.
.......
Tom
So the Twinkle and other fancy effects are stored in an ic on the board and not controlled by the D-Light software, its name escapes me right now?
Vixen already has Twinkle and other fancy functions as well.
