Elecraft

KAT100 - Reluctant to come on, K2 often displays "not inst"

Classic

List

Threaded

15 messages Options

Bill Coleman-2

KAT100 - Reluctant to come on, K2 often displays "not inst"

OK, I have a K2/100 (#2548) connected to a KAT100.

As of late, the KAT100 has been reluctant to turn on. I turn on the K2, and it comes up right away, but the LEDs of the KAT100 often stay off for 20-30 seconds, then come on.

When the KAT100 finally turns on, it often isn’t tracking lo-hi power, as I can rotate the power knob freely from <10 watts to >11 watts, and the KAT100 will stay stuck at a power level, usually low power.

Also, if I try to change antennas, or tune, I’ll get a “not inst” message.

This situation persists for a while. If I let the rig warm up for about 15-20 minutes, I can eventually get the K2 to recognize the KAT100. I may have to cycle the power a half dozen times.

I’ve verified with a scope that the KAT100 is getting the 12CTRL power immediately from the K2, and the internal power on the 5V regulator comes up immediately. It just seems to take it’s sweet time waking up.

I think the fundamental problem may be that the KAT100 isn’t responding to AUXBUS messages at the right point in the power-up sequence, so the K2 assume it’s not installed.

Would appreciate any suggestions on how to troubleshoot this.

Bill Coleman, AA4LR, PP-ASEL Mail: [hidden email]
Web: http://boringhamradiopart.blogspot.com
Quote: "Not within a thousand years will man ever fly!"
-- Wilbur Wright, 1901

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Bill Coleman-2

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

Yes, I have a cable that has the PowerPole connections to the K2/100, and a separate coaxial jack for the KAT100.

I switch the power supply on, which means the KAT100 has power, then switch the K2/100 on, which powers up the combo.

So, yeah, I have power applied to the KAT100 before the K2.

> On Aug 5, 2018, at 4:39 PM, Jerry Ford <[hidden email]> wrote:
>
> Hi Bill: The K2 / KAT100 has a strange start up procedure you have to follow or the KAT100 will do strange things like you describe
>
> You have to apply power to the KAT100 before you apply power to the K2. IF you start the K2 first, you get all kinds of strange things going on.
>
> I have my KAT100 in a separate enclosure and on a separate power supply. I forget to start the KAT100 first at times and it does some of the
> same things your seeing.
>
> Hope this helps.
>
> 73 Jerry N0JRN
>
> On Sun, Aug 5, 2018 at 3:29 PM, Bill Coleman <[hidden email]> wrote:
> OK, I have a K2/100 (#2548) connected to a KAT100.
>
> As of late, the KAT100 has been reluctant to turn on. I turn on the K2, and it comes up right away, but the LEDs of the KAT100 often stay off for 20-30 seconds, then come on.
>
> When the KAT100 finally turns on, it often isn’t tracking lo-hi power, as I can rotate the power knob freely from <10 watts to >11 watts, and the KAT100 will stay stuck at a power level, usually low power.
>
> Also, if I try to change antennas, or tune, I’ll get a “not inst” message.
>
> This situation persists for a while. If I let the rig warm up for about 15-20 minutes, I can eventually get the K2 to recognize the KAT100. I may have to cycle the power a half dozen times.
>
> I’ve verified with a scope that the KAT100 is getting the 12CTRL power immediately from the K2, and the internal power on the 5V regulator comes up immediately. It just seems to take it’s sweet time waking up.
>
> I think the fundamental problem may be that the KAT100 isn’t responding to AUXBUS messages at the right point in the power-up sequence, so the K2 assume it’s not installed.
>
> Would appreciate any suggestions on how to troubleshoot this.
>
>
> Bill Coleman, AA4LR, PP-ASEL Mail: [hidden email]
> Web: http://boringhamradiopart.blogspot.com
> Quote: "Not within a thousand years will man ever fly!"
> -- Wilbur Wright, 1901
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Bill Coleman, AA4LR, PP-ASEL Mail: [hidden email]
Web: http://boringhamradiopart.blogspot.com
Quote: "Not within a thousand years will man ever fly!"
-- Wilbur Wright, 1901

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Don Wilhelm

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

Bill,

Fine on the power sequence, but the Not Inst message indicates that
either the Control Cable to the K2 is not fully plugged in (check both
ends) or the cable has a bad connection, or that the firmware in the
KAT100 is not being recognized.

You should tighten the cable jackscrews to check the first, and for the
last situation, try reseating the firmware IC in the KAT100.

73,
Don W3FPR

On 8/5/2018 4:50 PM, Bill Coleman wrote:
> Yes, I have a cable that has the PowerPole connections to the K2/100, and a separate coaxial jack for the KAT100.
>
> I switch the power supply on, which means the KAT100 has power, then switch the K2/100 on, which powers up the combo.
>
> So, yeah, I have power applied to the KAT100 before the K2.
>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Bill Coleman-2

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

Jack screws appear to be tight on both ends.

After I cycle the power 6-12 times, it will eventually come up. I wonder if I have a bad PIC chip in the KAT100. I may try an older version of the firmware, I think I have one. That will take a few days.

I can put a scope on Pin 40 of the PIC chip. I see transitions. Anything I can diagnose with a scope?

> On Aug 5, 2018, at 5:14 PM, Don Wilhelm <[hidden email]> wrote:
>
> Bill,
>
> Fine on the power sequence, but the Not Inst message indicates that either the Control Cable to the K2 is not fully plugged in (check both ends) or the cable has a bad connection, or that the firmware in the KAT100 is not being recognized.
>
> You should tighten the cable jackscrews to check the first, and for the last situation, try reseating the firmware IC in the KAT100.
>
> 73,
> Don W3FPR
>
> On 8/5/2018 4:50 PM, Bill Coleman wrote:
>> Yes, I have a cable that has the PowerPole connections to the K2/100, and a separate coaxial jack for the KAT100.
>> I switch the power supply on, which means the KAT100 has power, then switch the K2/100 on, which powers up the combo.
>> So, yeah, I have power applied to the KAT100 before the K2.

Don Wilhelm

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

Bill,

If it were a bad PIC chip, the results would be consistent. Reseat the
KAT100 firmware Ic to clear away oxidation.
Look for a flaky connection on the Control cable - at both ends.

There is not much that you can diagnose with a 'scope other than to
determine that the chip is getting transitions to it.
If you want to reverse engineer the K2 AUXBUS, then you could make some
determination of the AUXBUS correctness, but that is a difficult
exercise in futility IMHO.

73,
Don W3FPR

On 8/5/2018 5:36 PM, Bill Coleman wrote:
> Jack screws appear to be tight on both ends.
>
> After I cycle the power 6-12 times, it will eventually come up. I wonder if I have a bad PIC chip in the KAT100. I may try an older version of the firmware, I think I have one. That will take a few days.
>
> I can put a scope on Pin 40 of the PIC chip. I see transitions. Anything I can diagnose with a scope?
>
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Bob McGraw - K4TAX

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

I would configure the station power such that the tuner is powered from the switched source on the radio. Thus the power supply is on first and then the radio is turned on and powers the tuner at the same time.

Bob, K4TAX

Sent from my iPhone

> On Aug 5, 2018, at 6:02 PM, Don Wilhelm <[hidden email]> wrote:
>
> Bill,
>
> If it were a bad PIC chip, the results would be consistent. Reseat the KAT100 firmware Ic to clear away oxidation.
> Look for a flaky connection on the Control cable - at both ends.
>
> There is not much that you can diagnose with a 'scope other than to determine that the chip is getting transitions to it.
> If you want to reverse engineer the K2 AUXBUS, then you could make some determination of the AUXBUS correctness, but that is a difficult exercise in futility IMHO.
>
> 73,
> Don W3FPR
>
>> On 8/5/2018 5:36 PM, Bill Coleman wrote:
>> Jack screws appear to be tight on both ends.
>>
>> After I cycle the power 6-12 times, it will eventually come up. I wonder if I have a bad PIC chip in the KAT100. I may try an older version of the firmware, I think I have one. That will take a few days.
>>
>> I can put a scope on Pin 40 of the PIC chip. I see transitions. Anything I can diagnose with a scope?
>>
>>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Bill Coleman-2

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

That’s not the way Elecraft recommends. The KAT100 contains an electronic switching mechanism. Power must be present at the KAT100 coaxial connection before the K2 is switched on. The KAT100 uses the 12CTRL voltage from the DB-9 connector to turn on it’s internal supply.

> On Aug 5, 2018, at 7:29 PM, Bob McGraw K4TAX <[hidden email]> wrote:
>
> I would configure the station power such that the tuner is powered from the switched source on the radio. Thus the power supply is on first and then the radio is turned on and powers the tuner at the same time.
>
> Bob, K4TAX
>
>
> Sent from my iPhone
>
>> On Aug 5, 2018, at 6:02 PM, Don Wilhelm <[hidden email]> wrote:
>>
>> Bill,
>>
>> If it were a bad PIC chip, the results would be consistent. Reseat the KAT100 firmware Ic to clear away oxidation.
>> Look for a flaky connection on the Control cable - at both ends.
>>
>> There is not much that you can diagnose with a 'scope other than to determine that the chip is getting transitions to it.
>> If you want to reverse engineer the K2 AUXBUS, then you could make some determination of the AUXBUS correctness, but that is a difficult exercise in futility IMHO.
>>
>> 73,
>> Don W3FPR
>>
>>> On 8/5/2018 5:36 PM, Bill Coleman wrote:
>>> Jack screws appear to be tight on both ends.
>>>
>>> After I cycle the power 6-12 times, it will eventually come up. I wonder if I have a bad PIC chip in the KAT100. I may try an older version of the firmware, I think I have one. That will take a few days.
>>>
>>> I can put a scope on Pin 40 of the PIC chip. I see transitions. Anything I can diagnose with a scope?
>>>
>>>
>>
>> ______________________________________________________________
>> Elecraft mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/elecraft
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:[hidden email]
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>> Message delivered to [hidden email]
>>
>
>

Bill Coleman-2

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

In reply to this post by Don Wilhelm

I pulled out the KAT100 PIC chip and re-inserted. No change.

I can confirm that transition ARE reaching Pin 40 on the KAT100 PIC chip. I see roughly three bursts. Two come shortly after turn-on, the third comes a second later.

I think you’d need a storage scope or logic analyzer to reverse engineer the AUXBUS. I don’t have that kind of equipment available.

> On Aug 5, 2018, at 7:02 PM, Don Wilhelm <[hidden email]> wrote:
>
> Bill,
>
> If it were a bad PIC chip, the results would be consistent. Reseat the KAT100 firmware Ic to clear away oxidation.
> Look for a flaky connection on the Control cable - at both ends.
>
> There is not much that you can diagnose with a 'scope other than to determine that the chip is getting transitions to it.
> If you want to reverse engineer the K2 AUXBUS, then you could make some determination of the AUXBUS correctness, but that is a difficult exercise in futility IMHO.
>
> 73,
> Don W3FPR
>
> On 8/5/2018 5:36 PM, Bill Coleman wrote:
>> Jack screws appear to be tight on both ends.
>>
>> After I cycle the power 6-12 times, it will eventually come up. I wonder if I have a bad PIC chip in the KAT100. I may try an older version of the firmware, I think I have one. That will take a few days.
>>
>> I can put a scope on Pin 40 of the PIC chip. I see transitions. Anything I can diagnose with a scope?
>>
>>
>

Bill Coleman-2

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

Sadly, I have no old PIC chips for the KAT100 in my inventory. It came out of the box with the 1.04 firmware (which isn’t the latest, but I don’t have the K60XV, either.)

I do have a second DB9 cable I can try, if I can find it.

> On Aug 6, 2018, at 7:05 AM, Bill Coleman <[hidden email]> wrote:
>
> I pulled out the KAT100 PIC chip and re-inserted. No change.
>
> I can confirm that transition ARE reaching Pin 40 on the KAT100 PIC chip. I see roughly three bursts. Two come shortly after turn-on, the third comes a second later.
>
> I think you’d need a storage scope or logic analyzer to reverse engineer the AUXBUS. I don’t have that kind of equipment available.
>
>
>> On Aug 5, 2018, at 7:02 PM, Don Wilhelm <[hidden email]> wrote:
>>
>> Bill,
>>
>> If it were a bad PIC chip, the results would be consistent. Reseat the KAT100 firmware Ic to clear away oxidation.
>> Look for a flaky connection on the Control cable - at both ends.
>>
>> There is not much that you can diagnose with a 'scope other than to determine that the chip is getting transitions to it.
>> If you want to reverse engineer the K2 AUXBUS, then you could make some determination of the AUXBUS correctness, but that is a difficult exercise in futility IMHO.
>>
>> 73,
>> Don W3FPR
>>
>> On 8/5/2018 5:36 PM, Bill Coleman wrote:
>>> Jack screws appear to be tight on both ends.
>>>
>>> After I cycle the power 6-12 times, it will eventually come up. I wonder if I have a bad PIC chip in the KAT100. I may try an older version of the firmware, I think I have one. That will take a few days.
>>>
>>> I can put a scope on Pin 40 of the PIC chip. I see transitions. Anything I can diagnose with a scope?
>>>
>>>
>>
>
> Bill Coleman, AA4LR, PP-ASEL Mail: [hidden email]
> Web: http://boringhamradiopart.blogspot.com
> Quote: "Not within a thousand years will man ever fly!"
> -- Wilbur Wright, 1901
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]

Don Wilhelm

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

Bill,

Are you looking at the K2 MCU firmware or the KAT100 firmware?
The KAT100 firmware currently is 1.05, and the 1.04 should work OK.

If you looked at the K2 firmware (hold any button while powering on and
it will be briefly displayed), then the level to support the KAT100 must
be 2.03d or above.

73,
Don W3FPR

On 8/7/2018 1:57 PM, Bill Coleman wrote:
> Sadly, I have no old PIC chips for the KAT100 in my inventory. It came out of the box with the 1.04 firmware (which isn’t the latest, but I don’t have the K60XV, either.)
>
> I do have a second DB9 cable I can try, if I can find it.
>
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Bill Coleman-2

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

In reply to this post by Bill Coleman-2

OK. I could use a little more help with this issue.

Let’s re-cap where we are.

Issue:

KAT100 doesn’t always turn on right away. When it does this, it may or may not switch low/high power LEDs when the power control is rotated. Pressing Ant 1/2 or Tune, the K2 will indicate “not inst”. Sometimes it will power up just fine.

Observations:

- If powered on incorrectly, the KAT100 never “recovers” — if the K2 doesn’t see the KAT100 at power up, it never discovers it.

- Generally fails when unit is cold / not used in a while, will eventually work if turned and left on for several hours, then switched off and back on.

- KAT100 is receiving power before the K2 is switched on. When the K2 is switched on the 12CTRL line on J3 pin 8 comes up immediately, and the 5V output from U8 does as well. So, power is immediately available when the K2 is switched on

- When the KAT100 works, the ANT 1/2 and Low / High Power LEDs light immediately on power-on.

- When the KAT100 fails, the ANT 1/2 and Low / High Power LEDs stay dark for a second or so, sometimes a few seconds

- AUXBUS transitions are coming in on J3 pin 6 and make it all the way to U1 Pin 40.

- I have two different interconnect cables. One is a three-way cable built exactly to the KAT100 specs, complete with jackscrews. The other is a simple two-way cable that connects Pin 1 and Pin 6-9 straight through with no jackscrews. Failure occurs with either cable.

- I have reseated the U1 chip in its socket with no change in behavior.

My current working theory is that there’s something in the KAT100 that prevents the U1 chip from resetting quickly. If it comes up immediately, the LEDs light and the K2 catches the unit during initialization. If its sleepy and doesn’t come up right away, it misses the opportunity to initialize and the K2 doesn’t know it is there. I think the antenna tuner and the low/high power indication are done in two separate initialization steps, because sometimes the KAT100 will respond to turning the power knob, and sometimes it won’t when the Ant 1/2 / Tune always responds with “not inst”.

Nothing else in the K2 apparently suffers from any AUXBUS failures, all the other units - SSB, NB, DSP, KPA100 always come up right away. This makes me think the issue isn’t with the K2, but perhaps with the KAT100 alone.

Anyone have suggestions? I’d really like to make my K2/100 with KAT100 a reliable rig again. I don’t want to have to power it up a day before I want to use it.

> On Aug 7, 2018, at 1:57 PM, Bill Coleman <[hidden email]> wrote:
>
> Sadly, I have no old PIC chips for the KAT100 in my inventory. It came out of the box with the 1.04 firmware (which isn’t the latest, but I don’t have the K60XV, either.)
>
> I do have a second DB9 cable I can try, if I can find it.
>
>> On Aug 6, 2018, at 7:05 AM, Bill Coleman <[hidden email]> wrote:
>>
>> I pulled out the KAT100 PIC chip and re-inserted. No change.
>>
>> I can confirm that transition ARE reaching Pin 40 on the KAT100 PIC chip. I see roughly three bursts. Two come shortly after turn-on, the third comes a second later.
>>
>> I think you’d need a storage scope or logic analyzer to reverse engineer the AUXBUS. I don’t have that kind of equipment available.
>>
>>
>>> On Aug 5, 2018, at 7:02 PM, Don Wilhelm <[hidden email]> wrote:
>>>
>>> Bill,
>>>
>>> If it were a bad PIC chip, the results would be consistent. Reseat the KAT100 firmware Ic to clear away oxidation.
>>> Look for a flaky connection on the Control cable - at both ends.
>>>
>>> There is not much that you can diagnose with a 'scope other than to determine that the chip is getting transitions to it.
>>> If you want to reverse engineer the K2 AUXBUS, then you could make some determination of the AUXBUS correctness, but that is a difficult exercise in futility IMHO.
>>>
>>> 73,
>>> Don W3FPR
>>>
>>> On 8/5/2018 5:36 PM, Bill Coleman wrote:
>>>> Jack screws appear to be tight on both ends.
>>>>
>>>> After I cycle the power 6-12 times, it will eventually come up. I wonder if I have a bad PIC chip in the KAT100. I may try an older version of the firmware, I think I have one. That will take a few days.
>>>>
>>>> I can put a scope on Pin 40 of the PIC chip. I see transitions. Anything I can diagnose with a scope?
>>>>
>>>>

Don Wilhelm

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

Bill,

The AUXBUS is NOT at fault.
The parts to concentrate on are shown in the lower left corner of sheet
2 of the KAT100 manual. Something there is not working reliably. My
first guess would be Q2, but it could be something else associated.

That entire powering circuit is controlled only by the 12CTRL signal
from the K2.

73,
Don W3FPR

On 8/19/2018 9:32 PM, Bill Coleman wrote:

> OK. I could use a little more help with this issue.
>
> Let’s re-cap where we are.
>
> Issue:
>
> KAT100 doesn’t always turn on right away. When it does this, it may or may not switch low/high power LEDs when the power control is rotated. Pressing Ant 1/2 or Tune, the K2 will indicate “not inst”. Sometimes it will power up just fine.
>
> Observations:
>
> - If powered on incorrectly, the KAT100 never “recovers” — if the K2 doesn’t see the KAT100 at power up, it never discovers it.
>
> - Generally fails when unit is cold / not used in a while, will eventually work if turned and left on for several hours, then switched off and back on.
>
> - KAT100 is receiving power before the K2 is switched on. When the K2 is switched on the 12CTRL line on J3 pin 8 comes up immediately, and the 5V output from U8 does as well. So, power is immediately available when the K2 is switched on
>
> - When the KAT100 works, the ANT 1/2 and Low / High Power LEDs light immediately on power-on.
>
> - When the KAT100 fails, the ANT 1/2 and Low / High Power LEDs stay dark for a second or so, sometimes a few seconds
>
> - AUXBUS transitions are coming in on J3 pin 6 and make it all the way to U1 Pin 40.
>
> - I have two different interconnect cables. One is a three-way cable built exactly to the KAT100 specs, complete with jackscrews. The other is a simple two-way cable that connects Pin 1 and Pin 6-9 straight through with no jackscrews. Failure occurs with either cable.
>
> - I have reseated the U1 chip in its socket with no change in behavior.
>
> My current working theory is that there’s something in the KAT100 that prevents the U1 chip from resetting quickly. If it comes up immediately, the LEDs light and the K2 catches the unit during initialization. If its sleepy and doesn’t come up right away, it misses the opportunity to initialize and the K2 doesn’t know it is there. I think the antenna tuner and the low/high power indication are done in two separate initialization steps, because sometimes the KAT100 will respond to turning the power knob, and sometimes it won’t when the Ant 1/2 / Tune always responds with “not inst”.
>
> Nothing else in the K2 apparently suffers from any AUXBUS failures, all the other units - SSB, NB, DSP, KPA100 always come up right away. This makes me think the issue isn’t with the K2, but perhaps with the KAT100 alone.
>
> Anyone have suggestions? I’d really like to make my K2/100 with KAT100 a reliable rig again. I don’t want to have to power it up a day before I want to use it.
>

Bill Coleman-2

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

I’ve confirmed that 5V power on the output of U8 comes up IMMEDIATELY when the K2 is switched on. Q2 seems to be doing it’s job. However, the KAT100 will sit there without any LEDs for a while, sometimes seconds.

I’m beginning to wonder if Z1 is not oscillating right away. I need to check that. If there’s no clock signal, the chip won’t initialize, and miss the AUXBUS startup window.

I really can’t think of many other things that could cause this behavior.

> On Aug 21, 2018, at 4:23 PM, Don Wilhelm <[hidden email]> wrote:
>
> Bill,
>
> The AUXBUS is NOT at fault.
> The parts to concentrate on are shown in the lower left corner of sheet 2 of the KAT100 manual. Something there is not working reliably. My first guess would be Q2, but it could be something else associated.
>
> That entire powering circuit is controlled only by the 12CTRL signal from the K2.
>
> 73,
> Don W3FPR
>
> On 8/19/2018 9:32 PM, Bill Coleman wrote:
>> OK. I could use a little more help with this issue.
>>
>> Let’s re-cap where we are.
>>
>> Issue:
>>
>> KAT100 doesn’t always turn on right away. When it does this, it may or may not switch low/high power LEDs when the power control is rotated. Pressing Ant 1/2 or Tune, the K2 will indicate “not inst”. Sometimes it will power up just fine.
>>
>> Observations:
>>
>> - If powered on incorrectly, the KAT100 never “recovers” — if the K2 doesn’t see the KAT100 at power up, it never discovers it.
>>
>> - Generally fails when unit is cold / not used in a while, will eventually work if turned and left on for several hours, then switched off and back on.
>>
>> - KAT100 is receiving power before the K2 is switched on. When the K2 is switched on the 12CTRL line on J3 pin 8 comes up immediately, and the 5V output from U8 does as well. So, power is immediately available when the K2 is switched on
>>
>> - When the KAT100 works, the ANT 1/2 and Low / High Power LEDs light immediately on power-on.
>>
>> - When the KAT100 fails, the ANT 1/2 and Low / High Power LEDs stay dark for a second or so, sometimes a few seconds
>>
>> - AUXBUS transitions are coming in on J3 pin 6 and make it all the way to U1 Pin 40.
>>
>> - I have two different interconnect cables. One is a three-way cable built exactly to the KAT100 specs, complete with jackscrews. The other is a simple two-way cable that connects Pin 1 and Pin 6-9 straight through with no jackscrews. Failure occurs with either cable.
>>
>> - I have reseated the U1 chip in its socket with no change in behavior.
>>
>> My current working theory is that there’s something in the KAT100 that prevents the U1 chip from resetting quickly. If it comes up immediately, the LEDs light and the K2 catches the unit during initialization. If its sleepy and doesn’t come up right away, it misses the opportunity to initialize and the K2 doesn’t know it is there. I think the antenna tuner and the low/high power indication are done in two separate initialization steps, because sometimes the KAT100 will respond to turning the power knob, and sometimes it won’t when the Ant 1/2 / Tune always responds with “not inst”.
>>
>> Nothing else in the K2 apparently suffers from any AUXBUS failures, all the other units - SSB, NB, DSP, KPA100 always come up right away. This makes me think the issue isn’t with the K2, but perhaps with the KAT100 alone.
>>
>> Anyone have suggestions? I’d really like to make my K2/100 with KAT100 a reliable rig again. I don’t want to have to power it up a day before I want to use it.
>>
>

Bill Coleman-2

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

In reply to this post by Don Wilhelm

OK, a final follow-up on this.

Since the 12CTRL signal resulted in 5V power at the regulator immediately, I racked by brain trying to figure out why The KAT100 would fail to light the LEDs for seconds, sometimes tens of seconds.

I decided the problem might have to do with the U1 clock. I put a scope probe on pins 13 and 14 of U1. While the KAT100 fails, these pins would float up to about 1 volt. When it worked, these pins would be at 0 volts, because the chip is sleeping! (the oscillator doesn’t run while the chip sleeps, to save battery power) So, it looked very much like the oscillator wasn’t starting reliably at power-on.

I hit the Z1 resonator with a heat gun, with no immediate effect. Later I nudged Z1 with a screwdriver, and the KAT100 suddenly came to life. Not sure if I had a bad device, or just a bad solder connection, I re-flowed the solder connections to Z1 and to pins 12-14 of U1, where they connect.

This seemed to work. I let everything cool down overnight, and checked it again in the morning. Oddly, the K2 was giving Info 080 and the KAT100 was failing again! I didn’t have time to diagnose.

Today, however, the K2 powered right up, and the KAT100 snapped to attention, both working flawlessly.

At the moment, I’m going to declare the mystery as being solved, and ignore the transient Info 080 issue. If it crops up again, I think I will replace Z1 on the KAT100.

Don Wilhelm

Re: KAT100 - Reluctant to come on, K2 often displays "not inst"

Bill,

With that evidence, I would arbitrarily replace Z1. Those 4MHz
resonators are inexpensive.

73,
Don W3FPR

On 9/5/2018 2:42 PM, Bill Coleman wrote:

> OK, a final follow-up on this.
>
> Since the 12CTRL signal resulted in 5V power at the regulator immediately, I racked by brain trying to figure out why The KAT100 would fail to light the LEDs for seconds, sometimes tens of seconds.
>
> I decided the problem might have to do with the U1 clock. I put a scope probe on pins 13 and 14 of U1. While the KAT100 fails, these pins would float up to about 1 volt. When it worked, these pins would be at 0 volts, because the chip is sleeping! (the oscillator doesn’t run while the chip sleeps, to save battery power) So, it looked very much like the oscillator wasn’t starting reliably at power-on.
>
> I hit the Z1 resonator with a heat gun, with no immediate effect. Later I nudged Z1 with a screwdriver, and the KAT100 suddenly came to life. Not sure if I had a bad device, or just a bad solder connection, I re-flowed the solder connections to Z1 and to pins 12-14 of U1, where they connect.
>
> This seemed to work. I let everything cool down overnight, and checked it again in the morning. Oddly, the K2 was giving Info 080 and the KAT100 was failing again! I didn’t have time to diagnose.
>
> Today, however, the K2 powered right up, and the KAT100 snapped to attention, both working flawlessly.
>
> At the moment, I’m going to declare the mystery as being solved, and ignore the transient Info 080 issue. If it crops up again, I think I will replace Z1 on the KAT100.
>
>