gmbartlett
New member
As a new year begins I want to update everyone on the planned changes/updates I will be making to the Helix system. After fixing a small bug in the Helix firmware that didn’t show up until I setup my display, my Helix systems worked without a hitch this season. I now plan to implement several improvements that I’ve had my eye on for a while. These changes/updates will be mostly to the firmware and software but I will also be making a few changes to the hardware. Almost all of the changes will be backwardly compatible with the existing hardware.
Helix Firmware/Helix Network Supervisor Upgrades (in roughly priority order):
1. Add the capability to play music between shows. This is a low hanging fruit so I’m working on this first.
2. Add the capability to have different shows each day of the week. I’m actually making it so you can have up to nine different shows every night for a total of 63 different shows per week. This improvement is loosely tied to number one above so I’m developing it in tandem.
3. Implement the Check for Updates button on the Helix Network Supervisor. This will allow you to easily download the latest versions of the Helix Firmware and Helix Network Supervisor.
4. Add auto-configuration of the XBee radios. This feature was in the initial release of the firmware but I had to remove it for a couple of reasons. I’m now going to add it back in.
5. Add auto-reassociation of the XBee radios. One of the quirks of the XBee radios is the way they setup their network. The main radio is the network coordinator and all of the other radios are network nodes. The coordinator is responsible for establishing the network. The nodes associate with the coordinator. However, if the coordinator is turned off, the nodes don’t know they are no longer associated with it. When the coordinator comes back on line, it may not use the same channel to setup the network, as a result it has lost all contact with the nodes. I believe I’ve figured out a way to force the nodes to auto-reassociate with the coordinator if they ever lose contact. This will fix a lot of the issues people have seen where the Helix “is not responding”.
6. Add the capability to stop/start a show or sequence from the Network Supervisor. This would be useful during setup and to demo the display.
7. Add the capability to run test routines from the Network Supervisor. This would also be useful during setup and troubleshooting.
8. Add the capability to check the status of all of the Helix Main boards from the Network Supervisor.
The main purpose behind the development of the Helix system was to have a standalone controller (Mode 1). When I built my first controller, the Prop 128v1, it operated in what I now call Mode 2. My first year I was able to control 128 channels without a problem and according to the bandwidth it should be able control 256 channels. The Prop 128v1 is the heart of the Helix so I thought it too should be able to control up to 256 channels. After much work and frustration I still can’t get the Helix to control more than about 64 channels in Mode 2. This is very perplexing to me since as I said the relevant hardware is virtually identical as is the firmware. That is why I started trying to develop Mode 3. For 2009 I ran out of time to fully develop Mode 3 but I plan to get back to it. However, as I said, my main development efforts will be focused on Mode 1. As such I plan to also work on the next two items to help eliminate the need for Modes 2 and 3.
9. Add the capability to drive the Renard series of controllers. The Renard uses a serial RS485 input at a fairly slow baud rate. The Helix Daughter boards are driven by RS422 drivers. In this operation RS422 is compatible with RS485. I believe that a daughter board could be replaced with a chain of Renard controllers. You would lose 32 Helix channels but you would gain many more Renard channels in their place. Hardware wise this would only require a custom Cat5 cable be built that would correct for the pin-out mismatch. This would eliminate one of the big requirements for Modes 2/3.
10. Add the capability to drive the LEDTriks boards. They too use a serial RS485 data stream. I believe swapping 32 Helix channels for LEDTriks would be a good trade. This would eliminate the other big requirement for Modes 2/3.
When I start developing these two capabilities I will need some testers and advise on how people use these controllers, specifically how they are used with the Helix.
The last two firmware/software updates are stretch goals for this year.
11. Add FAT32 support to the microSD file system. The current file system only supports FAT16. This limits the microSD card to 2GB or less. In order to use the larger cards it needs to be able to support FAT32. However, 2GB cards should be plenty large enough for even the most elaborate show so this upgrade is very low on the list.
12. Add the capability to interface with the miniRDS board. I would like to be able to display the song name and other messages via RDS. I don’t believe the Helix will be able to dynamically change the message while the sequence is playing but there is no reason the message couldn’t be updated between sequences. This feature is the only one that won’t be backwardly compatible with the existing Helix systems because it requires a change to the hardware.
If there are any other firmware/software upgrades that you are interested in then please let me know and I will see if it can be added to the list.
After running the last PCB group buy and assisting several people build and troubleshoot their boards I’ve decided to make a couple of changes/upgrades to the hardware also.
Hardware Updates:
1. Change the surface mount Quad RS422 drivers to through hole DIP chips. When I first developed the Prop 128v2 it was a 3.3V system only. I was unable to find a through hole 3.3V Quad RS422 chip. Now that the Helix has 5V on board I can use a through hole chip instead. This will eliminate one of the major sources of difficulty in assembling the main board. As a side benefit, the new chips are cheaper and easier to get.
2. Change the fuse holder to horizontal clips w/cover. This will make it easier to check the fuse and it is also cheaper.
3. Add 3.3V and 5V test points on the Helix Main board. This will make testing easier.
4. Add a XBee TX LED on the main board. This will make troubleshooting easier.
5. Add a miniRDS port to the main board. This is easy to add while I’m making the other changes but it won’t be required to be populated in order for the board to work.
If there are any other hardware upgrades that you are interested in then please let me know.
I plan to have the hardware updates completed in the next month. I hope to have all of the boards available for purchase by mid to late February. The prices will be a little cheaper than last time. Also, I plan to provide the SMT microSD socket soldered to the main board as part of the price.
Helix Firmware/Helix Network Supervisor Upgrades (in roughly priority order):
1. Add the capability to play music between shows. This is a low hanging fruit so I’m working on this first.
2. Add the capability to have different shows each day of the week. I’m actually making it so you can have up to nine different shows every night for a total of 63 different shows per week. This improvement is loosely tied to number one above so I’m developing it in tandem.
3. Implement the Check for Updates button on the Helix Network Supervisor. This will allow you to easily download the latest versions of the Helix Firmware and Helix Network Supervisor.
4. Add auto-configuration of the XBee radios. This feature was in the initial release of the firmware but I had to remove it for a couple of reasons. I’m now going to add it back in.
5. Add auto-reassociation of the XBee radios. One of the quirks of the XBee radios is the way they setup their network. The main radio is the network coordinator and all of the other radios are network nodes. The coordinator is responsible for establishing the network. The nodes associate with the coordinator. However, if the coordinator is turned off, the nodes don’t know they are no longer associated with it. When the coordinator comes back on line, it may not use the same channel to setup the network, as a result it has lost all contact with the nodes. I believe I’ve figured out a way to force the nodes to auto-reassociate with the coordinator if they ever lose contact. This will fix a lot of the issues people have seen where the Helix “is not responding”.
6. Add the capability to stop/start a show or sequence from the Network Supervisor. This would be useful during setup and to demo the display.
7. Add the capability to run test routines from the Network Supervisor. This would also be useful during setup and troubleshooting.
8. Add the capability to check the status of all of the Helix Main boards from the Network Supervisor.
The main purpose behind the development of the Helix system was to have a standalone controller (Mode 1). When I built my first controller, the Prop 128v1, it operated in what I now call Mode 2. My first year I was able to control 128 channels without a problem and according to the bandwidth it should be able control 256 channels. The Prop 128v1 is the heart of the Helix so I thought it too should be able to control up to 256 channels. After much work and frustration I still can’t get the Helix to control more than about 64 channels in Mode 2. This is very perplexing to me since as I said the relevant hardware is virtually identical as is the firmware. That is why I started trying to develop Mode 3. For 2009 I ran out of time to fully develop Mode 3 but I plan to get back to it. However, as I said, my main development efforts will be focused on Mode 1. As such I plan to also work on the next two items to help eliminate the need for Modes 2 and 3.
9. Add the capability to drive the Renard series of controllers. The Renard uses a serial RS485 input at a fairly slow baud rate. The Helix Daughter boards are driven by RS422 drivers. In this operation RS422 is compatible with RS485. I believe that a daughter board could be replaced with a chain of Renard controllers. You would lose 32 Helix channels but you would gain many more Renard channels in their place. Hardware wise this would only require a custom Cat5 cable be built that would correct for the pin-out mismatch. This would eliminate one of the big requirements for Modes 2/3.
10. Add the capability to drive the LEDTriks boards. They too use a serial RS485 data stream. I believe swapping 32 Helix channels for LEDTriks would be a good trade. This would eliminate the other big requirement for Modes 2/3.
When I start developing these two capabilities I will need some testers and advise on how people use these controllers, specifically how they are used with the Helix.
The last two firmware/software updates are stretch goals for this year.
11. Add FAT32 support to the microSD file system. The current file system only supports FAT16. This limits the microSD card to 2GB or less. In order to use the larger cards it needs to be able to support FAT32. However, 2GB cards should be plenty large enough for even the most elaborate show so this upgrade is very low on the list.
12. Add the capability to interface with the miniRDS board. I would like to be able to display the song name and other messages via RDS. I don’t believe the Helix will be able to dynamically change the message while the sequence is playing but there is no reason the message couldn’t be updated between sequences. This feature is the only one that won’t be backwardly compatible with the existing Helix systems because it requires a change to the hardware.
If there are any other firmware/software upgrades that you are interested in then please let me know and I will see if it can be added to the list.
After running the last PCB group buy and assisting several people build and troubleshoot their boards I’ve decided to make a couple of changes/upgrades to the hardware also.
Hardware Updates:
1. Change the surface mount Quad RS422 drivers to through hole DIP chips. When I first developed the Prop 128v2 it was a 3.3V system only. I was unable to find a through hole 3.3V Quad RS422 chip. Now that the Helix has 5V on board I can use a through hole chip instead. This will eliminate one of the major sources of difficulty in assembling the main board. As a side benefit, the new chips are cheaper and easier to get.
2. Change the fuse holder to horizontal clips w/cover. This will make it easier to check the fuse and it is also cheaper.
3. Add 3.3V and 5V test points on the Helix Main board. This will make testing easier.
4. Add a XBee TX LED on the main board. This will make troubleshooting easier.
5. Add a miniRDS port to the main board. This is easy to add while I’m making the other changes but it won’t be required to be populated in order for the board to work.
If there are any other hardware upgrades that you are interested in then please let me know.
I plan to have the hardware updates completed in the next month. I hope to have all of the boards available for purchase by mid to late February. The prices will be a little cheaper than last time. Also, I plan to provide the SMT microSD socket soldered to the main board as part of the price.
