Trying to fix some new year lanterns, need a lil assist


Recommended Posts

Hi all. I've had this line of chinese new year lanterns (basically christmas lights) for a long time, but then wires have completely deteriorated. They came from a Chinese store back in 2006, real nice set, but they're unusable now :( Thought I'd go and cut up some modern christmas lights and rebuild the set by hand. I went and tested them, but 1 side keeps blowing out. I'm certain that I'm not terminating the middle wire correctly. I know nothing about schematics or symbols, so I just drew a crude diagram. Two of the lines have 9 lights each, then there's the middle wire and I'm not sure how to terminate these lines. Might anyone know?

So far, I tried connecting all 3 together at the end, which leads to one side blowing out.  In the drawing, the right line blows out, left side does light up, but none of the bulbs are affected by the blow out of the right line.

There's also the possibility I connected the wrong wires to the controller in the wrong order. I'm almost certain the middle was the line with no lights, could be wrong.. Suggestions?

 

https://imgur.com/a/yfb1OZa  (drawing)

https://imgur.com/a/rozzT2b (the controller and the wires)

Edited by Izlude

Are they incandescent bulbs or LEDs? Do you have a photo or information (e.g. part number, voltage) about the actual bulbs themselves?

At the opposite and from the controller, did the original string have a female plug to daisy chain another string of lights?

Do you have a photo of the other side of the controller circuit board?

Edited by ShadeOfBlue

Hi just got back from work. Here's some images and info. It uses incandescent bulbs. There was no female plug on the opposite end of the string, but it did have a female on the back of the main plug itself. The main plug was only 2 wires to begin with, as is the donor. Original plug is 3A 125V, the donor is also 3A 125v with fuses. The capacitor on the board of the controller is 50v 4.7uf.  I have no details about the bulbs themselves, they were all pretty deteriorated anyway. Pulling them out of the sockets left crumbling plastic.

Someone did make a blog post bout a very similar set of lights, but theirs are LEDs while mine are incandescent, and my set only had 18 lights. I might even go as far as to say it's the exact same thing. A schematic is provided.
https://amaldev.blog/christmas-led-light-teardown/

It's too bad I can't see clear enough on their wire config, else I'd have tried to copy it. Anyway, here's mine.


APCGW9O.png

Edited by Izlude

That post is indeed very similar to yours. Since yours uses incandescent bulbs, it won't need the inline resistors. And there are some minor differences around the control chip. But other than that, it's essentially the same thing.

Your idea of tying all 3 wires together at the far end is correct. The third wire is just for current to return from the far end. Assuming all the connections are soldered tightly and the bulbs are good, the problem must lie on the controller board.

I would suspect one of the 2 SCRs (black components with 3 leads) next to the outputs. Either that or the controller chip, but there's nothing you can do about that.

When you say one side "blows out", do you mean it just doesn't light (or lights only for a moment)? Or do you mean one or more bulbs gets damaged?

If I were repairing this, I would be probing things with a mutimeter. But, as long as the bulbs are not getting damaged, an easy way to check for a bad SCR is to just swap them (making absolutely sure to place the 3 leads into the correct locations). If the problem also moves to the other side, then you know it's that SCR that is bad. And I'm sure you could find a replacement for it.

  • Like 2

sorry i thought i clicked submit >.<

Well it turns out the board is shot. I might have.. killed it. Apparently the wire without lights (going to the mains) is supposed to be on the far left with the capacitor, not the middle. The other two lines have the 3 prong components (pcr406's), those lines were meant for the lights. Not sure how I missed that. After rearranging them in the right order, nothing turns on anymore. I did manage to locate some of these lights on a Philippines online market called carrousel. I'll see if I can order one of those and this time put the wires in the right spots. Sorry to trouble you :( 

Well I hope you get something that you are happy with.

You are correct that the return wire should go straight to the plug, while the ones with bulbs should be connected to the SCRs. Having them in the wrong order would cause the current out of one SCR to flow through one string of bulbs, while the current from the other SCR would flow through both strings in series. This would cause bulbs to be on/off/dim at unexpected times, but it shouldn't cause any damage. So that is strange.

Lights1.jpg.fc36bd3c5a4598c0d3032c220d5ebae1.jpg

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Yup, that's a doozy right there 😄
    • It's a bundle of tools created by a variety of people, so things can go wrong sometimes. It's a great addition to Windows, and I use a lot of the tools on a daily basis. Also, it's still a 0.**** release so quick updates are to be expected 😉
    • Oh, I did. And it's even worse than I was hoping! Besides a lot of techno-babble jargon (yes I understand 100% of it but it's still all just techno-babble) there's 2 key points that make me super-weary about even considering testing this out. -- By default, after installation, a relay is automatically set up, so you do not need to care about that. * Non-chatmail apps use email servers as a long-term message archive while chatmail clients use email servers for ephemeral instant message relay. * Supporting the full variety of classic email setups would require considerable development and maintenance efforts, and complicate making chatmail-based messaging more resilient, reliable and fast. -- Basically, the end-user device is the 'server' (relay) so there is NO ARCHIVING whatsoever because every message is necessarily ephemeral. Great for techno-paranoia (and for illicit activities preferring no tracks to cover) but terrible for everybody else. It's also ironically contradictory to engineering principles of redundancies besides the transport layers due to the explicit absence of any persistent storage. Instead of 'classic email address' retaining multi-GB messaging archives on its server, now every device must retain 100% of those storage demands. (Email messages were originally meant to be short correspondences, not the multi-MB attachments boondoggle that now exists with unlimited spam engines flooding every potential recipient.) Any device swap or reset (or loss) makes the entire message history go bye-bye forever... lest there's an off-device auto-archival "relay" mechanism that's really a separate server that holds onto all transported messages (an email server) that utilizes 'chatmail email address' identities (like an email server) and its own persistent storage archive (like an email server). But... this solution is hoping to exist alongside real-world email address identities (based on the email server relay pathway) but simply render messages in chat thread format in an ephemeral manner (with contents being encrypted, and messages auto-expiring) ... In the end, it's a chat app/experience for the Web3/P2P-at-all-costs zealots. (I have accts on all sorts of federated web3 services so I understand the technical and non-technical alike.) For any practical users, however, it's just another service to download/install, register, cross-share id cards/qr codes, but know that there's no history/archive whatsoever (by design) so no account/message recovery whatsoever... update the device, install a bummed update patch, or dare upgrade your device... all history, poof, gone. Ya gotta start everything over again like they're a brand new person.
    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!