Keyboard Shortcuts
Likes
Search
Weird Xpander Behaviour
Hey there, My xpander - which I got last year - has started doing odd behaviour, and I just want to float it past you guys to see if it is what I hope it is; or if not, help to narrow it down. I was using my xpander yesterday, generating kick-ass sounds as normal. Then after about 20 minutes, suddenly the patch name display just filled up with asterisks. The sound engine still worked - and I was able to continue editing my sound. I then went to change the patch at which point the whole thing hung. No sound being produced and the buttons did nothing. I then rebooted it. The thing sprung to life as per normal but no sound was coming out. I then turned it off and unplugged from mains and left it a while. A couple of hours later I replugged it and turned it on. Booted up but still no sound. After a hunch, I went into the voices page only to find all the voices were set to off -- I turned them on and the xpander was working as it should. Again, I played with it for about 40 minutes (really addictive synth that it is), and just as I was about to turn it all off, the displays just went blank and the leds went on solidly. I power cycled it, and this time it didn't boot - just stuck with the leds on and no display. I turned it off and left it about a minute; rebooted and it displayed the message of Resetting the Memory (patches won't be effected). I pressed yes, only for it to again lock with all the LEDs on and no display. I again unplugged and left it a couple of hours. Coming back, it again showed the Reset the memory display, but this time it then booted. After that, I turned it off and called it a night. I'm hoping this is a battery issue -- it looks like it's using the original battery and surely that thing has to be dying by now. I opened it up and the caps all look fine. Checking the battery voltage (albeit in circuit), it's at 3.2v - which seems fine, though that is not under load. Reading online, it looks like when the battery dies, it can do all kinds of odd things to the synth; though checking the schematics I'm not totally sure of how this would affect the system once it's booted (and has been running successfully for half an hour or so). So does this sound like the likely cause? The only other thing I can think of (beyond the diodes around the battery and 5v line dying) is the psu giving spikes or drop outs -- which I'm really hoping it isn't. Mainly as the caps in those things can be pretty nasty. However, it is a Japanese unit and they seem to be known for having shitty PSUs. If it does end up being that (ugh), would just replacing the electrolytics be fine, or should I look at replacing the power supply entirely with a more modern design? Cheers, deano |
Mark Morton
I had a simliar-not identical but I got the "reset message " etc experience last year. I got sound but it was odd sound . It did turn out to be the battery. Hope that's the case with yours as it was an easy fix On Tue, Feb 9, 2016 at 5:46 AM, deanolium@... [xpantastic] <xpantastic@...> wrote:
|
Hopefully it is. Though looking at the schematics, I'm not totally sure why the battery failing would quite cause this.
I could see that with it failing, some of the RAM bits would become corrupted; and so I would expect either the patches to go crazy, or the system just not booting up properly. However, it is mostly booting up fine and only failing after about half an hour. In the last case, it failed whilst I was just playing some midi notes on a custom sound (ie, not saved to patch memory). So that sounds not totally like it would be the fault of the RAM bits becoming corrupted whilst the machine is off. My only guess looking at the schematics, are the failing of battery causing the system to pull a bit too much on the +5v power line and get an undercurrent situation which then affects all the digital chips. Or maybe the RAM bits which are being corrupted are the settings memory but they're corrupting in a way that only manifests itself in rare occasions? Regardless, I'll replace the battery when that arrives tomorrow since there's nothing to lose by doing so (particularly being a thirty year old battery...); but I will also try and check the following: 1 - The diodes in the battery to +5m line are working correctly (if the one by the battery is dead, then the +5v power line would be running through there - increasing the current usage which can't be good for it) 2 - Check the voltage level of the +5m line both with the system on and off 3 - Scope out the +5v line, and make sure it's relatively clean My main reluctance to do these checks is just paranoia of the system dying from whatever is up with it (a minor paranoia), and zapping myself on the incredibly exposed psu board that is right below the processor board. I'm pondering whether it might also be worthwhile to just replace the psu board with something more modern. However, since it requires a whole gamut of voltages (9v ac, +/-5v, +/-12v and that annoying +55v) it doesn't look like there's an off-the-shelf unit I can grab; but instead would have to get a basic switched mode power supply and then recreate the output transformer circuit from the xpander to get all those voltages. A lot of work, and really would need me to create a proper circuit board --- massively ambitious to the point of being impractical. Of course, if there's an easier way or someone else has done the footwork for this, that would be amazing. But enough rambling - let's hope the battery is the blame and the psu is still going strong. |
Mark Morton
Again? I cannot claim that our symptoms match up and mine was a Matrix 12 but the symptoms changes form bot up to boot up and all went away on a battery repalcement On Tue, Feb 9, 2016 at 8:46 AM, deanolium@... [xpantastic] <xpantastic@...> wrote:
|
Hey
toggle quoted message
Show quoted text
Odds are real good it's a battary issue, But being the machine is +20 yrs old the caps could easily need replacing. While you are replacing the battary it would be a good idea to re-seat all the ribbon cables, chips etc. If/When you can get it to boot up, Go to the service page and run the memory test diagnostics., on the outside chance you have RAM /ROM issues. Let me know what happens Best Luck Karl -------------------------------------------- On Tue, 2/9/16, deanolium@... [xpantastic] <xpantastic@...> wrote:
Subject: [xpantastic] Weird Xpander Behaviour To: xpantastic@... Date: Tuesday, February 9, 2016, 4:46 AM ? Hey there, My xpander - which I got last year - has started doing odd behaviour, and I just want to float it past you guys to see if it is what I hope it is; or if not, help to narrow it down. I was using my xpander yesterday, generating kick-ass sounds as normal. Then after about 20 minutes, suddenly the patch name display just filled up with asterisks. The sound engine still worked - and I was able to continue editing my sound. I then went to change the patch at which point the whole thing hung. No sound being produced and the buttons did nothing. I then rebooted it. The thing sprung to life as per normal but no sound was coming out. I then turned it off and unplugged from mains and left it a while. A couple of hours later I replugged it and turned it on. Booted up but still no sound. After a hunch, I went into the voices page only to find all the voices were set to off -- I turned them on and the xpander was working as it should. Again, I played with it for about 40 minutes (really addictive synth that it is), and just as I was about to turn it all off, the displays just went blank and the leds went on solidly. I power cycled it, and this time it didn't boot - just stuck with the leds on and no display. I turned it off and left it about a minute; rebooted and it displayed the message of Resetting the Memory (patches won't be effected). I pressed yes, only for it to again lock with all the LEDs on and no display. I again unplugged and left it a couple of hours. Coming back, it again showed the Reset the memory display, but this time it then booted. After that, I turned it off and called it a night. I'm hoping this is a battery issue -- it looks like it's using the original batter! y and surely that thing has to be dying by now. I opened it up and the caps all look fine. Checking the battery voltage (albeit in circuit), it's at 3.2v - which seems fine, though that is not under load. Reading online, it looks like when the battery dies, it can do all kinds of odd things to the synth; though checking the schematics I'm not totally sure of how this would affect the system once it's booted (and has been running successfully for half an hour or so). I've ordered a new battery and will check the voltages with the system on later to see what's happening there (I might as well scope it, so I can also check for ripple). So does this sound like the likely cause? The only other thing I can think of (beyond the diodes around the battery and 5v line dying) is the psu giving spikes or drop outs -- which I'm really hoping it isn't. Mainly as the caps in those things can be pretty nasty. However, it is a Japanese unit and they seem to be known for having shitty PSUs. If it does end up being that (ugh), would just replacing the electrolytics be fine, or should I look at replacing the power supply entirely with a more modern design? Cheers, deano #yiv6944683957 #yiv6944683957 -- #yiv6944683957ygrp-mkp { border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;} #yiv6944683957 #yiv6944683957ygrp-mkp hr { border:1px solid #d8d8d8;} #yiv6944683957 #yiv6944683957ygrp-mkp #yiv6944683957hd { color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;} #yiv6944683957 #yiv6944683957ygrp-mkp #yiv6944683957ads { margin-bottom:10px;} #yiv6944683957 #yiv6944683957ygrp-mkp .yiv6944683957ad { padding:0 0;} #yiv6944683957 #yiv6944683957ygrp-mkp .yiv6944683957ad p { margin:0;} #yiv6944683957 #yiv6944683957ygrp-mkp .yiv6944683957ad a { color:#0000ff;text-decoration:none;} #yiv6944683957 #yiv6944683957ygrp-sponsor #yiv6944683957ygrp-lc { font-family:Arial;} #yiv6944683957 #yiv6944683957ygrp-sponsor #yiv6944683957ygrp-lc #yiv6944683957hd { margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;} #yiv6944683957 #yiv6944683957ygrp-sponsor #yiv6944683957ygrp-lc .yiv6944683957ad { margin-bottom:10px;padding:0 0;} #yiv6944683957 #yiv6944683957actions { font-family:Verdana;font-size:11px;padding:10px 0;} #yiv6944683957 #yiv6944683957activity { background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;} #yiv6944683957 #yiv6944683957activity span { font-weight:700;} #yiv6944683957 #yiv6944683957activity span:first-child { text-transform:uppercase;} #yiv6944683957 #yiv6944683957activity span a { color:#5085b6;text-decoration:none;} #yiv6944683957 #yiv6944683957activity span span { color:#ff7900;} #yiv6944683957 #yiv6944683957activity span .yiv6944683957underline { text-decoration:underline;} #yiv6944683957 .yiv6944683957attach { clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;} #yiv6944683957 .yiv6944683957attach div a { text-decoration:none;} #yiv6944683957 .yiv6944683957attach img { border:none;padding-right:5px;} #yiv6944683957 .yiv6944683957attach label { display:block;margin-bottom:5px;} #yiv6944683957 .yiv6944683957attach label a { text-decoration:none;} #yiv6944683957 blockquote { margin:0 0 0 4px;} #yiv6944683957 .yiv6944683957bold { font-family:Arial;font-size:13px;font-weight:700;} #yiv6944683957 .yiv6944683957bold a { text-decoration:none;} #yiv6944683957 dd.yiv6944683957last p a { font-family:Verdana;font-weight:700;} #yiv6944683957 dd.yiv6944683957last p span { margin-right:10px;font-family:Verdana;font-weight:700;} #yiv6944683957 dd.yiv6944683957last p span.yiv6944683957yshortcuts { margin-right:0;} #yiv6944683957 div.yiv6944683957attach-table div div a { text-decoration:none;} #yiv6944683957 div.yiv6944683957attach-table { width:400px;} #yiv6944683957 div.yiv6944683957file-title a, #yiv6944683957 div.yiv6944683957file-title a:active, #yiv6944683957 div.yiv6944683957file-title a:hover, #yiv6944683957 div.yiv6944683957file-title a:visited { text-decoration:none;} #yiv6944683957 div.yiv6944683957photo-title a, #yiv6944683957 div.yiv6944683957photo-title a:active, #yiv6944683957 div.yiv6944683957photo-title a:hover, #yiv6944683957 div.yiv6944683957photo-title a:visited { text-decoration:none;} #yiv6944683957 div#yiv6944683957ygrp-mlmsg #yiv6944683957ygrp-msg p a span.yiv6944683957yshortcuts { font-family:Verdana;font-size:10px;font-weight:normal;} #yiv6944683957 .yiv6944683957green { color:#628c2a;} #yiv6944683957 .yiv6944683957MsoNormal { margin:0 0 0 0;} #yiv6944683957 o { font-size:0;} #yiv6944683957 #yiv6944683957photos div { float:left;width:72px;} #yiv6944683957 #yiv6944683957photos div div { border:1px solid #666666;height:62px;overflow:hidden;width:62px;} #yiv6944683957 #yiv6944683957photos div label { color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;} #yiv6944683957 #yiv6944683957reco-category { font-size:77%;} #yiv6944683957 #yiv6944683957reco-desc { font-size:77%;} #yiv6944683957 .yiv6944683957replbq { margin:4px;} #yiv6944683957 #yiv6944683957ygrp-actbar div a:first-child { margin-right:2px;padding-right:5px;} #yiv6944683957 #yiv6944683957ygrp-mlmsg { font-size:13px;font-family:Arial, helvetica, clean, sans-serif;} #yiv6944683957 #yiv6944683957ygrp-mlmsg table { font-size:inherit;font:100%;} #yiv6944683957 #yiv6944683957ygrp-mlmsg select, #yiv6944683957 input, #yiv6944683957 textarea { font:99% Arial, Helvetica, clean, sans-serif;} #yiv6944683957 #yiv6944683957ygrp-mlmsg pre, #yiv6944683957 code { font:115% monospace;} #yiv6944683957 #yiv6944683957ygrp-mlmsg * { line-height:1.22em;} #yiv6944683957 #yiv6944683957ygrp-mlmsg #yiv6944683957logo { padding-bottom:10px;} #yiv6944683957 #yiv6944683957ygrp-msg p a { font-family:Verdana;} #yiv6944683957 #yiv6944683957ygrp-msg p#yiv6944683957attach-count span { color:#1E66AE;font-weight:700;} #yiv6944683957 #yiv6944683957ygrp-reco #yiv6944683957reco-head { color:#ff7900;font-weight:700;} #yiv6944683957 #yiv6944683957ygrp-reco { margin-bottom:20px;padding:0px;} #yiv6944683957 #yiv6944683957ygrp-sponsor #yiv6944683957ov li a { font-size:130%;text-decoration:none;} #yiv6944683957 #yiv6944683957ygrp-sponsor #yiv6944683957ov li { font-size:77%;list-style-type:square;padding:6px 0;} #yiv6944683957 #yiv6944683957ygrp-sponsor #yiv6944683957ov ul { margin:0;padding:0 0 0 8px;} #yiv6944683957 #yiv6944683957ygrp-text { font-family:Georgia;} #yiv6944683957 #yiv6944683957ygrp-text p { margin:0 0 1em 0;} #yiv6944683957 #yiv6944683957ygrp-text tt { font-size:120%;} #yiv6944683957 #yiv6944683957ygrp-vital ul li:last-child { border-right:none !important; } #yiv6944683957 |
The @@@@@@@@ or %%%%%%% in the display is usually the PSU needing a
refurbish (caps), or one of the ribbon cables needing a re-seat, and is
common across the range of 6/12/Xpandr. Same for the all edit lights on and no display.
2 other things to keep in mind are RFi - such as 3g/LTE mobile phones and WiFi can cause unstability, and MIDI overflow. The 12 and X especially have a low tolerance for MIDI problems, and if You are on the end of a chain of 2 or more IN-THRU, You need to expect lockups, especially if there is some midi in the chain that is generated using a PIC implementation. Modern MIDI devices really can have problems with early complex MIDI like that in the 12/X. Lastly, check what socks and shoes You are wearing. the 12/X and 6 have poor tolerance for electro-static discharges. so even a small amount of static buildup from your feet rubbing on the carpet or furniture can cause strange behaviour that can linger even AFTER a power cycle. None of these things will cause lasting damage, but if You see the @@@@@@@, lights all on or PROCESSOR 1 FAIL alot, you need to isolate the device and see if that helps. |