Rhodes Chroma Polaris group photo

Yahoo Groups archive

Rhodes Chroma Polaris

Archive for chromapolaris.

Index last updated: 2026-03-30 01:08 UTC

Thread

Polaris broken.... help!

Polaris broken.... help!

2018-06-02 by lou@...

I've owned my Chroma Polaris for many years and repaired it many times. This time its different... When I start it up many LEDs light upon the front panel and that's it. Same patter of LEDs every time; no response to playing the keys or pressing any buttons. Not much of a surprise once I get down and dirty inside. The CPU is running, I've scoped address and data lines on the RAM and ROM chips. There is no signal at all on PCS3. I've checked this line for  continuity from the CPU IC to the various spots where it is used and the connection is good This line enables the transfer of data to/from the front panel. So that explains why the FP is not responding. Always at logic HI. This is a processor line.so I figured maybe the 80186 has died or become damaged. I tried a new CPU chip... same thing.

So now I'm like well what could it be?

I have three revs of EPROM firmware and tried all three... same thing. I have a nice O'scope and DVM and some good tools and lots of parts from that era. I have the owner's and service manuals. As I said I've repaired this guy before but this time around I'm not sure what the trouble is. Any Ideas  on what is going on or what I should check next?


Lou

Re: [chromapolaris] Polaris broken.... help!

2018-06-02 by Bob Grieb

Sounds like the CPU is not executing the code properly, or is getting
stuck somewhere waiting for something to happen. I am not familiar with the
structure of the code, but sometimes panel scanning is initiated by an interrupt
to the CPU. Maybe check any external interrupt signals to see if they are pulsing?

Sometimes you can check address decodes and get a feel for whether the CPU
is stuck polling one particular device, waiting for something to happen.

Also, if you have some spare RAM chips, try temporarily replacing them to see
if that changes anything. A bad RAM will prevent proper CPU execution.
Since the Polaris can use two different sizes of RAM chips, you can infer
the minimum amount of RAM needed for it to operate, and only install that much,
then try different chips.

Of course Paul D is the expert on all things Polaris...

Bob

Re: [chromapolaris] Polaris broken.... help!

2018-06-02 by Gregory Cox

Now, I didn't see any mention about adjusting your DC OK threshold as outlined in the service manual.  This totally sounds like the problem!

Greg


Sent from my iPhone

On Jun 2, 2018, at 10:13 AM, Bob Grieb bobgrieb@... [chromapolaris] <chromapolaris@yahoogroups.com> wrote:

 

Sounds like the CPU is not executing the code properly, or is getting
stuck somewhere waiting for something to happen. I am not familiar with the
structure of the code, but sometimes panel scanning is initiated by an interrupt
to the CPU. Maybe check any external interrupt signals to see if they are pulsing?

Sometimes you can check address decodes and get a feel for whether the CPU
is stuck polling one particular device, waiting for something to happen.

Also, if you have some spare RAM chips, try temporarily replacing them to see
if that changes anything. A bad RAM will prevent proper CPU execution.
Since the Polaris can use two different sizes of RAM chips, you can infer
the minimum amount of RAM needed for it to operate, and only install that much,
then try different chips.

Of course Paul D is the expert on all things Polaris...

Bob

RE: [chromapolaris] Polaris broken.... help!

2018-06-02 by Lou Champagne

Thanks for the suggestion Greg. OK I’m going to calibrate that again just to make sure.

Should I do this under load or with the PSU output disconnected from the main board?

Lou

 

From: chromapolaris@yahoogroups.com [mailto:chromapolaris@yahoogroups.com]
Sent: June-02-18 10:36 AM
To: chromapolaris@yahoogroups.com
Subject: Re: [chromapolaris] Polaris broken.... help!

 

 

Now, I didn't see any mention about adjusting your DC OK threshold as outlined in the service manual.  This totally sounds like the problem!

 

Greg



Sent from my iPhone


On Jun 2, 2018, at 10:13 AM, Bob Grieb bobgrieb@... [chromapolaris] <chromapolaris@yahoogroups.com> wrote:

 

Sounds like the CPU is not executing the code properly, or is getting
stuck somewhere waiting for something to happen. I am not familiar with the
structure of the code, but sometimes panel scanning is initiated by an interrupt
to the CPU. Maybe check any external interrupt signals to see if they are pulsing?

Sometimes you can check address decodes and get a feel for whether the CPU
is stuck polling one particular device, waiting for something to happen.

Also, if you have some spare RAM chips, try temporarily replacing them to see
if that changes anything. A bad RAM will prevent proper CPU execution.
Since the Polaris can use two different sizes of RAM chips, you can infer
the minimum amount of RAM needed for it to operate, and only install that much,
then try different chips.

