Elsewhere on the HW Forum,
viewtopic.php?f=1&t=19935
it has been suggested that if one has a lighted stop action with more stops then are needed for a sample set, it would be nice if there is a way of indicating which stops are enabled (activated) and which stops are not being used. A forum member, engrssc, has the rather clever idea that the LEDs for enabled stops all be made to glow dimly and only come on fully when the stop is ON. Since I have a decoder driver on my website already, I went ahead and modified it to have the behaviour just described.
https://sites.google.com/site/casavanto ... th-a-twist
Here is how it works: When a stop is turned on, its number is stored in an array that keeps track of all stops that are enabled. These stops are then turned on and off rapidly with about a 20% duty cycle causing them to glow dimly until they are turned ON, when they glow fully. Turning the stop OFF causes it to revert back to the dim state.
The code can be loaded onto an Arduino Mega which is then connected to a keyboard (channel 1) to see how this works. You will need to connect some LEDs (+resistors) to the outputs (pins 2 to 68) to see it in action.
When a new sample set is loaded, the decoder is reset by clearing the array that keeps track of enabled stops. For testing purposes only, I have arranged it so that pressing top C clears the array. This function could also be assigned to a "console reset" button or alternatively, it could be triggered automatically when a new sample set is loaded. If one now pushes a special general piston that has been programmed with all the stops in that sample set followed by a general cancel, all the enabled stops will glow dimly while stops not available will remain dark.
I think this is an excellent way of getting around having to use a touch screen if you already have a console with a multiplicity of stops and a lighted stop action.
viewtopic.php?f=1&t=19935
it has been suggested that if one has a lighted stop action with more stops then are needed for a sample set, it would be nice if there is a way of indicating which stops are enabled (activated) and which stops are not being used. A forum member, engrssc, has the rather clever idea that the LEDs for enabled stops all be made to glow dimly and only come on fully when the stop is ON. Since I have a decoder driver on my website already, I went ahead and modified it to have the behaviour just described.
https://sites.google.com/site/casavanto ... th-a-twist
Here is how it works: When a stop is turned on, its number is stored in an array that keeps track of all stops that are enabled. These stops are then turned on and off rapidly with about a 20% duty cycle causing them to glow dimly until they are turned ON, when they glow fully. Turning the stop OFF causes it to revert back to the dim state.
The code can be loaded onto an Arduino Mega which is then connected to a keyboard (channel 1) to see how this works. You will need to connect some LEDs (+resistors) to the outputs (pins 2 to 68) to see it in action.
When a new sample set is loaded, the decoder is reset by clearing the array that keeps track of enabled stops. For testing purposes only, I have arranged it so that pressing top C clears the array. This function could also be assigned to a "console reset" button or alternatively, it could be triggered automatically when a new sample set is loaded. If one now pushes a special general piston that has been programmed with all the stops in that sample set followed by a general cancel, all the enabled stops will glow dimly while stops not available will remain dark.
I think this is an excellent way of getting around having to use a touch screen if you already have a console with a multiplicity of stops and a lighted stop action.