From: noreply@ademu.com
On 2023-09-07 13:53, legg wrote:
> On Thu, 7 Sep 2023 09:56:22 +0200, Arie de Muijnck
> wrote:
>
>> On 2023-09-07 01:49, legg wrote:
>>> On Wed, 6 Sep 2023 20:38:27 +0200, Arie de Muijnck
>>> wrote:
>>>
>>>
>>>>> I see no I2C data traffic to the lamp control IC U2
>>>>> - both lines pulled low.
>>>>
>>>> That is an illegal state, I2C idle is both lines high.
>>>> This indicates a double short, or a bad 16-bit expander.
>>>>
>>>
>>> Can now see I2C clk and data lines are running when either
>>> the charger is connected or the unit is playing.
>>>
>>> The low condition occurs when the charger is disconnected
>>> and the unit is not playing (ie is off). I guess that is
>>> reasonable. . . . silly me. . . . or I could have been
>>> measuring the wrong pins on the wrong IC (it has happened
>>> before).
>>>
>>> The volume control switches are routed through the TPS1116
>>> - and THEY are functional. I can see the volume inc and
>>> decrement on the I2C lines in response to a button press
>>> and hear the difference.
>>>
>>> . . . . .but the battery capacity indicators and others
>>> (besides the CPU-driven 1/0 white and BT blue connect) are
>>> not being driven from the TPS1116 pins.
>>>
>>> RL
>>
>> So maybe the MCU does not know the battery condition?
>> Or the measured value is out of spec. Check voltage dividers etc.
>> Does the charging stop automatically or MCU controlled?
>> Do you have a USB-USB charge measuring dongle?
>> (The schematics are mostly unreadable for me).
>>
>> Arie
>
> I'd expect a false battery measurement by MCU to
> produce a low battery lamp, or not to run at all,
> but will check. OFF lamps are confirmed at TPS1116
> output ports, so it's not a harnessing issue.
>
> MCU also looks at USB input voltage. Considering that
> turn-on is now triggered by USB removal, it could be
> that measurement that's duff.
>
> Battery charging is by MP2637 from USB, without I2C com,
> so probably independent, with flags back and forth.
> I'm monitoring USB input current flow with a UN34C.
>
> During normal charge input current never exceeds 500mA.
> Spends most of its time between 360 and 300mA below
> 3V9 terminal voltage, reducing gradually to 100mA as
> 4V exceeded. Bttery capacity 3000mA, so not a quick
> charge.
>
> Charging terminates gradually as battery exceeds 4V0 and
> approaches 4V17, It's hysteretic (slight audible squeeling
> detectable), so not a regulation text book CV charge
> termination.
>
> Would be inconvenient for Player to be interrupted by
> USB insertion - either charge or play - this is not
> likely a normal behavior.
>
> Boost converter MP9428 regulation also seems local - no
> I2C with flags. See no issues in the usual power-
> handling sections or supply gating switches.
>
> Service manual skinny on normal operation, fault diag
> or lamp - button press codes/procedures. I republished
> the schematics for view on normal page sizes, but expect
> loss of PC text search ability in the results.
>
> Also some cryptic button pushing instructions from
> another source.
>
> http://ve3ute.ca/query/flip3.zip
>
> RL
Thanks for the proper diagrams.
I noticed that all problems seem to be with the switches and the battery state
LEDs.
In the flip3 indicators diagram those have the GND pin in common. The other
LEDs are using VCC.
Could it be that GND in that connection (J11 pin 13 to J9 pin 1) has a bad
contact?
That would explain most (all?) problems.
You could solder a jumper wire in parallel from PCB to PCB to test this
hypothesis.
Arie
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
