-
Posts
25 -
Joined
-
Last visited
Never
About superfeed
- Birthday 01/01/1
Profile Information
-
Gender
Not Telling
superfeed's Achievements

MIDIbox Newbie (1/4)
0
Reputation
-
Thank you very much for your patience Cimo. The button program worked. It was very nice to see them light up. Current status: A. I have now reloaded MB64, and realize that what I have connected to pins 9-16 on the DIN corresponds to LED's connected to pins 1-8 on DOUT. B. In MB64, the LED's only flash as the button is pressed and then go out again. I assume that (A) is because of definition in the setup_midibox64.asm file. Is (B) the LED's not toggling also a function of the setup file? Thanks, John
-
Okay, I have spent many hours trying to understand this now, and the leds are not lighting up. :'( In my MB64 v2 I have only one DIN and one DOUT module connected. I am using MIOS V1.9F. The buttons are working fine. My DOUT board is an R2 from Smash. If my understanding is correct from the posts I have looked at (many times) the default would be for when the button toggles, to turn the led on or off, right? Do I need to have all 8 SR's (both DIN's & DOUT's) connected? I checked the output pins on the header of the DOUT board and I cannot find any voltage on any of the outputs regardless of the button state. I have never programmed anything, so the asm files are perplexing. :-\ Any guidance or ideas would be of great help. Thanks, John
-
Thanks Cimo Seems like I had them all grounded. I removed the three wires from J6 grounded all the pins except +5, ground, and tied one fader to the input. It worked! Cool..., okay, I will try to get just one 4051 working now. I also noticed that the response was reversed, I guess I have my +5 and ground swapped to the fader.
-
Hi All, I have a 18F452 that came with V1.9F MIOS. I loaded setup_midibox64.hex file from midibox64_v@_4b. Let me qualify that I am a complete idiot regarding midi. I have never used it for anything, but I am hoping to use it to control my yamaha dsp2416 cards and Sonar. My core is attached to to AIN boards. I have one AIN wired to 8 faders. All other inputs to the 4051 chips are tied to ground. I loaded MidiOX and yokes. When I use midiox to connect my mpu-401 to midiyoke-1 and then use midiyoke-1 to control items in the software, the sofwarefader will just tremble, and not respond to fader movements. When using midiox to monitor the mpu-401 input, messages are blazing, constantly scrolling. Being new to midi, I don't know if there is a constant interogation of midibox parameters and therefore a constant stream of data? Or, should there be no data sent until I move a fader. I must say I wish I had never started this project so long ago. I put it away, and moved across the country, cry, blah, whine, blah... But, instead of pitching the whole mess, I would like to make it work. Any advice is greatly appreciated. Thanks, John :P
-
Thanks, All I've ordered 5 from Mouser. I Appreciate the help. John
-
Thanks Stryd, Are there many defective optocouplers, or is it possible I damaged it? John
-
Thank you Thorsten. I performed TEST IN7 on optocoupler. switch open/cable not connected = 5V switch closed/cable connected = 2V This means 6N138 is defective? John
-
Well, you all amaze me. I started with such high hopes more than a few years ago on a MBHP 64 project, then put it away as I got busy with other things. I feel technically inept. I thought that I should complete the box for better or worse, so I determined to make the box work (this might be my mistake). I am using a Smash TV board, pic, and components that I purchased 3.5 years ago. The pic is labeled MIOS_BOOTSTRAP_v1_1B All 0's underneath. I have attempted to use MIOS Studio to upload: update_without_installed_mios.hex When I start the upload with: Device id 0 "Wait for upload request before starting upload" checked and Smart mode I receive the following message: Starting upload of update_without_installed_mios.hex Hex file contains code in MIOS range, forcing reboot! Received Upload Request Sending block 00000000-000000FF Error: Received unexpected Upload Request (Sending block and Error repeated until abort) I tried the following from the midi troubleshooting guide: TEST IN1: Ok TEST IN2: Ok TEST IN3: LED stays lit (even with no message coming in?) TEST IN5: Ok TEST IN6: LED stays lit regardless of switch position Thank you for any help in advance. I should have just stuck to playing guitar. :P John Gregory :
-
A very ignorant question on a critical concept
superfeed replied to superfeed's topic in Design Concepts
Wow Justin, You have made things much more clear for me. I plan on using the minimal 2 x 16 lcd to begin with. I figure I can get more elaborate as I figure a few things out. Also, thanks for your advice on getting the core going first, then adding a bit at a time. John -
Hello all, :) I found this site a couple of years ago, and was blown away. Here and there as time permits, I have laid out a design, as I have found components at the local surplus store. I have designed a straightfoward setup with 17 faders, 60 some momentary switches, nearly the same amount of leds, 48 10k pots, and one encoder I scavenged off of an old Panasonic proffesional VCR. I am having no problem soldering this mess together and hooking it up, and am nearing completion. How does the MIOS work? I have never used midi before, other than an old alesis effects unit that I controlled with a footswich. :) I am going to use my midi-box to interface with a software called C-Console that I use to route audio on a yamaha dsp2416 card, as well as Cakewalk Sonar, that I use to record audio with. both of these apps can learn the moves from a midi device. How does MIOS help me to interface the midi-box with this stuff? Do I just load the MIOS into the computer, and it recognizes the midi-box? Is there a gui interface that I work with to make it go? Thanks for your input, I feel a lot of anxiety with the box coming together, and me wanting to hook this stuff up, and I don't have a basic understanding of how this stuff works. John Gregory
-
Very Cool Count me in please!! John