glitched

You answered it perfectly, thanks. Now, you said that screws hold the sides together, but if the interlocking method was the only one I intended to use for one of the panels (for easy access; the others would be glued), should I add 0.1 or 0.2mm to that piece to allow for the laser burn-off? Do you think the fit would still be decent enough to hold with normal use? (Come to think of it, your idea to use screws to apply pressure for the top panel sounds pretty good...) I'm nearing completion; I'll PM you when I'm done, if you don't mind. Thanks so much for your help.

Hi, Wilba. A question about your design: Did you add the 3mm "teeth" at the end of your design phase or did you create your case, including the teeth? In other words, let's say you had a 150mm X 100mm x 70mm case design: Would you have to make the dimensions 153 x 103 x 73? Also, did you include the "bumps" on the teeth that Ponoko recommends for the interlocking method?

Thanks very much for this. I'll let you know how I do.

Hi, Wilba. About the Ponoko enclosure: Will you share the .svg file(s) with us? Your work is inspiring, and I'd like to try to adapt the case to another DIY project (the Shruti-1: http://mutable-instruments.net/). I have never worked in Inkscape before and your design would be extremely helpful in the learning process. Thanks. Regards, -d

Thanks. The knob was taken from a fully-operational Alesis Midiverb IV unit. One day, I was searching for a case to put my MBSID in, and the Midiverb was the unfortunate victim. I never used the racked case, but found that the knob fit the "D shaft" encoder, perfectly. I also toyed around with taking one of those giant Sony volume knobs and putting it on there, but it just looked silly. I have no idea where you could get a knob like the one on the Alesis (but there are tons of used MV's on ebay).

Let me just recommend that you purchase two SID boards (and parts) now. Trust me, it will save you some time later when you find you're addicted to the SID sound (and your new-found love of electronics). It's no fun looking at those extra chip(s) and wondering what they sound like!

Well, I got mine, soldered it, and started playing with it within a day. Very easy kit to put together, even with the SMT chip. Take a look at some pics and listen to a couple sound files: http://drop.io/wtpalog The official forum is here: http://www.narrat1ve.com/forum/ .

Great! Thanks, Thorsten. I'll check it out today. Regards.

Thorsten: I believe I found a "bug" or oversight in SID V2 RC30 involving the saving of ensemble data to the internal EEPROM. Simply, it is not possible to save changes to ensembles to the internal EEPROM when using the "SAV" function. When saving, it only gives one address: "E001". The message, "SAVE ENSEMBLE" appears as if the settings were written. Upon changing ensembles by hitting the "page up" button, the settings are lost. Some background: I have one bankstick, mouser pn# 579-24LC256-I/P. It is ID# 0 and patch saving works fine. In order to troubleshoot the problem, I checked over all my connections (they were correct) and uploaded both the latest MIOS firmware and SID applications using MIOS Studio 7 (beta 5), with the suggested settings (smart mode--MIDI IN and OUT connected). Also, I tried setting "DEFAULT_ENS_BS_CS" to "-1" in the .asm. None of these things solved the problem. On a whim, I decided to fire up the V2 Editor and see if I could write the data that way. Well, I changed some filter settings, saved, and uploaded the ensemble to memory. What do you know? The settings are retained! To me, this means there is probably something at fault with the mechanism that saves the ensemble to the internal memory, within the SID software. What do you think?

Great! I'm glad I'm starting to help the MB community, rather than wasting its time (as usual) :D . Another bankstick is on the list for the next Mouser shipment, for sure. By the way, I wish that there was a higher resolution version of the first pic on this page: http://www.ucapps.de/mbhp_bankstick.html Perhaps I'll make a version.

Ok, so, on a whim, I decided to fire up the V2 editor. I thought, maybe I could edit the ensemble and save it to memory. Perhaps, you know, that would sort of clear out the crud. Well, I changed some filter values, saved the patch, and uploaded it to memory. Boom--the settings have been saved! The settings are recalled when the machine is booted up. However, any changes I make to the ensemble on the SID itself (by pressing "SAV") are not retained. So, this seems to point to a bug in the mechanism that saves the ensemble to the internal EEPROM. Would you agree? Thanks.

This is a triumph! I'm curious: How much money do you think you spent on this project? (Not that it matters!)

The LCD actually looks closer to this, when properly adjusted (see attached). Actually, it looks a lot better than that in real life, but I can't get the right settings on my camera! 100_0818 (Large).JPG 100_0818 (Large).JPG

Thanks for the reply. Oh, and my problem is a little different than the original poster's: my settings aren't "messed up", they just aren't saved. The machine is always initialized with E002 (which is expected, as you have said). I have one bankstick, mouser pn# 579-24LC256-I/P. It is ID# 0 and patch saving works fine. I used MIOS Studio 7 (beta 5) to upload with the suggested settings (smart mode, device ID = 0, bankstick = 1). Also, this is a dual-SID setup: one core and two SID boards (a 6581 and 8580). The L/R communication works fine (that is, I can adjust the filter settings for either chip, independently). Do you think the problem is with the internal EEPROM? EDIT: This may have been a silly assumption, but you can SAVE to the ensemble on the internal EEPROM, right?

Rather than starting a new topic, I'll resurrect this one because I have the same exact problem. The only difference is that I'm using a 24LC256, rather than the 512. I have re-uploaded MIOS 1.9f and SID V2 RC30. I have checked and re-checked the connections and they are correct. Is there anything else I can try?