Digest for sci.electronics.repair@googlegroups.com - 9 updates in 5 topics

bob prohaska <bp@www.zefox.net>: May 13 01:57AM

>> USB audio capture "card" so as to better understand how to use it and
 
> paste here the relevant output of the command
 
> lspci -vv
 
The device is USB 2.0 and is plugged into the USB 2.0 ports on the Pi, which
aren't accessed via PCI.
 
lsusb reports
 
Bus 002 Device 002: ID 152d:1561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS561U two ports SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 2034:0105
Bus 001 Device 005: ID 413c:3010 Dell Computer Corp. Optical Wheel Mouse
Bus 001 Device 004: ID 413c:2002 Dell Computer Corp. SK-8125 Keyboard
Bus 001 Device 003: ID 413c:1002 Dell Computer Corp. Keyboard Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 
I tend to think it's probably
Bus 001 Device 007: ID 2034:0105
which was the last USB device plugged in.
 
lspci reports
 
00:00.0 PCI bridge: Broadcom Limited Device 2711 (rev 10) (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 61
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00000000-00000fff
Memory behind bridge: c0000000-c00fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [ac] Express (v2) Root Port (Slot-), MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <2us, L1 <4us
ClockPM+ Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible+
RootCap: CRSVisible+
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [180 v1] Vendor Specific Information: ID=0000 Rev=0 Len=028 <?>
Capabilities: [240 v1] L1 PM Substates
L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
PortCommonModeRestoreTime=8us PortTPowerOnTime=10us
L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
T_CommonMode=1us LTR1.2_Threshold=0ns
L1SubCtl2: T_PwrOn=10us
Kernel driver in use: pcieport
 
01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) (prog-if 30 [XHCI])
Subsystem: VIA Technologies, Inc. VL805 USB 3.0 Host Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 62
Region 0: Memory at 600000000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot-,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: 00000000fffffffc Data: 6540
Capabilities: [c4] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0.000W
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <2us, L1 <16us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis+
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Kernel driver in use: xhci_hcd
 
[sorry about the messed up line breaks]
 
If you can find it in there my hat's off to you!
 
Thanks, for writing,
 
bob prohaska
Adrian Caspersz <email@here.invalid>: May 13 04:41PM +0100

On 13/05/2021 02:57, bob prohaska wrote:
> Bus 001 Device 007: ID 2034:0105
> which was the last USB device plugged in.
 
 
> If you can find it in there my hat's off to you!
 
Yup, my bad :) lsusb it should have been.
 
https://the-sz.com/products/usbid/index.php?v=0x2034&p=0x0105&n=
 
iSoft Silicon, Inc. (defunct website)
 
https://web.archive.org/web/20190122082235/http://www.isoft.com.tw/english/products_01.html
 
"IS-821
USB stereo ADC, stereo line-in and mono MIC-in, I2C interface, 28-pin
SSOP pack"
 
Bit of a dead end, but that site says
 
"Soft's audio chips are fully compatible the USB plug-and-play profile.
Under most OS platforms, there is no private driver required."
 
However for electrical specs, pinout etc, I've drawn a blank.
 
--
Adrian C
bob prohaska <bp@www.zefox.net>: May 13 04:00PM


> "Soft?s audio chips are fully compatible the USB plug-and-play profile.
> Under most OS platforms, there is no private driver required."
 
> However for electrical specs, pinout etc, I've drawn a blank.
 
Hmmm. The last reply from tech support was "... we don't quite understand what the question you are asking means".
 
Maybe it's absurd, but it makes me wonder if the device is a Trojan.
No....that's too clever....
 
Thanks for humoring me,
 
bob prohaska
Cydrome Leader <presence@MUNGEpanix.com>: May 11 01:39AM

>> Peter Wieck
>> Melrose Park, PA
 
> Just bought three pounds of vintage (BOW) 63/37 from ebay. $45 for all three including shipping, about as good as I can find.
 
Is there a good test to determine what mix a solder is? I came across pounds of
large diameter solder likely from a plumber. Not sure what old leaded plumbing
solder was. 50/50 by chance?
Ralph Mowery <rmowery42@charter.net>: May 12 11:29PM -0400

In article <s7cn9c$9jj$1@reader1.panix.com>, presence@MUNGEpanix.com
says...
 
> Is there a good test to determine what mix a solder is? I came across pounds of
> large diameter solder likely from a plumber. Not sure what old leaded plumbing
> solder was. 50/50 by chance?
 
The best easy way it to check the melting point. Heat someting up and
measure the temperature then touch the solder to it. Raise the
temperature 10 deg F at a time . There are charts to tell the melting
temperature of the mixes. Most plumbing solder is the 50/50 mix and
usually too thick to do much electronic work.
"Peter W." <peterwieck33@gmail.com>: May 13 03:48AM -0700

Standard plumbing solder is flux-free and 50:50 tin to lead. Then, there is Acid Flux plumbing solder that should not be allowed in the same county as electronic solder. You can determine which is which by cutting off the end. Acid flux solder will have a visible core containing the acid. Typical acid-core solder is 40:60.
 
If the solder in question is either of those *DO NOT* use it for electronics under any circumstances. And if it is vintage tin/lead solder *DO NOT* even use it for plumbing.
 
Peter Wieck
Melrose Park, PA
Cydrome Leader <presence@MUNGEpanix.com>: May 10 04:33PM

> does require the silver, for chemical compatibility. Some old wire used
> cotton under rubber, for similar reasons (so the insulation COULD be removed,
> not permanently bonded to the wire).
 