Of course Paul D is the expert on all things Polaris...

Bob

Re: [chromapolaris] Polaris broken.... help!

2018-06-02 by Gregory Cox

On load... you have to watch the led... once set, cycling the power should bring it back from this unresponsive condition.

Sent from my iPhone

On Jun 2, 2018, at 11:18 AM, 'Lou Champagne' lou@... [chromapolaris] <chromapolaris@yahoogroups.com> wrote:

 

Thanks for the suggestion Greg. OK I’m going to calibrate that again just to make sure.

Should I do this under load or with the PSU output disconnected from the main board?

Lou

 

From: chromapolaris@yahoogroups.com [mailto:chromapolaris@yahoogroups.com]
Sent: June-02-18 10:36 AM
To: chromapolaris@yahoogroups.com
Subject: Re: [chromapolaris] Polaris broken.... help!

 

 

Now, I didn't see any mention about adjusting your DC OK threshold as outlined in the service manual.  This totally sounds like the problem!

 

Greg



Sent from my iPhone


On Jun 2, 2018, at 10:13 AM, Bob Grieb bobgrieb@... [chromapolaris] <chromapolaris@yahoogroups.com> wrote:

 

Sounds like the CPU is not executing the code properly, or is getting
stuck somewhere waiting for something to happen. I am not familiar with the
structure of the code, but sometimes panel scanning is initiated by an interrupt
to the CPU. Maybe check any external interrupt signals to see if they are pulsing?

Sometimes you can check address decodes and get a feel for whether the CPU
is stuck polling one particular device, waiting for something to happen.

Also, if you have some spare RAM chips, try temporarily replacing them to see
if that changes anything. A bad RAM will prevent proper CPU execution.
Since the Polaris can use two different sizes of RAM chips, you can infer
the minimum amount of RAM needed for it to operate, and only install that much,
then try different chips.

Of course Paul D is the expert on all things Polaris...

Bob

RE: [chromapolaris] Polaris broken.... help!

2018-06-02 by Lou Champagne

Ok Bob;

Thanks for these ideas. I’ve checked some of these things but I’ll get set-up and give your suggestions a less hap-hazard try.

Two kinds of 6264 RAM chips are installed… but it used to work!

I think I have some 6116 around ….30 nS?

 

Best Regards

Lou Champagne

www.pterodactylrecords.com

 

 

 

From: chromapolaris@yahoogroups.com [mailto:chromapolaris@yahoogroups.com]
Sent: June-02-18 10:13 AM
To: chromapolaris@yahoogroups.com
Subject: Re: [chromapolaris] Polaris broken.... help!

 

 

Sounds like the CPU is not executing the code properly, or is getting
stuck somewhere waiting for something to happen. I am not familiar with the
structure of the code, but sometimes panel scanning is initiated by an interrupt
to the CPU. Maybe check any external interrupt signals to see if they are pulsing?

Sometimes you can check address decodes and get a feel for whether the CPU
is stuck polling one particular device, waiting for something to happen.

Also, if you have some spare RAM chips, try temporarily replacing them to see
if that changes anything. A bad RAM will prevent proper CPU execution.
Since the Polaris can use two different sizes of RAM chips, you can infer
the minimum amount of RAM needed for it to operate, and only install that much,
then try different chips.

Of course Paul D is the expert on all things Polaris...

Bob

RE: [chromapolaris] Polaris broken.... help!

2018-06-02 by Bob Grieb

I seriously doubt that you have 6116's with 30 nSec access times.
More likely 300 nSec.

So you are thinking that just because something used to work, that
it must be OK? If that were true then nothing would ever fail, right?

Anyway, good luck. I am sure you will sort it out. Maybe it is just the reset
circuit as has been suggested.

Bob

RE: [chromapolaris] Polaris broken.... help!

2018-06-05 by Lou Champagne

Hi Greg et al,

 

Following the procedure it is interesting that the power supply does not allow me to even get down to 4.8V. The closest I can get it 4.88V. So I set it to light at that point and reset the regulation of the supply back to 5.0V measured where the wire enters the main board. The zero reference I’m using the the fast-on tab ground point near the front panel connector.

 

Same thing… bunch of LEDs come on in the same pattern. No panel response or keyboard response. Signals on RAM and ROM address and data lines.

 

Sometimes the pattern of these signals looks too regular to be code executing… not sure about this. Looping?

 

 

With regards to the 6116s… I see so the -3 must mean 300… kinda makes sense. Anyway it appears I only have 6 ICs so that idea is moot.

 

I think something may be occupying the CPUs attention.

