Put the bulb in series with the outlet on the wall and the primary of the transformer. Basically, In series with or in place of, the fuse.
You may have heard this: The transistor blows just in time to protect the fuse. So, now you know it's true.
BTW: What do you know about Win 7 and wireless particularly "Red X through wireless icon with connectivity" and related issues.
You may have heard this: The transistor blows just in time to protect the fuse. So, now you know it's true.
Windows problems update
Found errors and warnings for: DHCP Client (1001, 1003) Address config status event and Warnings for 1014 (DNS Client event)
So, made NETBIOS over TCP/IP mandatory. Added my gateway address to list of DNS servers.
Restarted twice: Both OK
Done.Pick up four 22K 1/2 W instead of the 10K 1 W.
Pick up a 1K 1/2 W.
Pick up a 2SA1015.
Done, got a new Q7 underhand, ready to be soldered.1a. Procure Q7
1c. Leave everything as is; Q7, Q8 and Q9 out.
I have a few (3) spare C2240, so out of 5 transistors, should hopefully find a pair with a close match! Will go back to one of your previous posts to figure out how to match them, and let you know how that progresses.2. Remove and match Q1 and Q2 and any NPN transistor that you have, that you don't have to remove.
Install Q1 and Q2. The two with the closest match. Hopefully, within 10% or better.
Let's also try to match Q1 and Q2 within 5-10%.
Here is the data sheet: https://www.electro-tech-online.com/custompdfs/2011/04/2sc2240-1.pdf
Hfe between 200 and 700 is too wide for this application. So try for 0.1 mA of base current and 1000 x would be 1 mA of collector current. Can't go above 20 ma for base current and no more than 100 mA of collector current.
The test circuit should look like; Rb in series with the base, connected to the 1.5V battery and the emitter.
Take a 9V battery and put a resistor, Rc in series with the battery and the collector. The - of the 9V battery should go to the emitter as well. Put voltmeters across Rb and Rc.
Using your battery (1.5 V); the base resistor should be about (1.5-0.6)/0.1e-3 amps.
Multiply this by 1000 (700 with a fudge factor, easy # to multiply)
Take the recalculated current, Ib; (1.5-0.6)/Rb and multiply by 1000.
Size Rc*(ib*1000) to be 5-8 volts. Not critical.
Measure Rb and Rc.
Measure Vb (voltage across Rb), Rc (Voltage across Rc) and make a table.
Transistor n | Rb | Vb | Ib | Rc | Vc | Ic | Ic/Ib
Rb and Rc are fixed
Select the transistors for Q1 and Q2 which have the closest Ic/Ib ratio. Do write down the original Ib/Ic for Q1 & Q2. Now that you've done all of this work keep the transistors labeled by Hfe.
Windows problem.
4 restarts/boots: 50% of the time worked.
The driver is: Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC , Driver version = 2019.1.1203.2010. There is nothing in the release notes that suggest an upgraded driver will fix this issue. I updated about 4 days before the next release.
I like to remove any realtek software installed and just use the default windows manager for network settings. I find that using other software can sometimes confuse it. You can uninstall realtek software, and reinstall only the drivers by manually chosing a driver folder to install.When your in the mode above SOMETIMES it will re-connect to the preferred wireless network. Sometimes it will do the blue ball thing and end up with a yellow ball in the wireless ICON. Selecting and connecting manually works fine. Wireless G, no encryption. Repeater on the preferrred network.
Finding equivalent software is sometimes a pain in Ubuntu. As a last resort, I use "wine", an emulator, or the overkill method, a virtualPC with XP installed, just to run photoshop or whatever I need.... Of course, last resort, I use my dual boot image. You could try to look at services ("services.msg" I think), google what must, and must not necessarily be booted at startup, and remove realtek etc useless stuff. Google yields a tonne of stuff on services to kill to optimize the PC, and in your case, you could possibly look for network services that might be conflicting...Sometimes when using wierd applications like PDANET or SYNCCELL, a tethering app, and even when not using one, sometimes "Media Disconnected" appears. In XP net start "Wireless Zero Autoconfig" fixed the problem and so does re-booting. In Win 7 Pro, stopping and starting "Wlan AutoConfig" doesn't work. Re-booting does.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?