Urgon

AVE... I made a very, very stupid mistake and didn't program the uC at all. Mea maxima culpa. Even though it looked as if I programmed it. The first program code doesn't contain config bits, so I took them from bootloader. Even though uC is programmed properly this time, it doesn't seem to work. No USB communication at all. I'll recheck the hardware and try it with different computer running different OS... Bootloader doesn't work. And even if it worked, Windows won't install those drivers for some reason. They are too old or something. I had such driver issues with other hardware too. That's why I didn't follow your installation instructions... I had issues with compilation related to paths and missing files. I solved most of them but still was unable to successfully compile sources, though it made a hex file. Also I used wrong version of SDCC... I solved the problem finally - IC socket had connection problems. Device works now... I attached a zip containing my board design made in DipTrace, also two views of top and bottom side, and 300dpi black and white print version for thermal artwork method. Hope it'll help someone... MBHP-PIC-USB-IIC.zip

AVE... For various reasons I decided to make USB MIDI interface based on PIC18F4550. I designed board for it, programmed the uC and plugged it in. And it didn't work. I checked out the hardware part and it's good, then I checked programming part, and found few odd things. I have a couple of questions: 1. Why firmware sets odd configuration bits for microcontroller? For example external clock, instead of HS oscillator. 2. What are proper configuration bits? 3. Why you had to use GPASM and SDCC? MPLAB IDE is evil or something? 4. Does anyone know, how to set SDCC, GPASM and MinGW32 on Windows 7 x64, so it won't fail compilation every time? I set the paths correctly. 5. Could someone recompile the firmware for me so it could work with 4 IIC modules(when are connected)? Or make it MPLAB-compatible so I could use proper toolchain? 6. Could someone make simple code to test the USB comunication or post a link to working code for that test? For programming I'm using PICKit3 and MPLAB IDE v8.87(MPLAB X doesn't work too well with Win7), and PIC18F4550 Rev. 7. No, I don't want to buy GM-5 or use STM32 or LPC17 cores. I spent too much time and money on this already...

AVE... My good friend sent to me a E-mu ST 1200 service manual. We analysed its design and came with clever way to make velocity pads for any MIDIBox with at least 8 AIN ports. The basic version utilises one piezoelectric membrane as velocity/pressure sensor and 8 microswitches for AIN pin selection. Circuit diagram: It's just an amplifier/filter. RV1 is used to set pad sensitivity. Construction: Two piezoelectric membranes connected in parallel are between two metal or plastic bars, which are loosely joined together. On top are placed microswitches. Tapping one of them will send a pulse generated by membranes and amplified by circuit to one od AIN ports. This is the simple, yet working way... In more complex design you can use DIN imput(i.e. push-button 4x4 matrix) to force the Core to read data from AIN ports. Still at least one membrane must be beneath the buttons. This way you can eliminate adding contacts noise from microswitches. If you want to make a real dynamic keyboard, you must have original mechanical keyboard assembly from piano or something like that. Just replace strings with piezoelectric membranes and switches BENEATH them, so when hammer strikes any of them, you can get real velocity parameter. Switches should be connected to DIN module and write proper code for Core module... This is just concept. I wasn't able to test it, but I'm sure it will work. TLC27M4 should be replaced, since in some countries(i.e. in Poland) is impossible to find it. Probably any op-amp should work with this design...

AVE... Another question: My laptop doesn't have any RS232 or MIDI ports. Many USB<->MIDI converters are beyond my financial reach(either I'll have a working MIDIBox or working USB<->MIDI cable). Can I use PCMCIA<->RS232 interface and LTC module to upload MIOS and send SysEx dumps? Has anyone tried this?

AVE... I have some further questions regarding MIDIBox64E, and because I don't want to make too much mess, I'll place them here. 1. Can I use ANY MIDI-to-USB converter to send SysEx dumps and MIOS? 2. Can I have one AIN module with 2 DIN's and 1-2 DOUTs? Is there a software limitation? 3. Is software capable of using AIN signals as Note On/Off+Velocity messages? Ad. 2-3. - I'm working on a simple pad design to make a MPC60-style controller. If it works, I'll share it here... BTW, you should place a note at http://www.ucapps.de/mbhp_core.html page, that only PIC 18LF452-I/P or 18F452-I/P are good, I almost bought 18F4520...

AVE... Well, I'm just starting my PIC ASM education... I read about page selection buttons in MIDIBox64E, when there is less than 64 encoders, for example in 1 encoder version or 16 encoders version. I would like to replace these buttons with encoder... And another question: MIDIBox64E has support for 2*16 LCD display, but had anyone programmed support for 4*20 LCD? I decided not to complicate my work. My first MIDIBox will be simple as it is. But I still want the 4*20 LCD. Help, anyone?

AVE... I'm going to make a MIDIBox64E, and I have some basic questions: 1. I want to make 8 encoders with LED rings + 8 buttons with LEDs setup, but also use 2 additional encoders and LED rings to select banks separately for encoders and buttons to have 16*8 parameters controlled by encoders and 16*8 button controls. Is it possible? 2. Is it possible to add 7 segment LED displays showing value of currently rotated encoder? 3. Is there any designed PCB for making LED rings?