Jump to content

John_W._Couvillon

Members
  • Posts

    350
  • Joined

  • Last visited

Everything posted by John_W._Couvillon

  1. TK, Not good news! Do I understand then that there is no way to get the AINSER8 working? This is confusing. The circuitry is provided. The interconnection diagrams to connect to the LPC17 are provided, but there is no firmware to finish the deal. Did I miss or mis-read something in the literature? Evidently I am the only midibox user that has ever tried to use an LPC17 to midify an organ with swell shoes and cresendo pedal having pots. If I am misinformed, i would appreciate someone setting me straight. As I recall PER S published a fix to midio128 ver. 2 running on a core 8, a couple of years ago. My setup includes a core 8 which could be uised for the swell pedals. Question: Will the resolution be better then with the LPC17 running midio128 ver. 3? TK, since I have a fully functional, headless, 12 Rank Theatre organ, SAMS and all, built around the LPC17 and midio128 ver 3., but only half playable with out swell shoes. I built the AINSER8 because an organ doesn't neet 16,32 or 64 ADCs, only 3, and that is what the AINSER8 is perfect for. I hope the AINSER8 firmware is not too far down the wishlist. I am aware that the overwhelming majority of users of the LPC17 are other then organ guys. However, the LPC17/midio128 ver3. combination is so very close to being the complete deal. You helped get functional hardware and firmware going to midify SAMS, and everything else on the electronic organ. Getting the AINSER8 working would be the final step. I'll donate a case of beer to your cause if it will "grease the skids"! Johnc
  2. Not sure if this topic belongs here, but anyway: Can mios studio be re-compiled or whatever to run on Linux Puppy Frugal? Its really difficult to operate the LPC17 without access to mios studio. If so Can someone talk me through that process? Would really appreciate the help/ Thanks johnc
  3. TK, Forum. As a work around for the low resolution of analog inputs to the LPC17, i build the AINSER8 for use with the pots on my organ swell pedals. Using the control surface for setup, there is a setup for an AIN and also an AINSER. Which of these should be used.? jOrgan is configured with two swell shoes, one on midi channel 0 and one on channel 1. The console swell shoes .seem to function, but there is no output from the AINSER8. that shows up as an input on the monitor in jOrgan. The LPC router is configured, but stil no input. Has the driver for the AINSER8 operating through j19 always been in midio128-ver3? I have not upgraded ver.3 since the initial installation. I am running jOrgan with linux puppy which does not support mios studio, so I am essentially running blind. I checked and rechecked the circuitry with nothing found. Voltage is present across the pots, and a variable voltage is present on the individual channel inputs to the AINSER8. Help Johnc
  4. Al, kPete, TK, just an Update! After re-arranging some wiring associated with the KB matrix cards, in particular the KB encoding the SAMS contacts, the problem with the GC and pistons has gone away. Evidently, the KB wiring must be kept short and care taken to isolate DIN wiring from DOUT wiring. That is difficult to do on a Theatre organ horseshoe stop Bolster as the SAMS are distributed all the way around. Still one problem still exists and that involves, SAMS not receiving the final tab off message. Everything works well on the "on" side, but on the SAM off cycle, the final tab off message does not come thru everytime and the off magnet stays energized. This happens on only one division, and just a few stops, and does not happen every time. I suspect hardware is the cause and will go through wiring, chip contact in the sockets, etc. Johnc
  5. wow, guys, lots of suggestions, all appreciated. 1. No to the +/- Sams question. negayive common SAMS with - common psus. 2. The matrix chain is working after a thorough check of all solder joints, and replacement of several chips, as well as new connectors. i had some wired spare pisrtons on te keyboard so i reprogrammed jOrgan to use a different piston as the GC and it works fine while the old one still does the same as previously. i will go thru the wiring from Pistons to matrix for some glitch. 3. All the DOUT chains are working, having done some upgrade to the PSU wiring to the DOUT boards. Also replaced one SAM that was not working at all. last issue to deal with involves the DOUT chain and SAMS on the great. After a GC, clearing all stops, 2 or 3 are remaining energized on the great, even though the tabs are off. They heat up quickly. i am in the process of replacing the 595 and the uln driver chips on the DOUT, so hopefully that may solve the problem. I also need to see if the disposition is corrupted. i have not tried using a shorter pulse time for the SAMS. It should be long enough to allow the feedback from the SAMS contact the receipt of which causes the SAMS extension in jOrgan to send out the off signal. Strangely, The disposition has 4 sams extensions, one per division, and the other stops on the great work fine. Johnc
  6. Update: the socket and both chips are replaced for matrix#4 on KB pcb#2. Evidently that was not the problem. Same issues as before, with a new twist. 1. Activating the stops on the desktop cycles the stop on and off both visually on the desktop and the physical stop tab as well for stops on the ACC, solo and pedal. cycling stops on the great not only activates stops on the great, but stops in other divisions as well, much like pressing a piston. 2. The GC physical piston still does the same thing with fluttering, activated stops, and activated then deactivated stops. pressing the GC again repeats the same action. 3. some Off magnets(on the great) are still not being de-energized , although in the off position. it appears that the SAMS extension in jOrgan is not sending out the final off message. next task is to remove the DIN and DOUT chips and trace all wires in the matrix for the SAMS on the Great. More later. johnc
  7. Kpete, Aeoline8, Found what i feel initiated the problem, The DOUT chip on KB matrix #4 (Sams contacts) is in fact bad, and failed while I was doing tests. the chip fused to the socket which will require some major repair. Al i will check to see if damage was also done to the DIN chip on that KB. you were correct on the wire issue, found two bad solder joints. FYI take a look at the revised block diagram below. I'll update the post after repair. Thanks Guys1 johnc
  8. kPete, I disconnected the kb matrix card that encodes the pedal and the SAMS contacts, and nothing changed. After some thought and checking i remembered that the way the SAMS extension in jOrgan works, after the note on message is sent out, if the SAMs armature moves, the sense contact closes. The SAMS extension looks for the closure, then sends out the off message. it also times out for 500 ms and sends out a second off message. So even if the sense contact is not working, the SAM will be turned off.. however, going through all of the SAMS, at least 1/3 were being turned off by the second timed note off, and the sense contact is not closing. This was confirmed by just toggleing the physical tab on the console. A close look at the matrix and circling the positions based on the hex note #, one full row is not working, and the other positions are random. i suspect a wire is loose for the row, but the random could be wire, or diode. I even found one case where both of the magnet off messages were not reaching the SAM, so it stays energized. need to look seriousluy at that one, so i don't burn up the SAM. More later. Pete, you are knowledgeable about jOrgan, Are you using a linux distro on the pc? johnc
  9. TK, the new topic name is fine! Still a bummer not being able to use MIOS Studio. i don't fully understand why puppy lucid is not compatible, but it does run the organ, so I shouldn't complain. In implementing kPetes test, I did find a problem that may be the culprit. one of two things has happened: some of the wiring in the matrix that monitors the SAMS sense contacts is messed up, or some of the diodes in the matrix are bad. Need some more digging to isolate the problem. I mentioned a power supply issue on another topic and was hoping for some comments. Many of my DIN and DOUT pcbs are early SMASHTV boards, designed before the additional 100uf caps were added on the 5v pins on the chips. This was for noise suppression, i suspect, and have concern that this could be some of my problem. In addition, the 12vdc PSU for the SAMS has a common ground with the 5vdc supply for the core 8 and jindirectly the dc supply on the LPC17. Any comments would be appreciated. johnc
  10. I went to Puppy because puppy linux lucid frugal will allow a power off shutdown and power on boot without keyboard mouse and monitor. I use it with jorgan virtual organ software and is installed in an organ console. one "on/off" switch. If Ubuntu 12.04 LTS or some other dispo will do the same thing, I am game. MIOS Studio is an excellant tool and i miss having access to it. How would I transition from puppy to Ubuntu? Boot with an ISO on cd then install to the HDD? johnc
  11. Kpete, TK, I put the post in this topic, since midio128 ver.3 is the basis of system operation. What catagory would you prefer, troubleshooting, midification? TK, the "GC" is the general Cancel, and for all practical purposes is just another contact input to the DIN chain. More specifically, the "GC" causes jorgan to send out off messages to all DOUT pins. per the message monitor in jOrgan, it is doing that, however, some on messages are also going out which shouldn't be. pete - the resistors on the matrix boards are 10K. As for loose wiring i must admit my guilt. in most cases the DOUT wiring to SAMS and matrix wiring from SAMS contacts is separated, but still in close proximity, 2-3". Strangely, the random situation is recent, has not been that way until recently. At Christmas time, i had to dis-assemble everything which was in a setup mode, i.e. pc, soundengine etc., although all midibox devices and wiring remained unchanged. during that time, i moved the PC so as to get linux puppy lucid loaded and setup to run jOrgan. You troubleshooting test sounds good to me and could be most helpful. i'll do it and get back to you. TK, MIOS Studio would be a great tool, but is asking for glibc2.15 before it will load. Evidently puppy lucid uses an earlier release. See thread in the MIOS Studio topics. Sure would be nice to be able to use it with linux puppy lucid 5.2.8! DIN cables that extend from the SAMS KB pcb (LPC17) to the SAMS are approx 5 feet long for the longest, 18" or so for the shortest.. the SAMS are mounted on a theatre organ style, horseshoe shaped bolster with a 2' +/- arc. DOUT wiring that extends from the DOUTs to the SAMS parallels the DIN wiring. There are 64 SAMS in all, bounted side by side around the horseshoe. There is no way to shorten the wiring. Thanks for the comments and suggestions. Johnc ps; the block diagram I attached needs updating, I'll post a better one.
  12. Anybody, Ok, i am confused! Do I have to change from puppy lucid to Precise 5.6.1 or Slacko 5.6 to use MIOS Studio? Is there not an "out of the box" version of MIOS Studio that will run under Puppy Lucid 5.2.8? Johnc
  13. alchmist, jimi_diller, TK This is a cross post, but is is possible to re-compile mios studio to work with puppy lucid as well. it needs glibc 2.15 as well. How is that done? I have been using mios studio (win version) and it is a wonderful piece of software, however my change over to linux puppy has forced me to the linux version. Can puppy lucid be upgraded to glibc2.15? johnc
  14. Alchimist, googling, i found the following: glibc version release date Puppies Debian Ubuntu 2.17 2012-12-25 - unstable sid, testing jessie 13.04 2.16 2012-06-30 - - - 2.15 2012-03-21 Precise 5.6.1, Slacko 5.5, 5.4 - 12.10, 12.04 2.14 2011-06-07 - - - 2.13.1 - - 7.0 wheezy - 2.13 2011-02-04 Slacko 5.3.1 - 11.10, 11.04 2.11.1 - Puppy 5 - - 2.10.1 - Wary, Racy, Fluppy - - Since I am using puppy lucid ver. 5.2.8, i would assume that it uses glibc 2.11.1. Chart didn't past well. Hope this helps. johnc
  15. Alchemist, i am a newbie to linux, and don't know the ins and outs of the terminal. with the console open, "Sh-4.1# " comes up. I don't know what that means! Anyway i typed in the sudo command as you listed it and got a text display to the effect it wasn't a command. I picked the Hd icon, opened the directory and managed to locate a "lib" folder which contained many files that start with lib...., including " libc.so.6". no files starting with a "glib...., uclibc or elibc" i wil try again if you can direct me what to do. I appreciate your help johnc
  16. TK, This is what i got when tried to execute: ./MIIOS_Studio:/lib/libc.so.6:version 'GLIBC_2.15' not found (required by MIOS Studio) Am i out of Gas! or can puppy's lib be upgraded? Johnc
  17. TK, all, Everytime i get a problem solved, another one comes in. Take look at the attached block diagram. The PC is now running linux puppy lucid (frugal), in a headless mode. One power on/off switch starts everything and the same switch turns it all off, thanks to linux puppy. The pc is running jOrgan (linux) ver. 3.14, which provides the desktop GUI and combination action. jOrgan appears to function without problem when operating stops, couplers, pistons, set and cancel using the mouse and GUI. See (problem 2) Problem 1: When operating from the console mounted devices, pistons, stops, etc., jOrgan functions but with one problem. if a gen piston is set with stops in all divisions, say 6 or 8 random stops, followed by gc., then the Gen piston is depressed, the SAMS turn on as expected. however, when the gc is pressed to clear the stops, multiple things happen: 1. The pre set stops turn off. 2. other SAMS turn on and stay on, 3. other SAMS flutter on and off. 4. pressing the gc multiple times changes the state of some SAMS, on to off and off to on . The same thing happens with division pistons, and the GC. Doing the above procedure with the jorgan message monitor on clearly shows the preset SAMS turning off, and also shows other Sams operating, i.e. on magnet turned on then off after slight delay per SAMS extension. Problem 2: Doing a close check of the state of SAMS which should have been off, the cooling fan on the 30A - 12vdc PSU came on. A close check revealed SAMS that were off, but hot, and when the TAB was moved, returned to the energized position, indicating that the SAMS extension had not turned the off mkagnet off. using the jOrgan message monitor, and cycling the SAM with the mouse showed that in fact the SAMs off magnet was still energized. Cycling the SAM using the mouse turned it off after a few cycles. My first suspecions are; a week magnet, misadjusted mechanical stops on the SAM armature, or possibily low voltage due to excessive load on the 12vdc PSU. However, it could be that problem 1 and problem 2 are related. To complicate things, note on the block diagram that the sense contacts on the SAMS are matrixed (with diodes) using a KB pcb, tied to an LPC17, whereas the piston inputs come through DINS on the core8, and SAMS drivers are on DOUTS with ULN2803 drivers also on the core8. There are 2 KB pcbs, #1 encodes two keyboards, #2 the third keyboard, and SAMS sense contacts. The keyboard maticies are configured to exit through midiout 2 on the LPC router which outputs messages to an Artisan Sound engine, along with activated/de activated messages for all SAMS, Pistons, couplers. 12vdc PSU Grounding was the subject of a thread some time ago as regards this setup. At this point I am puzzled. The system worked fine until recently. Any suggestions, comments, questions, troubleshooting tests, etc are welcome. Organ block Diagram - Ground.bmp
  18. All, Problem is solved. Linux is not the same as WIN!!!!! ALSA came to the rescue. johnc
  19. Thanks TK! My reason for needing mios studio involves midifications, so please check my post there. Thanks again!
  20. Anybody, I have changed from XP to puppy lucid linux, and am lost! 1. Will mios studio run on puppy lucid? 2. I have it downloaded to the root dir, but can't figure out how to extract and get it installed. If you know puppy lucid and can give me some s teps to follow to get it insalled, i would be in your debt. Having searched for hours, there is no simple 1.2.3, how to procedure to be found. Has anyone made a PET package? Is there a midiox for linux? Help, anybody johnc
  21. Lllehaze, anybody interested in midification; Great explanation on PSU design! You bring up an interesting point regarding use of caps for reduction of spikes, especially with operating frequencies above 40mhZ My midified organ console is built with midibox components from SMASHTV, some dating back to 2004. Back then, the small caps were not used on each chip as they are now on the recent kits. Recently I upgraded to an LPC-17 core merging it with an old 8bit core. the LPC-17 is used primarily for encoding 3 keyboard, and 64 SAMS contacts thru 2 attached KB cards. The 8bit core has 4 DIN and 4DOUT which handles pistons inputs, and SAMS coil drivers.. The system functions, but it is experiencing "cross talk", for lack of a better word. SAMS are being actuated by pistons when not set . The gen cancel clears set SAMS, but also turns on SAMS that were off as well. The system uses jOrgan and strangely, the behavior described occurs only when using the hardwired devices on the console. Actuating stops or pistons with a mouse on the display does not produce the same effect. The power supplys are simple; The LPC through the USB connection to the PC, and the core 8 thru a wall wart module. The SAMS operate with a 12vdc - 30amp powersupply. The negative side of the 12VPSU is common with the negative side of the core8 PS by virtue of the card design, and the ULN2803 drivers mounted on the DOUTS. Actually, there is a lot of 26ga wire floating around to act as transmitters and receivers, probably not good! Question; 1. Would addition to small caps on the core8 DINS and DOUTs help? 2. Would going to a better common, better filtered, regulated power supply for the LPC and the Core8 Help? 3. Would putting some type of caps on the SAMS coils help dampen out high freq. spikes and switching noise? Hopeing for some help, suggestions, etc. johnc
  22. Sven, Gramm Goode, anyone, I am running midio128 ver3. on an LPC17 and the USB port is connected to a pc running linux puppy 5.2.8,and jorgan 3.14. jOrgan does not find the USB audio for inputs and outputs, hence errors on the disposition. . All communications in betweeen the LPC17 and the pc is thru the USB link. Is there some setting, or additional linux software that needs to be loaded for the two devices to communicate? Johnc
  23. Given: P4 pentium, XP OS, midio128 v3, LPC-1 USB connected to computer, 2 KB matrix modules running In the 8x8 matrix configuration, the output routing is selected. in my case there are 4, 8x8 matrixes, 3 keyboards, 64 SAMS sense contacts (channels 1,2,3,5), all output to midiout 2 on the router. I am also running jOrgan, which outputs messages through midiout2 Question 1:: With the LPC's monitor displaying the midi ins and outs on the LCD, and depressing a key on any keyboard, the out2 on the monitor blinks. Manually setting a SAM stop tab does the same. The blinking is to fast to read the message for confirmation that the output conforms with the programmed value. is it also necessary to set the Router config? if so what source setting is required? Question 2: Does mios studio 2.4.4 monitor the midi out from the router? Johnc
  24. TK, Pete, Great! USB is up and running again. Thanks TK for the fix, and thank you Pete for jumping in to support me. johnc
  25. TK, Don't know where to put this post, so i will start here. At this point, my system (pc/lpc) is in a total state of confusion, including me. i really need some help straightening out the mess, even if it means back to step 1! PC: P4 processor, 2.8 mb running win XP prof, SP3. The GM5 driver has been "un-installed". LPC core currently has the latest rel of the bootloader, midio128 with latest rel of ver3. need to back up to releases that will work with the XP machine. Currently, the latest releases are not compatible with the XP USB driver. Kpete duplicated my installation and had same problems with USB driver. System capability I need: 1. One (1) usb port on the LPC to talk to the pc runinning jorgan ver.3.14 2. Where to find a copies of past midio128 ver 3 releases. Was using rel .005 beforeneed the latest release that will work with the XP USB composite driver. 3. Need only midi in1, midi out1, midi in2, midi out2 to work with the router. 4. Need a reliable version of mios studio (I have given up on the file Browser feature of ver.2.4.4). Johnc
×
×
  • Create New...