Jump to content

jwrigh10

Members
  • Posts

    31
  • Joined

  • Last visited

    Never

Posts posted by jwrigh10

  1. I have a Core with 4 DINS for a Midio128 project. These dins primarily run the pistons/buttons on the organ. However, one set of pistons is dupilicating the other set. For example, when I press the Pedal Pistons I get: 

    TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT             

    00093034  3  --    94    15    7F    5  A  0 Note On             

    00093101  3  --    94    15    00    5  A  0 Note Off             

    000933C8  3  --    94    14    7F    5  G# 0 Note On             

    000934A5  3  --    94    14    00    5  G# 0 Note Off             

    00093604  3  --    94    13    7F    5  G  0 Note On             

    000936C8  3  --    94    13    00    5  G  0 Note Off             

    00093858  3  --    94    12    7F    5  F# 0 Note On             

    000938F7  3  --    94    12    00    5  F# 0 Note Off             

    00093AD0  3  --    94    11    7F    5  F  0 Note On             

    00093B6F  3  --    94    11    00    5  F  0 Note Off             

    00094295  3  --    94    10    7F    5  E  0 Note On             

    00094333  3  --    94    10    00    5  E  0 Note Off             

    These are connected into DIN #1.

    When I press another set of buttons, which are plugged into DIN #4 I get several duplicates. Here is what I get:

    TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT             

    000BBBEB  3  --    94    14    7F    5  G# 0 Note On             

    000BBC39  3  --    94    14    00    5  G# 0 Note Off             

    000BC6C6  3  --    94    13    7F    5  G  0 Note On             

    000BC800  3  --    94    13    00    5  G  0 Note Off             

    000BCB29  3  --    94    12    7F    5  F# 0 Note On             

    000BCBE9  3  --    94    12    00    5  F# 0 Note Off             

    000BCBFD  3  --    94    12    7F    5  F# 0 Note On             

    000BCC12  3  --    94    12    00    5  F# 0 Note Off             

    000BCF03  3  --    94    11    7F    5  F  0 Note On             

    000BCF7B  3  --    94    11    00    5  F  0 Note Off             

    000BD221  3  --    94    10    7F    5  E  0 Note On             

    000BD238  3  --    94    10    00    5  E  0 Note Off             

    000BD24C  3  --    94    10    7F    5  E  0 Note On             

    000BD2A3  3  --    94    10    00    5  E  0 Note Off             

    000BD5E3  3  --    94    6F    7F    5  Eb 8 Note On             

    000BD601  3  --    94    6F    00    5  Eb 8 Note Off             

    000BD615  3  --    94    6F    7F    5  Eb 8 Note On             

    000BD698  3  --    94    6F    00    5  Eb 8 Note Off             

    000BD6AD  3  --    94    6F    7F    5  Eb 8 Note On             

    000BD6C1  3  --    94    6F    00    5  Eb 8 Note Off             

    000BDCAF  3  --    94    15    7F    5  A  0 Note On             

    000BDCEE  3  --    94    15    00    5  A  0 Note Off             

    000BDD03  3  --    94    15    7F    5  A  0 Note On             

    000BDD17  3  --    94    15    00    5  A Note Off             

    000BDFE2  3  --    94    16    7F    5  Bb 0 Note On             

    000BE05B  3  --    94    16    00    5  Bb 0 Note Off             

    I have reloaded the sysex file and checked the .ini file, but cannot figure out why I am getting these duplicats. Could this be a short int he board? Any thoughts?

    Thanks

  2. Thanks for the response.Yes, I am using a Midio128 project. I have a core with 4 din units. All are working fine, however, on Din 4 J6 I am getting the exact same response (148 20 127 5 G# 0 Note On) as I do Din 1 J6 (148 20 127 5 G# 0 Note On). I get this same response for 7 of the 8 pins; however 1 pin on Din 4 J6 registers in the range it should (148 111 127 5 G# 0 Note On). In other words, the Din 4 J6 pins should be reading 111-118, but instead they read 22-16 with the exception of 111 and for some reason they are duplicating the same as D1 J6. (I hope this make sense.)

    Unfortunately, I lost the original ini file and was wondering if there was a problem with the original file. Quite frankly, I don't remember how I uploaded it in the first place since it has been over a year. I guess I am hoping I don't have to go back through all the research and learning again ???. Any thoughts are greatly appreciated.

  3. I have lost my ini files for my keyboards and pedal board. It has been over a year since I created them and they have been apparently wiped off my system  ???. It has been a year since I created them and I don't want to have to go back into intensive learning mode or reconstruction unless absolutely necessary. Is there a way I can upload them from my cores?

  4. I'd swap the shift register with one connected to a set of non-malfunctioning pins. If the problem persists on the same pins there has to be a short somewhere on the board. If the problem moves to another set of pins you have a faulty shift register.

    I swapped the shift register wiith a one connect to a set of non-malfunctioning pins and got the same result. I did this twice and had the same result. Therefore, there must be a short.

    jw: by your description it seems that you are not receiving a duplicate message, but a message corresponding to the neighbouring pin. You only explained the behaviour of one pin, so it's not clear whether shorting pin5 also triggers pin6, shorting pin6 also triggers pin5

    or shorting pin5 also triggers pin6, shorting pin6 also triggers pin7

    When I press the button corresponding to pin 5 I get "94 29 7F 5 F note on" and "94 2A 7F 5 F# note on." Also, when I press the button corresponding to pin6 I get "94 29 7F 5 F note on" and "94 2A 7F 5 F# note on" (i.e., the same message). Both pins are giving me the same message. Pin5 should give me "94 2A 7F 5 F# note on" and pin6 should give me "94 29 7F 5 F note on."

    I put another cable on the J5 pins and had the same problem at the same place so it is definately in the board.

    How do I track down a short in the board? I have visually checked it with a magnifying glass and have found no shorts. Is there any other way I can track down a short on the board.

  5. I am apparently experiencing an issue with one connection (J5) on a DIN module. When I press buttons corresponding to pins 5 & 6 I get two midi messages per pin. For example, a normal message is: 94 2D 7F 5 A note On. However, when I press a button corresponding to these pins I get: 94 29 7F 5 F note on and 94 2A 7F 5 F# note on. In other words, I get two sets of midi messages per pin.

    Here is what I have done to troubleshoot

    1. Replaced the cable connectors-same result

    2. Plugged in another cable (from J4 for example)-which did not give multiple messages on J4 pins--same result on the J5 pins

    3. Plugged in a good cable (e.g., the one from J4 which works fine) into J5-same result of multiple messages

    4. Checked midio file-could not find a bug

    5. Visually checked DIN-could not see a problem.

    Does anyone have any suggestions. All the other ports (J3, J4, J6) work fine. I just have these 2 pins on J5 that are triggering multiple midi messages.

  6. I have two modules which work fine for my midio128 project. However, I wanted to enable one of the cores to allow for a volume pedal. I hooked up the pot as instructed; yet, when I tried to upload the appropriate hex file to enable the operation of the volume pedal, I could not get mios studio to upload. I checked all the connections from the interface to the core an the mios studio connections to the interface. I followed the instructions on the Mios studio page concerning uploading with no success.

    I am running v1.9e so I changed course and tried to upgrade to v 1. 9f but with no luck. I know the core is receiving and sending information via my led lights on the midi interface. Also, I can open Midiox and see that the core is receiving input. When I failed at the upgrade of one of the cores, I tried the other-again, no luck.

    I am running the latest version of a driver for my midi interface (a Motu 2x2 USB Fastlane)

    The Midi Interface troubleshooting page talkes about upload the mios in midiox; however, I do not see how you can upload a hex file in midiox.

    Once again, I can play the instrument with the cores with no problem, but I am having difficulty getting either core to accept a hex file. Any thoughts will be appreciated.

  7. My core reset issue has been resolved. Apparently, linking the cores using J11 is not the best for organ midification. When I linked the cores via midi cables, the problem disappeared. I also powered each core with its own power supply. Thank you all for your help. I am off to the next phase of my project-which will involved another midibox core!

    Jim W.

  8. Removed optocoupler from first core unit: Still getting a reset message!

    Removed optocoupler from both cores: Still getting reset message

    Removed optocoupler from second core unit: Still getting reset message.

    Checked sysex file and changed MidiMerge to "enabled" for both cores: Still getting reset message

    Getting frustrated.  :-[

  9. Sorry for the delay.

    Here are the results from the core tests:

    Core 1:

    IC1 pin 1:4.99v

    IC1 pin 11: 4.99v

    IC1 pin 20: 4.97v

    IC1 pin 26: 4.99v

    IC1 pin 32: 4.99v

    IC2: pin 8: 4.99v

    Midi Out: 4.99v

    Core 2:

    IC1 pin 1:4.98v

    IC1 pin 11: 4.98v

    IC1 pin 20: 4.92v

    IC1 pin 26: 4.99v

    IC1 pin 32: 4.98v

    IC2: pin 8: 4.98v

    Midi Out: 4.97v

    PSU set at 9vDC

    Connected cores together at J11: Voltage tests consistent when tested individually.

    Swapped the  PICS and Optocouplers between the two cores.

    Ran MidiOX

    Test 1: Both keyboards (Core 1): Okay. No resets despite large "hand fulls" of notes over several minutes

    Test 2: Pedalboard (Core 2): Okay. No resets despite large "hand fulls" of notes over several minutes

    Test 3: Connected Cores via J11 with PSU and MIdi cables attached to Core 2: Tested Keyboards alone: Okay.

    Test 4: Connected Cores via J11 with PSU and MIdi cables attached to Core 2: Tested pedalboard alone: Okay.

    Test 5: Connected Cores via J11 with PSU and MIdi cables attached to Core 2: Tested Keyboards and pedalboard: FAILED. Reset message appears after only 15-30 seconds. Occassionally, other messages such as "aftertouch" randomly appear.

    Test 5: Connected Cores via J11: Tested Keyboards and pedalboard with PSU attached to Core 1 : FAILED. Reset message appears.

    Test 6: Connected Cores via J11: Tested Keyboards and pedalboard with PSU and MIdi cables attached to Core 1 : FAILED. Reset message appears.

    Test 7: Tested with another midi interface (Motu Fastlane USB) connected to faster computer (Pent. 4 Core 2 Duo): FAILED. This time multiple random messages appear such as "Piano"; "Electric Piano," etc.

    I cannot seem to make one core reset. It only occurs when both cores are connected. They seem to get overloaded and random messages, including a system reset, begins to appear. Thought it could be an interface problem, but the use of a second interface seemed to rule that possibliity out. Any other thoughts would be appreciated.

    Jim

  10. I tried a radio shack PSU with a 9VDC and 1000mA. Same result. Core resets when I play both keyboards and pedals. Am not sure which core resets or if both do it. I will replace the 7805's next and see if that helps. Any other suggestions would be appreciated.

    jim

  11. I found a 3-12V Regulated 1000mA AC Adapter from Radio Shack. Would that do the trick? If so, do I have to remove the 2200µF cap and the regulator from the 2nd core? Is the amperage a major issue? I thought it had to 500mA. Also, is AC better than DC in this application? My PSU is DC perhaps that is my problem. Sorry to be such a pain! But I am learning alot!

    Jim

  12. I won't remove the bridge. I did some experimenting and it seems that when I am pulling from just one core (e.g., Keyboards along) I do not get a reset message no matter how much I throw at it. Could it be that the cable which connects the core is losing some voltage? I was surprised to find that the J11 to J11 connecting cable powered the second supply. I thought you powered the other supplies by connecting the J2 connections to each other. Should I be doing both? Would simply having the second core powered by its own power supply be an easy fix?

    Jim

  13. The power supply is about 6 months old. I do have another one that is 6v 800mA. I have not removed the bridge rectifiers yet. Should I try to find a 10vAC power supply instead. BTW, what I have is a power adapter. I don't know if there is any difference.

    Jim

  14. Thanks for the comments.

    Being a Newbie, I have no clue what stuffed cores are  ;D

    When you say "skip the bridge rectifier" are you recommending I desolder it from both cores? What if this doesn't work?

    You recommend "getting a supply with higher voltage at output." The voltage supply I have can go up to 12 volts. Is that what you recommend? Would I burn something up if I increase it to 9 or 12 volts?

    Is there a particular power supply you would recommend?

    I don't mind purchasing another 7805 but I just hate to wait another 2 weeks to get it.

    Jim

  15. I have midified an organ. I can play for a minute or so and then the system resets. It will immediately begin working again. What could be causing the reset? I am powering it with a 500mA power supply set at 6 volts. (it said it is a 5 volt power supply, but the only options are 4.5v and 6v.) The power supply is connect to one core and that core is connected to another core on J11 terminal. I did not run power from the J2 of the primary core to the J2 of the secondary core as it is getting power from the cable. Any thoughts on why the system is resetting?

    Jim

  16. I have successfully changed my midio128.ini file for the keyboards of my project. However, when I went to update the 2nd core, I cannot get the batch program to convert the midio128.ini file. I have revised the file, saved the file and then click on the "make" icon, but nothing is changed. The time stamp on the .ini file is an old one and does not reflect that a change has taken place. When I test the file in Midiox, I get the old .ini file! 

    I have deleted, reloaded the mk_midio128_syx multiple times, but to no avail. Is there another way to do this? Is the Pearl program messed up? Any thoughts would be appreciated.

  17. I have 2 keyboards and I need one to work on Channel 2. When I go to the mk_midio128_syx folder I get a "midio128" folder which is the "ini" folder. However, when  I click on the file to edit it, I get this message at the top "This is an example init file for MIDIO128." Where is the real "ini" file? Also, after I edit it, do I simply run the "Make" program to upload it? One post suggested using Pearl. I have dowloaded this program, but have no idea how to use it. Am hoping there is a simpler way.

  18. I unzipped the http://www.ucapps.de/mios/midio128_v2_1d.zip, opened Midiox, followed the instructions and uploaded the file marked "main." Everything seemed to work and I recieved readings in both the Monitor Input and Output windows. In addition, I have uploaded the SysEx files from "mk_midio128_syx." I also uploaded the "main.hex" file from midio128_v2_1d.zip in Mios Studio

    My LCD reads: OKOS "V3.; g"""""3+Novg" C_2""" I know that this is not right. Is it possible that I have really messed this thing up?

    JW

×
×
  • Create New...