Scifo

Thank you, TK, for the answer. 1. We ran the mbsid_testtone and there is a tone coming from all 8 sockets, 3 of which produces a somewhat lower volume, but still a tone. Is it very strange that some sockets produce different db? 2. About the mbsid_interconnection_test_v2: Starting the test, it says you need to connect the multimeter to pin A0. Where exactly is this pin? Should the test be done with or without the SID-chips, or doesn't it matter? EDIT: Managed to complete the test. All pins, on all 8 sockets, are OK. 3. When booting up the synth after the 8580 setup-hex file has been loaded into all 4 cores, only 3 LEDs shine up and some of the SELECT buttons are not working. My gut feeling says that all hardware is working (or at least correctly assembled), and that something is not correct with the software. COULD it be that the USB MIDI interface haven't been able to completely transferred the hex-file to the synth correctly? That there are some parts on the software missing, hence some of the LED's and buttons are not working. Or is that an impossibility, cause the synth won't even start up if the hex-file hasn't been received 100% ? 4. To test the buttons/encoders, should we use the MIDIO128 for this? Are there any instructions on how to use this program? 5. Which SID-socket is the boot-up arpeggio played from (just curious)? Best regards /Scifo

UPDATE 2: As I've mentioned earlier, we have sound coming from the synth, so we know at least that one of the SID-chips were working. We removed both and tested with only one chip in SID 1A (the rightmost socket when facing the midibox), and there was NO sound. Moved the chip to 1B (second rightmost), and there we have sound. Tried with the other chip - same result. So both chips are working, but I'm worried that the SID-socket 1A is faulty.

UPDATE: We found Wilba's matrix LED-test in an old topic and managed to upload the test-hex-file and ALL LEDs are working! :phone: But why on earth are only 3 LEDs lighting up on boot-up? :pinch:

Thanx for the reply, TK. I have some questions straight away: 1. The word "application" means a certain hex-file, correct? In our case, we only needed to upload the 8580-version of the hex-file, right? No other hex-files (applications) needed? (We uploaded the .hex-file to all the 4 cores separately by switching the jumper, was that necessary or would it be enough to upload it ONCE to the master core?) 2. Firmware - is that the bootloader that was preburned from SmashTV? 3. In the manual, it says that on boot-up, the first row should read "E002 A001 Ld Chn. 1" but ours read "E002 PInt Ld Chn. 1". Is something wrong here? 4. So we have LEDs not lighting up as they should - how can we debug this? (and, is it possible that the LEDs are correctly installed, and something in the software wasn't installed correctly, thus making some LEDs not light up?) UPDATE: Ran Wilba's LED matrix test = all LEDs 100% working 5. It says in the manual that the first step is to click the LEFTMOST SELECT BUTTON. Nothing happens when doing so, which probably mean that at least one button is not working (probably more). I read something about an application called MIDIO128 - can we use this together with MIOS Studio to test if all the buttons are working? Again, a big thanks for the patience of helping us. We wouldn't do much progress without you. /Scifo

When starting up MIOS Studios with the Midibox connected, this is how the MIOS Studios look like. IS there a possibilty that the hex-file has been uploaded correctly, and that the Midibox is working, and it's just that Dad doesn't yet know how to change the sound? I suspect this, because when I hear the sound that he is playing, by controlling the Midibox with a midi-keyboard, the sound is identical with the sound that is being previewed in the SID Manual section "The fun begins..." first sound example. Same waveform, same sort of sound. Is it correct that only 3 leds should be lit when starting up the Midibox? If so, it might be all good and I just have to guide my Dad through the manual how to edit the sound. If we just can get the sound to change, I'm pretty sure that all is working well.

Ok, I got some new info. It seems like my father didn't give up on the USB midi interface and did some tweaking by himself. He is where we are now: Dad found a section about the jumpers and took some action, and it seems like he missed out on this earlier: This section: "J11 at the bottom of the board is used to switch which PIC's serial output is connected to the MIDI Out. You use this during uploading of MIOS and the MB-SID V2 firmware to each PIC. Place a jumper vertically across two pins to switch between the PICs 1,2,3,4 (1 is the master, on the right). Leave the jumper in position 1 when you've finished. All PICs receive the same MIDI In, which is OK during uploads and the MB-SID V2 firmware also requires them all connected to MIDI In. I've labeled this 1,2,3,4 and the Cores/PICs are identified 1,2,3,4 but the device IDs you burn into the PIC are 0,1,2,3." So it seems like the PICS were wrong positioned earlier, cause we did some progress in MIOS Studios now: After messing around with ID numbers (Querying on MIOS Studios), my dad managed to establish some sort of contact between MIOS Studios and the PICS and managed to upload the hex-file 4 times (one for each PIC). We got the message "Application is up and running" in MIOS Studios. (let me clearify here that we've NEVER received the message "Bootloader is up and running") Now, when booting up the synth, it plays a quick 8-note arpeggio, 3 leds are on and the display reads: E002 PInt. Ld Chn. 1 1---- Lead Patch We're able to play the synth from a midi-keyboard controller, but no matter how much we tweak the knobs, the sound never changes. The 3rd button under the display activates the LFO-menu, and the 4th button toggles the waveform. Uploading the .hex-file without having the "Bootloader is up and running" message wasn't probably a good idea, and I really hope nothing has been broken by doing so. I also started to think of the possibility that the Bootloader is missing in the PICs, even though I bought it from SmashTV? What would be our next step? Please help. Best regards Scifo

Just what I thought. The situation is, that my Dad is the one who has built the Midibox, and he lives in Sweden, and I live in Finland. Here, I have a Pro Tools system with an Mbox audio interface, and I'm sure the Sys-Ex is working on this one. I could of course ask my Dad to send the Midibox here to me, so I could do the uploading. But we really would like to test the Midibox before he sends it here, since HE is the one who knows about hardware, soldering, voltage etc... Well, that is OUR problem, and we'll find out a way :) Thanx for the help so far. Good to come to a conclusion of the USB Midi interface. I let you know about our progress. We're not giving up! /Scifo