PREQ is patched to INT1 on the jumpers near the CPU - should that signal be always HI?

 

Lou

 

 

From: chromapolaris@yahoogroups.com [mailto:chromapolaris@yahoogroups.com]
Sent: June-02-18 11:23 AM
To: chromapolaris@yahoogroups.com
Subject: Re: [chromapolaris] Polaris broken.... help!

 

 

On load... you have to watch the led... once set, cycling the power should bring it back from this unresponsive condition.

Sent from my iPhone


On Jun 2, 2018, at 11:18 AM, 'Lou Champagne' lou@... [chromapolaris] <chromapolaris@yahoogroups.com> wrote:

 

Thanks for the suggestion Greg. OK I’m going to calibrate that again just to make sure.

Should I do this under load or with the PSU output disconnected from the main board?

Lou

 

From: chromapolaris@yahoogroups.com [mailto:chromapolaris@yahoogroups.com]
Sent: June-02-18 10:36 AM
To: chromapolaris@yahoogroups.com
Subject: Re: [chromapolaris] Polaris broken.... help!

 

 

Now, I didn't see any mention about adjusting your DC OK threshold as outlined in the service manual.  This totally sounds like the problem!

 

Greg



Sent from my iPhone


On Jun 2, 2018, at 10:13 AM, Bob Grieb bobgrieb@... [chromapolaris] <chromapolaris@yahoogroups.com> wrote:

 

Sounds like the CPU is not executing the code properly, or is getting
stuck somewhere waiting for something to happen. I am not familiar with the
structure of the code, but sometimes panel scanning is initiated by an interrupt
to the CPU. Maybe check any external interrupt signals to see if they are pulsing?

Sometimes you can check address decodes and get a feel for whether the CPU
is stuck polling one particular device, waiting for something to happen.

Also, if you have some spare RAM chips, try temporarily replacing them to see
if that changes anything. A bad RAM will prevent proper CPU execution.
Since the Polaris can use two different sizes of RAM chips, you can infer
the minimum amount of RAM needed for it to operate, and only install that much,
then try different chips.

Of course Paul D is the expert on all things Polaris...

Bob

RE: [chromapolaris] Polaris broken.... help!

2018-06-05 by Bob Grieb

Greg,

Are the installed RAMs 6264 types? If so, just two of them installed is a valid configuration,
so you could remove all but two and swap those out to see if you have a bad RAM chip. You can see the
valid configurations and jumper setting in the service manual.

The service manual mentions that U84 and some other gates are not used in the Polaris, and this circuitry
was for something that Fender was developing. I think this is the circuit that was driving PREQ, so
probably it's OK to be sitting high.

Bob

RE: [chromapolaris] Polaris broken.... help!

2018-06-06 by Lou Champagne

I’m down to two 6264 now with nothing to report after having swapped them around a bit to make sure.

 

Lou

>>

Are the installed RAMs 6264 types? If so, just two of them installed is a valid configuration,
so you could remove all but two and swap those out to see if you have a bad RAM chip. You can see the
valid configurations and jumper setting in the service manual.

The service manual mentions that U84 and some other gates are not used in the Polaris, and this circuitry
was for something that Fender was developing. I think this is the circuit that was driving PREQ, so
probably it's OK to be sitting high.

Bob

RE: [chromapolaris] Polaris broken.... help!

2018-06-06 by Bob Grieb

That's one thing you can rule out. So it's something.

If the CPU is stuck somewhere, there should be one particular address decode/chip select
that's getting hammered.

I'm sure you scoped the reset to make sure it's not glitching into the active state, right?

Sounds like a tough one...

Re: [chromapolaris] Polaris broken.... help!

2018-06-06 by Gregory Cox

By the way Bob, Lou’s the guy with the problem, not I  ;)   Anyway Lou, before you set off on a complicated journey, I would honestly re-examine the DC OK threshold in detail.  My main argument of why-- sometimes the power supply DC OK LED comes on when adjusted but may still need a little more juice in some situations to work correctly.  Without the correct DC OK setting none of the digital side will work and the polaris will be unresponsive with LEDs lit just as you originally described.  After making a small incremental adjustment reset the power and see if it helped, then repeat again to see if any higher adjustment works.

A while ago my polaris appeared to be screwed and unresponsive but it was a finicky trimmer on the power supply.  Make sure it’s sprayed with a contact cleaner or something and readjust as described in the service manual.

Greg





On Jun 5, 2018, at 8:13 PM, 'Lou Champagne' lou@... [chromapolaris] <chromapolaris@yahoogroups.com> wrote:


I’m down to two 6264 now with nothing to report after having swapped them around a bit to make sure.

 