Some high temp teflon wire is nickel plated copper. If you can't solder a strand
of the wire, it's nickel plated.
micky <NONONOmisc07@fmguy.com>: May 12 02:34PM -0400

I renamed the thread and moved it from its original location to the
bottom of the list so I wouldn't have to hunt for it so much.
 
 
>> I was out of the dealership by then, but a simple piece of duct tape
>>over the sensor will turn the head lights on constantly when the
>>engine is running. That SHOULD turn on the instrument lights.
 
Okay, I tried that and it did turn on the headlights and taillights.
BUT the ones in question** didn't go on.
 
Yet up until the last time I drove in the dark, two nights ago, they do
go on at night. I will try tonight and see if they still go on at
night, but how that could be different from covering the photocell I
don't know.
 
 
FWIW there are actually two photocells but I covered both of them. When
I first got the car I asked on ToyotaNation or the other one what the
second one was for, and if I got an answer, I forget what it was. Each
as a domed plastic cover but one is 1/4" high or more and the other much
shorter. I wonder why.
 
 
**(Most of the other lights are too dim to see during the daytime, but
they work fine already.)
 
> e-mail me the schematic / wiring diagram and I'll look at it
 
It will take a bit of time to extract the relevant pages from my 390
page wiring diagram. I'll work on it.
 
> Does it get dimmer when the headlights are on? It should.
 
One thing only does dim and that's the little dot/light on the dash that
shows what gear I'm in, and I think that's fair because the other lights
are powered directly from 12v. I haven't tested when the headlights go
on, but instead, I removed the Panel fuse and ran a jumper from the
12v-when-engine-on to one of the locations the Panel fuse powers**, and
when I touch the jumper to that, the dot on the dash goes dimmer and
when I remove it it goes back to full daytime brightness. That is
reliable.
 
Sometimes!!! when I do touch the jumper that way, the "clock" lights go
on, but unreliably and rarely. It will work, then 3 minutes later, it
doesn't. And this testing was done at night (they weren't on to begin
with I used to think because the panel fuse was out, but later I think
they went on without the panel fuse or the hot-wire. I have to do more
testing tonight. Prior testing was very confusing, so I hoped you'd
just know the answer already, although I suppose it's very unlikely
people would complain about something like this and that your service
department would try to rewire a car that was working according to the
Toyota spec.
 
In the daytime I've never gotten them to go on.
 
Do you think there's any chance, once I have the current operation
totally clear and written down, if I wrote to Toyota, they'd tell me why
it works that way, or even how to change it? I figure they'd ignore me
or tell me to go to a dealer.
 
Most of the lights*** are powered directly from the battery when the
Taillight relay is closed, via the Panel fuse, and they don't dim, but
normally they only go on at night. I guess going on is the opposite of
dimming.
 
**From the 12v that powers the seat heater switch to the light for the
seat heater switch, so the wires are only a half inch away from each
other. I thought it would be such an elegant fix, except it doens't
work for the "clock" lights. It does light up all the other lights
below***.
 
***The speedo cluster, glovebox, the buttons for the radio, heater/ac,
seat heater switches, and the gearshift indicator on the center console.
 
And there is a light in the speedometer needle that changes in some way.
I think it lights up at night. It's really all very nice except for my
one complaint. I would have thought lots of people would complain and
by 2006 they would have changed it. I have the digital version of 2006.
It's harder to read than on paper, but I checked to the extent I could
and haven't found any differences related to this. Maybe that they
didn't change it would mean mine is broken, not misdesigned. But I
still should be able to fix it.
 
I'll do more testing when it gets dark, which seems to be different from
having the photocells covered.
 
>It should
>DIM when the headlights are on and be brigher during the day I think.
 
Yes, those gear indicator dots works that way.
 
>Is this an orange/red light? or green?
 
In the speedo cluster, there's a little light for each gear. Park is
green. I think the others are different.
 
 
2005 Toyota Solara (similar to a Camry)
Three Jeeps <jjhudak4@gmail.com>: May 12 10:17AM -0700

On Wednesday, May 12, 2021 at 8:42:38 AM UTC-4, Erik W wrote:
> circuit board without bending down over the device? I suppose a flip up
> or away magnifier might be useful too. I don't wear glasses normally.
 
> Thanks in advance.
I use and like a binocular headband magnifier, very similar to this:
https://www.amazon.com/Headband-Magnifying-Magnifier-Head-Mounted-Electronics/dp/B085DRM3WL/ref=sr_1_25?dchild=1&keywords=headband+magnifier&qid=1620838872&sr=8-25
 
The one I got is a no-name brand that I picked up at a hamfest years ago.
All the lenses are plastic. in addition to one fixed lens, there are two additional lenses that fold up out of the way into the visor. My magnifiers are 2x, 4x, 8x. IMHO, using tools with the 2x and 4x on, such as soldering, requires a little getting used to. I find the 8x almost impossible to use with tools and only comes in handy for inspection and for me, can't be worn for long.
I found the external loop handy in a few situations.
I am not a fan of the built in lighting system as they are not usually well directed to the workpiece and tend not to be very bright.
I like that the visor portion folds up and out of the way when not needed.
Given these are plastic lenses, the optical quality is not that great and may be a challenge if you wear them for a long period of time. If that is the case, I suggest looking at high grade optical lenses (perhaps glass?). The price will definitely go up.
Good luck
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to sci.electronics.repair+unsubscribe@googlegroups.com.

No Response to "Digest for sci.electronics.repair@googlegroups.com - 9 updates in 5 topics"

Post a Comment