The loopback doesn't seem to work. Since I'm using a USB-MIDI-interface it's not possible to plug the midi cables physically IN nor OUT from the computer, but I guess the loopback test should work anyway. Same with SysEX transfer - no ping arrives when typing something in the command window. The USB MIDI interface is a german goobay.de brand, bought in a shop in Sweden, http://www.kjell.com/sortiment/dator-kringutrustning/datortillbehor/keyboard-midi-ljud/midi-ljud/midi-interface-till-usb-p38862 It could well be that this USB MIDI Interface is crap.

When I boot up the Midibox, I get information in the MIOS Studios MIDI IN window such as: [2893.266] 83 00 00 Chn# 4 Note Off c-2 Vel:0 and sometimes: [2893.267] 83 00 00 Chn# 4 Note Off c-2 Vel:0 When switching OFF the Midibox, this information came: [3035.348] 83 16 00 Chn# 4 Note Off a#1 Vel:0

In the "MIDI IN" and "MIDI OUT" menues in MIOS Studios, I am not seeing the Midibox option there. I can only choose my internal sound card "Microsoft GS Wavetable Synth" or the USB-midi device (the cables I'm connecting the Midibox to). I've tried uploading the .hex file using both options, but nothing. I don't see the Core-info in the Query-window, and the upload stops automatically when I start it. I'm checking midi troubleshooting guide, but can't come up with anything. Suggestions?

OK! Are there detailed instructions anywhere how to do this? So the LEDs will start working when the application is loaded? DANKE alot, TK, for your quick respons.

We manage to read the LCD now. For a second it reads "MIOS V1.9g © 2009 T.Klose" Then it turns to "READY." Still, the LEDS only flashes up on start-up, then nothing. Is 1.6 V enough on the LEDs? Is there a board schematics showing how much voltages should be expected across the board? We need to find out why the LED doesn't stay on. Thanx for all help.

Where is that pot located?

Status updated: My Dad finally finished the both boards and I shipped the C64 9 V PSU to him (we live in different countries). He has, with a multimeter, confirmed that the PSU is working. R40-R55 and T2-T9 are in position. When booting the box, all the LEDs are flashing up, then dies out (correct behavior?), BUT the LCD display shows no text - only background lights up, and stays on. When Dad is measuring the boards, there's 5V on most places, EXCEPT the LEDs, they have 1.6V. We need some advice on where to start looking for errors. (photage of boards and front coming up) We followed Hawkeye's tutorial pretty much exactly as was written (not that this is a guarantee in a DIY-project :) Thanks in advance. /Scifo

Thanks, Johey. Does this LCD have the right measurements and requirements? http://www.ebay.co.uk/itm/170440870233?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649

Where can I find instructions how to build the base board? Everything from SmashTV has arrived now.

I would like to thank NorthernLightX for his panels - they arrived safe and sound. Now I just hope that those soon-to-arrive flat 3mm LEDs will fit through those holes... And, Mouser just got a new batch of Alpha Encoders, so they are on the way as well. The project is rolling. OT: Today I bought a DSI Tempest. Can't wait for the MB6582 to be ready to make them best friends :)

About the LCD, I found this on Reichelt: http://www.reichelt.de/LCD-Modules-organic/EA-W204-XLG/3/index.html?;ACTION=3;LA=446;ARTICLE=113324;GROUPID=3012;artnr=EA+W204-XLG;SID=12ULFlq38AAAIAAE3FU3Q32cc7c628a6ea428f73250adc80754e9 It's pricey, but I really like the yellow on black, but this one is using OLED (not LED) technology - problems? Crystalfontz has one as well, but they have a 63 USD shipping cost to Europe, so I'm trying to find a EU seller that has this yellow-on-black display.

Thanx Rosch. So the 16mm shaft is not a must on these encoders?

Can't find any ALPS product on Voti's page, but I found these: http://www.voti.nl/shop/catalog.html?SW-ROT-02 Is it important that the shaft is 16 mm when I'm looking for these encoders?

Mouser have a 12 weeks Factory Lead Time on the 15 Alpha Rotary Encoders. Does anyone know other places to order them from (pref in EU), since these Alpha's are highly recommended? Thanx. /Scifo