Jump to content

John_W._Couvillon

Members
  • Posts

    350
  • Joined

  • Last visited

Everything posted by John_W._Couvillon

  1. Midiboxxer, My understanding of how the motorfader works, and how it is used is weak. I can see how the fader itself can serve as feedback to the control loop, but it didn't dawn on me that a voltage, current, or what have you, resulting from the the same resistance value could also be used for some other purpose. Once the parameter is digitized, it could serve both purposes. The PIC software could easily handle that. Looking at the interconnection diagram, on the ALPS fader, there are two leads for the motor and three connections at the other end, one for the touch sensor, ground and one other. is it safe to say that the one odd connection comes from the fader resistance itself? Can anyone familiar with the ALPS motorfader confirm this for me? If thats the case, then all my questions will have been put to rest. Hopefully, Thorston or comeone else will jump in here with some input. Thanks, Johnc
  2. Midiboxxer, Having gone through all recommended reference links, etc. I'm still a bit confused. Permit me to review what my control device inputs and control device outputs are: Control Box - The installation (core, MF card) is intended to operate as a stand alone device, installed in a small box, with terminal strip for inputs and outpus. Power supply will be internal to the box. Control devices: Control Pot - The control pot is built in to the foot actuated swell shoe on the organ console remote from the location of the control box (core, MF card). This pot sets the desired position for the swell shades (0-closed to 100% fully open). No leds are needed to indicate position. Swell shade motor Drive - This includes the dc gearhead motor with arm attached to the output shaft which opens and closes the swell shades. Movement is from 0 - closed shades to 100%- fully open shades, or rotationof the output shaft of 90 degrees. Attached also to the output shaft is a rotary shaft feedback pot, linear taper, 10K which tracks the position of the output shaft. So from the motor drive there are 7 wires, 3 for the 12vdc to the motor(2hots, ground); 4 for the connection to the feedback pot (top of pot, bot. of pot, wiper, ground). Control Inputs: Position setting pot - Analog in on J5, term A0 of the core Feedback pot - Analog in on J5, Term A1 of the core Outputs: output to motor - digital out on J3, M1-1 and M1-2 on the MF card. The core will have midi out and midi in connectors, however, operation of the installation will be by turning on the power to the core, etc. midi channel selection is for setup, config, troubleshooting only. Since the installation has minimum devices, a custom pc board will be used to combine the core and the MF module components. With only one motor to drive, all should fit on one board. What I don't understand is the input side from the pots. Do the leads from the pots connect directly to the terminals on the core? Do I use the 5vdc on the core PS to input a proportional dc voltage? Same question for the feedback pot signal. Which ini file for 64E software do I use, the MF ini? How does the software know which of the pot signal inputs is control input, and which is feedback input? I haven't found anything in the writeups, tutorial, etc. that say anything about feedback. Do the ALPs motor faders have a feedback pot tied in to the slider that is internally wired. With only 4 wires to each motor fader from the core/MFboard, something is not right. Regards, Johnc
  3. Midiboxxer, It appears from the datasheets for the TC4427 and the schematic for the MF board that the HC595 delivers two outputs to each TC 4424 on the MF board. the TC 4427 is a dual mosfet driver rated 1.5 amps (the TC 4424 will do 3 amps) with no special circuitry for direction, etc. consequently, it appears that any two input H-Bridge with the necessary rating to match the motor, will work. What I don't see in the references is where feedback from the pot comes into the picture. There is input directly to the core which I assume is where the feedback comes in, however, I am at a loss as to what the signal is; variable dc voltage analogus to position of a pot as a % of 5vdc, a variable resistance value from the pot directly. If a pot is involved, what value is it, and is it linear. Last question, will the 64E apps software run the MF module, right out of the box, or is there an ini file. or some way to configure it? I am not familiar with the ALPS devices or motorfaders in general, other then that they are motorized pots used in audio, etc. I am getting closer to the realization that the MF module and core will do what I want them to do, but some extra input would help. Thanks for your help, Johnc
  4. Midiboxxer, Thanks for the reply. So I would need a core running the 64E app, and an MF module. Since I will have only on rotary encoder in the form of a pot, and only one motor to run, can I do it with only one DIN? The dc motor is a reversible, 12 volt motor, only two leads. I will add a pot on the output shaft to encode position. How does the feedback pot tie in to the MF module, or the core? Since the MF module cannot provide enough drive for the motor, I will use an Hbridge which has two inputs, one for each direction. How does this tie in to the MF module? Thanks, Johnc
  5. I am back on the track of using the midibox MF module to drive a dc motor. After researching the issues, Hbridges are available to provide for the increased output needed for a larger dc motor. What I am trying to do is to do position control using a dc gear motor as typically done in the radio control area for model aiplanes and boats. Basically, it involves a pulse generator, servo amplifier and H bridge. My big question is wether the MF module can provide the function of the servo amplifier, accepting the pulse input and driving the Hbridge and motor. The motor will be an auto windshield wiper motor, 12vdc, reversible,with 60 RPM output, with a potentiometer connected to the output shaft for feedback. Does the MF module operate on midio128, 64 or what app software? Anyone knowledgable in this area, please respond. Thanks, Johnc
  6. Hello Trevor, My apology for the impatience. One midibox core and two DOUTS would be a good start. Pay close attention to PER S's comments above, concerning the PIC Id, Its important. You should check out the midio128 design details on http://www.uCApps.de and read up on connecting relays. The DOUTS from Smashtv (http://www.avishowtech.com/mbhp/buy.html) provide some options for mounting the reed relays on the DOUT pcboard this really simplifies things. Without more data on your relay, I would recommend using the reed relay as the individual contacts would be easier to connect in to your relay. However, its your choice. Good luck! Johnc
  7. Trevor, In an earlier post you said " I'm not looking to have Midibox read from the manuals/pedals/stops. All I would like is something that can interpret MIDI signals coming from Finale/Sibelius. etc. on the computer and turn it into 12V going to the correct key relay." The above is in conflict with your last post where you said " I think the key contacts would be the best place to wire the DOUTs because there are pins that can easily have other wires soldered onto them. Also, the coupler relays are all right in the console and the key contacts are the only good places to wire into before hitting the relays in the console." YOu can't wire DOUTS to the keyboard contacts. It seems to me that you are going in two different directions at the same time. If you want to drive pipe magnets from midi messages that come from your laptop running finale/Sibelis, that you can do with a system as shown on your jpg on an earlier post. Your laptop feeds out through a midiman 1x1 or 2x2 usb interface, the midi signal goes to a midibox core with douts only. Each DOUT drives a pipe magnet. There may be a conflict with your existing diode matrix where by you can't drive a magnet from a DOUT through the matrix. Do you have a schematic of your diode matrix? Can you email it to me. In any event you will have to have a DOUT pin for every pipe magnet you intend to drive. Divide the total number of magnets by 32 and that equals the number of DOUT modules you need. Divide the number of DOUT modules by 4 and that tells you how many midibox cores you need. Each core can handle 128 outputs. Provided you can configure the midi music to assign different ranks to different midi channels, the system could work. or Going back to keyboard contacts opens up a whole new box of goodies. You will have to have independent contacts available on the keyboard for connection to the DINS. Then comes a decision wether to use a matrix format or wire each key contact to a pin on a DIN. The matrix requires one DIN and one DOUT to do an 8x8 matrix, but required only 16 wires. the other approach will require 61 wires and one common. If you take this approach, you will end up with midi messages to route somewhere. I don't see where this fits into your program. With this, I am very confused. You need to go back to the forum and wiki and read about what the different midibox modules do. Also, you need to read up on general midi. I think that I can help you, but you need to state more clearly exactly what you want to do. It appears that you have a conventional console with stops, pistons, etc. Do you have a conventional relay that was designed to be used with this particular console? Have you gutted the console and wired the keyboards directly to your diode matrix drivers? What are the existing stop drawknobs connected to? Same question for the pistons? You mentioned that you already have a combination action, Then you must have a conventional relay somewhere. How is it wired up? Confused, Johnc
  8. Trevor, That would be a good start, however, you said "Yes, the Midibox will be wired in parallel into the key contacts". This is a bit confusing. The midibox core can be used to encode keyboard contact closures (DINS module needed) into midi messages and send these out to remote devices such as a pc running jOrgan, miditzer, Haupwerk or some other device, or it can be the remote receiving device that accepts a midi stream on a pair of wires from the PC and converts the incoming midi messages back in to contact closures (DOUT module), or a drive source for a pipe magnet. Or it can do both at the same time. Would you explain what you mean by "wired in parallel into the key contacts". If you use a PC runnig finale or noteworthy composer, or some such software you will take a midi signal from the pc and the midibox core will have to be programmed with the correct midi channel, midi note# and type of midi message that the PC is sending out. If this is what you plan to do, then your setup will not have anything, directly, to do with keyboard contacts. If you are going to drive pipes, you will need the DOUT that has the ULN2803 driver chips on them. These are available from SMASHTV, http://www.avishowtech.com/mbhp/buy.html. You will also need a core module which you will have to assemble. Each core has an identifing code number, so you will need to specify that you would like the bootstrap loader and also the operating system MIOS be installed on the PIC 18F452 processor, and the PIC id be "00" since this is the first core. Each additional core will have an id number, 01, 02, 03 and so on. You will have to read up on the procedures for doing that in the wiki section of the midibox website. Good luck Johnc
  9. Trevor, The beauty of the midibox core is that it can be programmed to send out or respond on multiple midi channels. Each dout module has 32 outputs. The midio128 application can be programmed to accept midi messages on different channels. My organs uses two cores with four douts on each core. That gives me 4 ranks of 61 magnets, each rank on different channel, two ranks per core. On the encoder side, the same thing holds true. Each core can handle 128 inputs with 4 DINs. Each DIN has 32 input pins, each of which is programmable. You need to read up on the midio128 and its companion cards on the http://www. uCApps.de website. Again I also recommend you read through the "midification" thread. To answer your question, one core with 4 DOUTS will get you 128 outputs. How you divide them up among the 15 midi channels is your call. Johnc ps: Send me your email address and I'll email you some photos of my decoder setup. My email address is jwcouvillon@cox.net
  10. Trevor, As a beginning, I would recommend that you read the "Midification" thread on the current forum, end to end. That would give you a very base line knowledge of what it will take. To answer your question, there are midibox modules to provide all you will need to midify your organ console, and provide the necessary magnet drivers for the pipes. You don't really have to know alot about electronics, but you will have to develop some skill in following schematics and soldering. My home project over the last couple of years has been midification of a Moller 2 manual console and assembly, construction, fabrication, etc., etc., of regulators, wind trunks, windchests, blowers, in order to have a hybrid organ of 5 ranks of pipes playing with multiple ranks of electronics sounds either from soundfonts or wave samples. So far I have completed the base organ, i.e. console, wind supply, pipe chests for three ranks with the remaining two under construction. My system is based on the midibox midio128 modules for encoding the keyboards and the midi decoders and magnet drivers. Jim Henry stated it very well above, when he said that you will need a relay to run your organ. This became very obvious for me very soon after beginning my project, until I discovered jOrgan and miditzer. Both can be considered to be relays since they can provide most of the functions of a conventional, commecial relay. What attracted me to them was that they are "free", with lots of support through the forums for each one. The VTO software was developed to allow anyone with midi keyboards to use their home computer and stereo system and set up an organ. It just so happens that we can benefit from the same software as an actual computer based relay. In my case, At this point, I lean toward jOrgan and it can provide the relay functions for a theatre organ or a more classical organ. You did not say which type of instrument you desire, although your console is classical. Jim Henry's recommendation of Artisan products as a relay is well taken. You can put together a very fine relay with Artisan modules and limit your organ to the 20 ranks of pipes you already have, and if you so desire, couple it with other voices with jOrgan, miditzer or someother VTO software. Artisan is pre-built and bears a price tag considerably above midibox kit prices. It is possible to merge the two systems together using parts of each, but that will take some planning. If cost is not an issue, go for it. Otherwise read on. The other issue you need to understand is that with the VTO software( jOrgan, Mditzer, Haupwerk) the system is PC based and you will need a computer of sufficient computing power to run the system, not necessariy dedicated, but with ample speed, storage and memory. In my case, I am not interestedn having a computer monitor residing on top of the console, so all organ functions are sent and/or received through midi messages. The computer resides in the pipe chamber 30 feet from the console. My console is fully functional with stops, pistons, couplers, two manuals, pedal, swell and combination action. I have not implemented the cresendo pedal but could. Only one other feature is not fully developed and that involves powering the on and off magnets on the stop switches (SAMS). The combination action built in to jOrgan operates the stops, but they don't change position on the console. To my knowledge, of the VTO software available, only Haupwerk will do the complete organ, although the software is expensive. Upgrades to jOrgan are hopefully forthcoming, same for Miditzer. In a nutshell, thats what I am doing. It has been an in depth learning experience for me which has provided many hours of pleasure. You can email me if you have specific questions. Johnc
  11. QBAS, OK, my friend, I will take it easy. The reason I want to send you the photo is that the matrix is a PCB attached to the keyboard switches. I thought you would want to see what we are working with. As for a test, I don't have a core and DINX and DOUTX to use for a test. I will order kits from SMASH and get back with you when they are complete. I would include photos in my post, but I do not have a website on which to locate the photos. If there is a way to do that by direct insertion into the post, somebody please give me some input. As regards, documentation, yes I will be happy to do what is necessary, and yes, your text is hard to follow. Forgive me for feeding back my understanding of what you put in your post in my own words, but if i don't understand, thats the only way for me to confirm. For all interested, I agree, best we keep this on the forum. I'll get back with you as soon as I have hardware to use for the test. Johnc
  12. QBAS, I am reviewing your last post, and have many questions. Please email me at jwcouvillon@cox.net with your email address so that I can send you photos, schematics, etc., of the keyboard pcb's. Questions: 1. The code you provided is loaded as an application on top of mios? 2. There is no .ini file to configure the inputs and outputs. Its hard coded in the program? The configuration data youi used is same as in my post, with changes? 3. Hardware will require 1 MBHP core, one DINX module(32 pins) and on DOUTX module(32 pins). The DINXs and DOUTXS are wired to the core as in midio128 app. by interconnecting J8 and J9 to the I/O PCB's? I understand the pin order for the DINX, but the pin order for the DOUTX is confusing. Is "SR", "Shift Register"? So looking at the DOUTX Schematic, counting from the J1 end of the board, the SRs (74H595) are numbered 1 through 4. The pin numbers for SRs are: SR PIn # New Pin#SR1 New Pin# SR2 New Pin # SR3 New Pin# SR4 0 31 23 15 7 1 30 22 14 6 2 29 21 13 5 3 28 20 12 4 4 27 19 11 3 5 26 18 10 2 6 25 17 9 1 7 24 16 8 0 Is this correct? Do the column numbers of the matrix correspond to the pin numbering, ie. col#1 is DOUTX SR4, pin 0? QBAS, I appreciate your hard work and speed with which you have come up with the code, however, This is a beginning project to assemble a new complete console, including fabrication of a true theatre organ cabinet with horseshoe stop tab rail, three manuals, etc. All of the devices are included in the matrix and it will take me some time to complete the project. Since you have hardcoded the configuration, I will need a table to identify switch assignments withing the matrix (row, col) so I know how to wire from the DINs and DOUTs. Please review my questions and answer as best possible. Considering the potential length of future posts, I feel it best that we go to email to continue. Best Regards, Johnc
  13. QBAS, Be advised that there are two errors in the data I posted: The Pedal has 32 notes, the correct range is C2 (Midi 36) to G4 (midi 67). Also, note C7 is show as midi note 97 on all the keyboards, the correct entry should be midi note 96. Sorry about the mess up, Best Regards, Johnc
  14. Hi Tim, First of, the coils are not energized continuously. They open the pallet valves that let air in to the pipes. The coil is energized as long as you hold your finger on a key. No problem with this. The magnets are anywhere from 40 ohms to 150 ohms, most common 90 ohms, and are rated for 12vdc. These are standard designs that have been around for decades, nothing new. I have no idea what the coil conductor is, probably # 30 awg or smaller magnet wire, nor do I know what the number of turns is. I do know that I have one core receiving mididecoder, note on - note off messages with the douts (with ULN2803) and driving pipe magnets, and all of a sudden the midimerger doesn't work, and one note is missing, like the ini file has been corrupted deleting or erasing one entry. I'm still suspicious that the power supply has something to do with it. Regards, Johnc
  15. Hello Jim, thanks for the reply. Actrually, the magnets are no the pipes themselves, not on SAMS, and are only energized as long as you hold your finger on a key. I always thought the diode on the ULN2803 was more to prevent interaction inbetween drivers. Any way, whats to keep the spikes from coming back through the power supply, or the common ground? Johnc
  16. Gentlemen, On the same general subject. I am developing the 12v power supply for the ULN2803 drivers driving magnets, from a 12.6 volt transformer with traditional bridge rectifier and Cap. The transformer has a center tap, so I am deriving the 6 volts for power supply to the midibox cores from the center tap to one leg of the transformer (ac side of course). Is it possible for some switching spikes, surges to be developed with the magnets switching on and off rapidly, that could get back into the PIC with this arrangement? Could a shunt capacitor on the dc side of the 12vdc supply supress the spikes? What value cap would be needed if this is possible? Thanks, Johnc
  17. QBAS, Ok, a 32x32 matrix would do nicely. NOt sure what you mean by ranges of note on/note off. Midibox should seed note on note off message as in the ini file for the midio128. You will note that i changed up the table below somewhat, less channels. If you are not famliliar with the midio128, you should take a look at it. I agree with Jim Henry in his post above. If what I have provided is not what you are asking for, please let me know. Device Number of keys Channel Note range Midi note Main 61 1 C2 to C7 36 to 97 Accompaniment 61 2 C2 to C7 36 to 97 Solo 61 3 C2 to C7 36 to 97 Pedal 32 4 C1 to C4 24 to 71 Stops 64 5 C1 to D#5 24 to 75 Stops 64 6 same Pistons 36 7 C1 to B3 24 to 59 Swell on Great 12 8 C1 to B1 24 to 35 Swell on Accomp 12 8 C2 to B2 36 to 47 Swell on Solo 12 8 C3 to B3 48 to 59 Cresendo 12 9 C1 to B1 24 to 35 * Middle C is C4 Johnc
  18. QBAS Thanks for the reply. I will work on the list of questions. First of all, forget about pitch blend, velocity and all of that stuff. The keyboards are pure and simple, on/off switches. However, there is one important point that needs to be made and it didn't occur to me earlier. the keyboards will be used with virtual Organ Software. These programs recognize a different midi channel for each keyboard, and all of the other devices i.e. pistons, stops, swell shoe need to be on different channels also. with an 8x8 matrix, the number of points just about consumes the matrix, so it can be on its on midi channel. The 16x16 or 8x24 or 32x32 won't work with virtual organs unless the encoder program can assign a differen midi channel to each group of switches. Normally they keyboards and devices are assigned midi channels as follows: Keyboard No. of Keys Midi channel [table][tr][td]Great 61 1 Accompaniment 61 2 Solo 61 3 Pedal 32 4 Stops 128 5 Pistons 33 6 Swell on Great 12 7 Swell on Accomp 12 8 Swell on Solo 12 9 Cresendo 12 10[/table] Total switches 428 It would be great if the program would be similiar to midio128, and the config of the midi messages could be done in an INI file. Again, if specific midi channels cannot be made, then the large matrix will not work. The solution will be to use multiple 8x8 matrixes each on a different midi channel. Thanks much for the help, I appreciate it. Johnc
  19. QBAS, Thanks for your reply. The devices I want to include on the matrix are dry switches on a pipe organ console, no velocity, or anything like that. The total count for the keyboards and pedal would be 215 (3 ea at 61, 1 at 32). It would be good to add the stops, pistons, etc to that number, to bring it up to 256, but 256 won't cover the total. The three keyboards are idential, actually wired as 8x8 matrixes, with the 8 rows connected together to form a 8x24 matrix. To get a 16x16 matrix, I will have to separate the rows. The pedal board consists of 32 individual key switches, no matrix, but can be wired that way I am currently using two midibox cores with 4 DIN modules on each, to encode 2 keyboards, pedal, stops, pistons, swell, and will reuse thecores and DIN's with the matrix. A matrix covering the three keyboards, plus other switches to get to 256 would be on one core if possible, and the second core would cover the balance in normal DIN fashion with midio128 would work great for me. To answer your question, I and not code literate! I am learning assembly language code, but cannot put a complete package together. Currently, the midio128s that encode my keyboards send out "note on/note off" midi messages. I am familiar with mios, and midio128 i.e., and know how to setup the .ini file, load the programs, etc. Question: Does the 16x16 matrix work with a modified midi0128 app? With a 16x16 matrix, do you still have a .ini file to set up the type of midi messages sent ont. thanks much for you willingness to help me, I appreciate it. Johnc
  20. QBAS, If I add all the other things I need to the switch matrix, I think that a 16x16 would cover the ground. Did you write the code to go from 8x8 to 16x16? Would it work for me. I am not sure what the velocity business is, however all my switch inputs are just open close switches. What App program do you use with a 16x16 matrix, midio128? How do you match up the switch positions with the .ini file? With the standard DIN and Midio128, each pin is programmed. Is t here a special .ini format for the 16x16? Thanks, Johnc
  21. QBAS , Thorston You are absolutely correct, and I do intend to use midibox designs for the encoders. I just didn't want to tear out any components before I knew exactly what to tear out. I have reviewed Thorston's circuit diagram for the 8x8 matrix and it uses only one 8 bit chip on the DIN (74HC165) and one 8 bit chip on the dout (74HC595) for an 8x8 matrix. The three manual keyboard stack is wired as an 8x24, 8 rows and 24 col's. In terms of midibox, the dout is connected to the rows and the dins are connected to the columns. So to run an 8x24 matrix, I would need one DOUT chip, and three DIN chips connected as in Thorston's example. Thorston, will this work with the app examples listed on the website, or is come additional codeing needed. I would prefer to do the encoding with one core if possible, rather then three. Also, the diodes are in backwards from Thorston's example. The cathodes are wired through the key switch to the row bus. They are not directly connected to the common row bus. Any help would be appreciated. Johnc
  22. Hello QBAS, Yes you are correct, I traced out the circuitry and can very easily delete the existing chips and use midibox devices to implement the switch matrix. However, the existing design looks a all three keyboards in one matrix and scans them all. One chip a 74c42 is a BCD to Decimal decoder. there are 4 inputs to this chip, the connection points to the pc bd are mared c8, c16, c32, c64. Eight of its ten outputs feed the rows of all three keyboards in parallel. Three 74hc151 8 input multiplexers are used, one for the columns of each keyboard. There is one output from each multiplexer, and three inputs which are marked c1, c2, c4. So th 7 inputs and three outputs. Since I don't have the rest of the circuitry, i don't know where the inputs came from or where the outputs went to. However, There was probably a processor or clock producing a 8 bit binary number, and the c1.2.4.8.16.32.64 came from it. The mux output from each of the multiplexers was a serial train that probably was processed by a processor to a specific note, activating an oscillator, etc. Evidently no midi was involved. My question is how to configure the matrix, midibox dins and outs with the pic core to scan all three keyboards. Johnc
  23. Thorston, I recently "liberated" a three manual keyboard assembly from a "Saville" electronic organ. In its present form, each of the three keyboards is wired in an 8x8 matrix with a diode in series with each key (blue band on the diode on the switch side), installed on the opposite side of the key switch from the common bus(row- with 8 switches per row) Each keyboard is wired to a small pc board with a 74hc151 chip, and there is one pc board receiving feed from the 8 row inputs of each keyboard all connected in parallel. The row pc board has a 74C42 chip on it. Needless to say, I don't have a schematic for the keyboards, and don't know what the cabling from the keyboards connected to. However I would like to use as much of the installation as possible. Actually, since the keys are attached to pc boards with the diodes just as you show them on your example schematic, It would be easy to use a core for each keyboard and merge them, or set up a dout and din as per your example and the setup in the referenced website(below), daisy chaining them with one core. I have reviewed your download examples 1 and 2 for setting up an 8x8 matrix and also found an example using that data on line at "http://www.midibox.org/dokuwiki/doku.php?id=midiboxkb_-_using_a_c64_keyboard_as_input " which uses your example to encode a C64 keyboard. I don't see why that method won't work on a keyboard. However, I have 3 keyboards and also a 32 note pedal. Your example indicated an upcoming example of how to extend the matrix to up to 1024 buttons or switches. I don't need 1024, but half that number would be great. Can this be done with one core, two, three? My existing system uses two cores with 4 DINs on each, encoding two keyboards, pedal, stops and pistons. A 32x32 matrix approach would simplify the wiring, reduce the number of DINs and increase the number of switches available. If anyone reading this post knows of a source for schematics for the "saville" organs, please email me at jwcouvillon@cox.net. Regards, Johnc
  24. Jef, Your work is interesting as I am trying to use midibox to control a dc motor (servo motor, stepper) on pipe organ swell shades from a poteniometer mounted on the swell pedal. Does this relate to what you are doing. Johnc
  25. Thorston, The motor required to move the shades will probably have to be a high torque unit. Will that be a problem to drive it from the FM module? Johnc
×
×
  • Create New...