Lou

>>

Are the installed RAMs 6264 types? If so, just two of them installed is a valid configuration,
so you could remove all but two and swap those out to see if you have a bad RAM chip. You can see the 
valid configurations and jumper setting in the service manual.

The service manual mentions that U84 and some other gates are not used in the Polaris, and this circuitry
was for something that Fender was developing. I think this is the circuit that was driving PREQ, so 
probably it's OK to be sitting high.

Bob



Re: [chromapolaris] Polaris broken.... help!

2018-06-06 by Tracy Barber

That applies to me as well. Thanks.

Tracy


--------------------------------------------
On Wed, 6/6/18, Gregory Cox adhmzaiusz@... [chromapolaris] <chromapolaris@yahoogroups.com> wrote:

Subject: Re: [chromapolaris] Polaris broken.... help!
To: "chromapolaris@yahoogroups.com" <chromapolaris@yahoogroups.com>
Date: Wednesday, June 6, 2018, 11:52 AM


 












By the way Bob, Lou’s the guy with the problem, not I  ;)
  Anyway Lou, before you set off on a complicated journey,
I would honestly re-examine the DC OK threshold in detail.
 My main argument of why-- sometimes the power supply DC OK
LED comes on when adjusted
but may still need a little more juice in some situations
to work correctly.  Without the correct DC OK setting none
of the digital side will work and the polaris will be
unresponsive with LEDs lit just as you originally described.
 After making a small incremental
adjustment reset the power and see if it helped, then
repeat again to see if any higher adjustment works.



A while ago my polaris appeared to be screwed and
unresponsive but it was a finicky trimmer on the power
supply.  Make sure it’s sprayed with a contact cleaner or
something and readjust as described in the service
manual.



Greg
















On Jun 5, 2018, at 8:13 PM, 'Lou Champagne'
lou@... [chromapolaris] <chromapolaris@yahoogroups.com>
wrote:











I’m down to two 6264 now with nothing to report
after having swapped them around a bit to make
sure.

 
Lou



>>



Are the installed RAMs 6264 types? If so, just two of them
installed is a valid configuration,

so you could remove all but two and swap those out to see if
you have a bad RAM chip. You can see the 

valid configurations and jumper setting in the service
manual.



The service manual mentions that U84 and some other gates
are not used in the Polaris, and this circuitry

was for something that Fender was developing. I think this
is the circuit that was driving PREQ, so 

probably it's OK to be sitting high.



Bob































#yiv5042080038 #yiv5042080038 --
#yiv5042080038ygrp-mkp {
border:1px solid #d8d8d8;font-family:Arial;margin:10px
0;padding:0 10px;}

#yiv5042080038 #yiv5042080038ygrp-mkp hr {
border:1px solid #d8d8d8;}

#yiv5042080038 #yiv5042080038ygrp-mkp #yiv5042080038hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px
0;}

#yiv5042080038 #yiv5042080038ygrp-mkp #yiv5042080038ads {
margin-bottom:10px;}

#yiv5042080038 #yiv5042080038ygrp-mkp .yiv5042080038ad {
padding:0 0;}

#yiv5042080038 #yiv5042080038ygrp-mkp .yiv5042080038ad p {
margin:0;}

#yiv5042080038 #yiv5042080038ygrp-mkp .yiv5042080038ad a {
color:#0000ff;text-decoration:none;}
#yiv5042080038 #yiv5042080038ygrp-sponsor
#yiv5042080038ygrp-lc {
font-family:Arial;}

#yiv5042080038 #yiv5042080038ygrp-sponsor
#yiv5042080038ygrp-lc #yiv5042080038hd {
margin:10px
0px;font-weight:700;font-size:78%;line-height:122%;}

#yiv5042080038 #yiv5042080038ygrp-sponsor
#yiv5042080038ygrp-lc .yiv5042080038ad {
margin-bottom:10px;padding:0 0;}

#yiv5042080038 #yiv5042080038actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#yiv5042080038 #yiv5042080038activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#yiv5042080038 #yiv5042080038activity span {
font-weight:700;}

#yiv5042080038 #yiv5042080038activity span:first-child {
text-transform:uppercase;}

#yiv5042080038 #yiv5042080038activity span a {
color:#5085b6;text-decoration:none;}

#yiv5042080038 #yiv5042080038activity span span {
color:#ff7900;}

#yiv5042080038 #yiv5042080038activity span
.yiv5042080038underline {
text-decoration:underline;}

#yiv5042080038 .yiv5042080038attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px
0;width:400px;}

#yiv5042080038 .yiv5042080038attach div a {
text-decoration:none;}

