yaiy

Members
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About yaiy

  • Rank
    MIDIbox Newbie
  • Birthday 01/01/1970

Profile Information

  • Gender Not Telling
  1. resistance problem?

    TK, i couldnt find a referance to a sm_example2 anywhere in here or ucapps. i will try to connect a midibox interface i have and check i want it super low cost for handing out to kids that cant efford smashtv prices ;). i still hope i can implement stryd idea. ill look into it. http://www.soundonsound.com/sos/mar04/articles/synthsecrets.htm to show my love for the forum, here is a mini controller i made from a cigar box (very good material to work with) couldnt find a better place to post this(?)
  2. hi great forum. first i want to tell all the guys  that helped me on my last troubleshooting accident. hope its the right place. my problem now is not midibox specific,  but as this problem troubeled me in an earlier midibox project i ask. i made a "pressure sensitive" grid of digital switches, made from 2 pecies of thick aluminium foil with double sided sticky window sealing foam (see pic bottom). my problem is i am getting slow response from my "buttons". i am using a usb keyboard as logic. the keybaord has a matrix type logic so i am running 5 rows over five columns of plastic sheets with the aluminum foil sprey gload on the inside. my frst attmpt didnt work as the conductive aluminium tape i used was too resistive, long areas and not enough current running i guess. this prototype works mechncly but i was hopeing to get it fast enough to respond to thrown objects, like slingshot stubs. now it works only for touch. any other problems in the design? the usb provied a current of 5v thru the usb interface. from http://www.computer-engineering.org/ps2protocol/ this is a montage of the work so far (500k pic) http://img.photobucket.com/albums/v315/pixelpusher/slingshotMake.jpg
  3. The making of a Midibox64

    great work
  4. The making of a Midibox64

    looks great. are you planing to use a custom  pcb?
  5. din problem

    sorry. like this one for each ressitor?
  6. din problem

    thanks TK is this what you mean?
  7. din problem

    hi all, i have a problem with my project. i use the midio128 and when shorting the pins directly on the board (with a small piece of wireup)i get good results. problem is my  actual wires running to the on/off buttons are very long. some are 4-7 m long. when i push them, i get (on some) several on/off  messages. they are all traceable and reoccurring. as i mentioned before. i use wireup cables, i need them because the buttons are very close to each other. i had a problem managed. these are not standard buttons but 2 pieces of aluminum with a piece of insulator between them. when applying pressure to the top foil i close the circuit. trouble is there was a lot of on/off jitter. i fixed that by changing the debounce value in the  mk_midio128_syx. maybe i can fix these problem using a similar method? is there something i can change that will rise the tolerance of the buttons so they want be effected by false positives? please don't tell me to rewire  :P similar problems? http://69.56.171.55/~midibox/forum/index.php?topic=2893.0 there's also the thread about the added capacitors. will it help stable my inputs?
  8. write failure on mios

    thanks again. i will try to help with the wiki, a lot of oldforum links there
  9. write failure on mios

    revelation, my hheart is overjoyed i was uploading the WRONG mios128 insted of  the preciuos midio128_v2_1c.zip  73k  The complete PIC18F port of MIDIO128 i =, for 4 days and 4 nights was trying to upload the mk_midio128_syx.zip  11k  Creates SysEx Dumps for MIDIO128: midio128.ini -> midio128.syx it works. i whish to thank TK for you are a nice guy © and would be happy to walk your dog (if you have one).
  10. write failure on mios

    TK your some kind of psychic midigod . i wired a switch to my power supply (better then yancking it from the jampers to restart :))and i was able to get confermation to my sysbox packets sending. to all you lost souls, confermed packets looked like this. it worked for the mios1.7 upload, but for the mios128 i couldnt get it confirm, using the same method i only  was able to send. i switched to midi-ox and got this... check midi-ox config, it was defulat, the guide as info on how to change it, changed... good. but, the mios128 still wont confirm. not on any upload util. as it stands, im preaty sure i got the mios core on the core but no application. still trying
  11. write failure on mios

    current state: stil stuck, i get the ping when i power on the core, when in midiox. but nothing else. i can read and write to the pic using sysbox (only sysbox), and i get confermation on all packets. but no midi stream frusrating as hell, tommorw ill replace the octopelers, i already tried on several wintel systems using both soundblast thru gameport and thru yamaha usb midi adapter. frustrating, time is ticking but my midi is not
  12. write failure on mios

    UPDATE: i got it to work by changing the device ID from 0 to 1 in SYSXBOX i get conformation on every packet both for the mios 1.7 and the midio128 in SYSXBOX problem now is i cant seem to find the option to change the device ID  parameter in midi-ox. those anyone have a clue? i searched the midiox forum and docs  and came up with nothing. i think i need to change that in order to view  midi inputs in midi-ox for debuging before i head on to incorparate the inputs in my platform of choise, java.
  13. hello everybody i am having trouble with the uploading of the mios. first of all i got the usual conformation "F0 00 00 7E 40 00 01 F7" every 2 seconds. i then uploaded the mios ver 1.7 and got this errors note, i get the same error in midi-ox . i tried the midi loopback  and i get the prescribed result (same same) i built 2 cores and i tried it with both of them, same error. i am using the soundblaster pci gameport. updated the drivers. whats next? i looked closely at the soldering but i cant seem to find anything wrong. i also want to add that i get the " F0 00 00 7E 40 00 01 F7" once now, on power on. i searched the docs and i found out the 0E04 message is related to a writing failure. is that a problem of the midi-in midi-out, the pic or something else?
  14. large scale buttons

    thank you for the replay. i thought about using that windows osscilator to test the signal. but i cant figure it out completly. i orignaly planed on using analog inputs for the midi and cleaning the signal after using the host program. ill check that "schmitt trigger"
  15. large scale buttons

    hi all i am building a midi carpet based on the mios platform. i have a peace of clothe sandwiched between to pieces of PVC. on the bottom PVC there are 90 large 20x20 cm positive charged buttons. on the other side theres a negatively charged one big piece of aluminum foil. the carpet size is 2x3 meters. heres a pic the piece of cloth is a kind of resistor, only when you stand on the mat the button closes. my problem is i only built a small scale version of this, one meter in size. i was wondering if building it full scale will the large foil of aluminum would offer to much resistance. i hope I'm making sense. i guess what I'm basically asking is, can i use the same ground source for all the buttons at the same time? how can a measure a Resistance of a substance to know if it is too much? i first used buttons like the ones used in ddr diy kits, basically two slabs of metal with window insulator in between which is used as a spring. its mechanical and so it simply works great,  clean signal. but its to heavy and expensive at large qt. you can see on on the left of the pic. the new system is portable and (hopefully) it will work but the signal is pretty noisy. i think i need some kind of gate or process the signal again at the processor. (false positive and false negative are rare but they happen) thank you for any input yair