Filch

Wow, all this time and didn't realize it went counterclockwise. Thanks for everyone's help :)

Thanks for the response. Just so I don't make any poor assumptions, here's a pic of what I think you are suggesting for JD1. Did I screwup the pin count here? Here's where a slight confusion for me happens when it comes to the Pin number. I was under the impression pin 1 on an IC was the left side pin with the dot/notch, continued down the side, then started on the right side and on down. I was thinking the pin I've connected to in the pic for U16 was pin 14?? Or I'm just completely wrong about pin order or where I think this wire should be connecting and it is actually pin 11, 3 up from the one in my picture.

I ended up lifting 2 pads off of a Rev2 MB-6582 baseboard when desoldering some items. I was hoping someone may help me identify if and where I'll need to attach some flying wires to fix the flub I made. On the topside of the board, I lifted pad for R43 near U22. - if I'm reading the board layout properly, I should just be able to bridge solder on the bottom of the board from R43 to the socket pin? On the bottom of the board, I lifted pad D0 for JD1 - this one looks a little more complex and not exactly sure what the best action for repair is. Could I run a flying wire from D0 to the small hole joining the last two pins of resistor network? Convenient link to the baseboard PCB layout : http://www.mb6582.org/plans/MB-6582_Base_PCB_R2_Color.pdf

I'm guessing the later, If I turned P1 most of the way up, the box would reboot.

I turned P1 all the way down and I haven't noticed any more of the flickering. The screen is still plenty bright at this setting. I'll keep playing around with the sammichSID and see if it flickers again, but for now it appears to have disappeared. Thanks

I've just completed and tested my sammichSID kit and for the first time ever, I completed a kit with no mistakes, no bugs, and no errors. I want to thank Wilba for a most excellent piece of kit and fantastic instructional writing. I think it's a testament to how well this was designed and want to thank you again. And now for one one, minor issue..... ;) MY LCD gets occasional flicker and dimming. It's slight, but noticeable. Is this normal or is there something I should start looking at as the cause? Thanks!

I will be trying this soon. I love M4L and I have several HW synths that I want to build editors for. I plan to use yours here as a guide in helping me. I haven't built a thing in max yet. I want to be able to do full sysex as well since many of my other synths will do sysex only. If you know of a workaround to work sysex control into Live, please let me pick your brain.

Ha. I guess I probably should have realized switching/switchmode were one in the same. Should've figured there would be something wrong with this. :-p Hopefully I can redeem myself with this : It's the last model on this pdf : Linear PSU Model : ST-1212-R0.5A And here it is on Amazon for $11.95 US after shipping

Wallwart PSU from Amazon US I found this pretty cheap wallwart on Amazon.com and looks like to be a good candidate and another source for a PSU. I intend to use this with my 6582 sammich. * Fully Regulated 100V-240V can be used world wide * 12V DC 500MA Switching Power Supply * 6 Ft Long cord with center positive 2.1 MM jack

If you haven't already, double check that your LCD board isn't shorting on the CS. This has been the cause of many weird and wild problems in the past.

It will work, but only using CC's. Ableton Live filters all sysex, even though Max has no trouble with Sysex, it's hosted in Live, therefore it will never makes it into Live, recorded or otherwise. There is some mild rumors about sysex support in the future, but Ableton is purely focused on bug squashing right now and will not be adding new features anytime soon.

I actually noticed your post for that when I searched for LCD Insulation. I think I'll do that as well as taping up the PCB (which I've already done). My screws are a little small though, so I may stack 2 washers instead for a gap. My problem now is that with all this futzing around troubleshooting the issue, I've broke a few wire leads on some of the ribbon cables between the CS and the mainboard.... *sigh*

I was using the LCD to determine if I was getting the error still or not. The CS was not responding normally. Most of it was, other parts were acting strange. When I did your test, I was getting the same errors on the LCD. So, I detached the LCD from the CS and the problems went away! :D Looks like I've got a short somewhere. I already had the pads covered in electrical tape. I'll just wrap the rest of the exposed LCD PCB in electrical tape. Thanks Wilba!!! I'm going to have to remove the front panel to get the LCD attached again. I was trying to avoid taking these apart as I fear I'm going to squish some LEDs when putting the front panel back on. My panel fitting is a bit snug. I have to nudge a button here and there to get it to slide on properly.

Spoke briefly to Wilba about this problem in the chat room. I was suspect of my CS causing the problem since the mainboard was working okay before I wired up the CS. He suggested removing the Shift Registers and see if the problem goes away. I removed them all and my error did disappear. I replaced them one by one to see where the problem began. I started with the 165's and all was well until I placed in the 5th 165 into U20. I thought I may have a short or bald solder point there. I reflowed all the points and came back with the same problem. To make sure the shift register wasn't bad, I removed it and put the one from U19 into U20 and I had no errors. I thought I may have found a bad IC, but to be thorough, I put that suspect IC into U19, removed the IC I had in U20, and no errors again. The only time I get this error is when all 5 165 shift registers are in place. The problem goes away when I remove any one of the 165's, it doesn't matter which one. Removing one or all of the 595's does not change anything.

I reupped the SID OS to all 4 cores again, and now I'm back to SID4 Not Available (No MBNet Response)