#yiv5042080038 .yiv5042080038attach img {
border:none;padding-right:5px;}

#yiv5042080038 .yiv5042080038attach label {
display:block;margin-bottom:5px;}

#yiv5042080038 .yiv5042080038attach label a {
text-decoration:none;}

#yiv5042080038 blockquote {
margin:0 0 0 4px;}

#yiv5042080038 .yiv5042080038bold {
font-family:Arial;font-size:13px;font-weight:700;}

#yiv5042080038 .yiv5042080038bold a {
text-decoration:none;}

#yiv5042080038 dd.yiv5042080038last p a {
font-family:Verdana;font-weight:700;}

#yiv5042080038 dd.yiv5042080038last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#yiv5042080038 dd.yiv5042080038last p
span.yiv5042080038yshortcuts {
margin-right:0;}

#yiv5042080038 div.yiv5042080038attach-table div div a {
text-decoration:none;}

#yiv5042080038 div.yiv5042080038attach-table {
width:400px;}

#yiv5042080038 div.yiv5042080038file-title a, #yiv5042080038
div.yiv5042080038file-title a:active, #yiv5042080038
div.yiv5042080038file-title a:hover, #yiv5042080038
div.yiv5042080038file-title a:visited {
text-decoration:none;}

#yiv5042080038 div.yiv5042080038photo-title a,
#yiv5042080038 div.yiv5042080038photo-title a:active,
#yiv5042080038 div.yiv5042080038photo-title a:hover,
#yiv5042080038 div.yiv5042080038photo-title a:visited {
text-decoration:none;}

#yiv5042080038 div#yiv5042080038ygrp-mlmsg
#yiv5042080038ygrp-msg p a span.yiv5042080038yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#yiv5042080038 .yiv5042080038green {
color:#628c2a;}

#yiv5042080038 .yiv5042080038MsoNormal {
margin:0 0 0 0;}

#yiv5042080038 o {
font-size:0;}

#yiv5042080038 #yiv5042080038photos div {
float:left;width:72px;}

#yiv5042080038 #yiv5042080038photos div div {
border:1px solid
#666666;min-height:62px;overflow:hidden;width:62px;}

#yiv5042080038 #yiv5042080038photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#yiv5042080038 #yiv5042080038reco-category {
font-size:77%;}

#yiv5042080038 #yiv5042080038reco-desc {
font-size:77%;}

#yiv5042080038 .yiv5042080038replbq {
margin:4px;}

#yiv5042080038 #yiv5042080038ygrp-actbar div a:first-child {
margin-right:2px;padding-right:5px;}

#yiv5042080038 #yiv5042080038ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean,
sans-serif;}

#yiv5042080038 #yiv5042080038ygrp-mlmsg table {
font-size:inherit;font:100%;}

#yiv5042080038 #yiv5042080038ygrp-mlmsg select,
#yiv5042080038 input, #yiv5042080038 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#yiv5042080038 #yiv5042080038ygrp-mlmsg pre, #yiv5042080038
code {
font:115% monospace;}

#yiv5042080038 #yiv5042080038ygrp-mlmsg * {
line-height:1.22em;}

#yiv5042080038 #yiv5042080038ygrp-mlmsg #yiv5042080038logo {
padding-bottom:10px;}


#yiv5042080038 #yiv5042080038ygrp-msg p a {
font-family:Verdana;}

#yiv5042080038 #yiv5042080038ygrp-msg
p#yiv5042080038attach-count span {
color:#1E66AE;font-weight:700;}

#yiv5042080038 #yiv5042080038ygrp-reco
#yiv5042080038reco-head {
color:#ff7900;font-weight:700;}

#yiv5042080038 #yiv5042080038ygrp-reco {
margin-bottom:20px;padding:0px;}

#yiv5042080038 #yiv5042080038ygrp-sponsor #yiv5042080038ov
li a {
font-size:130%;text-decoration:none;}

#yiv5042080038 #yiv5042080038ygrp-sponsor #yiv5042080038ov
li {
font-size:77%;list-style-type:square;padding:6px 0;}

#yiv5042080038 #yiv5042080038ygrp-sponsor #yiv5042080038ov
ul {
margin:0;padding:0 0 0 8px;}

#yiv5042080038 #yiv5042080038ygrp-text {
font-family:Georgia;}

#yiv5042080038 #yiv5042080038ygrp-text p {
margin:0 0 1em 0;}

#yiv5042080038 #yiv5042080038ygrp-text tt {
font-size:120%;}

#yiv5042080038 #yiv5042080038ygrp-vital ul li:last-child {
border-right:none !important;
}
#yiv5042080038