CurtPalme.com Home Theater Forum

barclay66 · Posted: Sat Mar 02, 2013 12:32 pm Post subject:

Hi,

Another look at the schematics leads me to this conclusion:

- The slave processor (U16) should be healthy. Why: It receives and processes the remote commands correctly which is proven by its ability to perform control over the power switching (almost the only thing it can do by itself directly).

- The communication to the main processor (U27) and other "recipients" isn't working anymore. Why: Same as above with the addition that any other remote command than power control requires processor to processor communication.

If my analysis is correct it should be possible to repair the CLM by swapping U18 (74HC374, SMD) and U20 (74HC374, SMD) as these are being used as gates/buffers for the now inoperable communication. There are two more components which are indirectly involved: U6 (74HC245, SMD) and U28 (MACH110-20JC). These would be the next ones to swap if replacement of U18/U20 wouldn't provide success...

Regards,
barclay66

mp20748 · Posted: Sat Mar 02, 2013 1:49 pm Post subject:

**Curt Palme** · Posted: Sat Mar 02, 2013 3:04 pm Post subject:

OK, that's great Mike, thanks! At my end, I'll play with his original CLM in a Marquee once I retube a G90 today, and I'll report back what I find with his CLM.

CIR Engineering · Posted: Sat Mar 02, 2013 4:03 pm Post subject:

Thanks Mike!

I'm really curious what this turns out to be.

craigr

jcoles · Joined: 17 Jul 2008 Posts: 40

Well guys, it's not the CLM. I took it over to Mike's house and popped it into his 9500 and it worked like a charm. Even brought my remote...so back to the drawing board I'm afraid. Will try a different LVPS next.

Tim in Phoenix · Joined: 21 Oct 2006 Posts: 4409 Location: Phoenix

Hello

Did you disconnect the IR sensor and try the wired keypad? The sensor could be flaky or there could be an unwanted IR noise source in the room.

.

**Curt Palme** · Posted: Sun Mar 03, 2013 4:03 pm Post subject:

I'm also wondering if there's a dual issue here, since I was able to duplicate is reported fault here exactly with only his CLM at my place.

Seriously, short of a Sony G70 that would shut down only at 1080p, which turned out to be a corrupt memory location in the CPU board, this is one of the weirdest issues I've run across...

jcoles · Joined: 17 Jul 2008 Posts: 40

Busy morning! I've been trying all the tips you guys have been suggesting. I replaced the LVPS...no difference. I shut the door to all my equipment to block extraneous IR signals...no difference. I unhooked the IR receiver to the PJ and just ran the the wired remote. At the same time I sprayed the EEPROM (?spelling) chip with toluene per Mike's suggestion. The remote worked!! I rehooked up the IR sensor and both remotes were working perfectly. I turned off the PJ and then neither worked. But after a few minutes one of the menu items I had earlier pressed popped up spontaneously and both remotes worked again. Shut the PJ off. 30 mins later I turned it on again and now nothing works.

I'M EXHAUSTED

Tim in Phoenix · Joined: 21 Oct 2006 Posts: 4409 Location: Phoenix

Hello

Some processor is stuck in a loop; unplug the wired keypad and try the IR

.

mp20748 · Posted: Sun Mar 03, 2013 6:03 pm Post subject:

jcoles · Joined: 17 Jul 2008 Posts: 40

The remotes either both work or both don't. I've tried unplugging one or the other, to no avail. Just went down and unplugged the wired remote without improvement. One thing I've noticed is that the red light blinks on the back of the CLM board no matter which remote I use. However, the red light on the wired remote itself will blink when buttons pushed but not on the wireless remote, even when the PJ responds to it. Don't know if this means anything.

Nashou66 · Joined: 12 Jan 2007 Posts: 16171 Location: West Seneca NY

jcoles · Joined: 17 Jul 2008 Posts: 40

Well, the latest is that after letting the PJ remain on for several hrs, I came back to it and the remote worked. I did a convergance on the present setting without incident. Turned the PJ off and then back on again. Usually this is where it fails, but it actually worked again. Turned it off again and when I turned it on again it failed. Put a CLM board in from Mike and got a few button pushed out of it before it too failed. I think we have ruled out a problem with the CLM board as it worked fine on Mike's PJ. Don't think it has anything to do with the wired/wireless remotes either as they both work or both fail in unison. The only reliable button push remains the on-off control. Crying or Very sad

Tim in Phoenix · Joined: 21 Oct 2006 Posts: 4409 Location: Phoenix

Guys

I am thinking flaky backplane IC. There is a small capacitor on the backplane next to the IC, try breaking off the capacitor with needlenose pliers, there is nothing to lose at this point.

.

jcoles · Joined: 17 Jul 2008 Posts: 40

I don't know if this means anything, but while watching a movie in my only available setting, I was about half-way thru and menu items popped up that I had pressed before starting the movie. I guess this is what's meant by "ghost in the machine"

Nashou66 · Joined: 12 Jan 2007 Posts: 16171 Location: West Seneca NY

I still think a complete initialization will fix this . Did you try it?

Nashou

**Curt Palme** · Posted: Wed Mar 06, 2013 7:40 pm Post subject:

So I put the bad CLM with the nonworking IR back into my test set (different chassis from the last time I was playing with it), and sure enough, in wired mode all buttons work, in wireless only the power button works. Customer's programming still in the board. I then press the reset button on the CLM, and as expected, it shuts down.

FIre the set back up again, and wireless still only works with the power button. But wait, I press other buttons at random, and very slowly they also start to work. A minute in, and all of them are now working, both with wired and wireless.

So I'll let this thing heat up a bit and see if I can get it to fail again. If it does, I'll wipe out all programming by doing a complete initialization to get rid of all parameters. Then I'll see if the board works completely wiped. Weirder and weirder...

Tim in Phoenix · Joined: 21 Oct 2006 Posts: 4409 Location: Phoenix

Sooooo

Is this thing fixed or whut?

.

**Curt Palme** · Posted: Mon Apr 01, 2013 1:55 am Post subject:

Dunno yet. I sent him a new CLM last week that I've run here for days and days, with and without Craigs programming. Worked flawlessly. We'll see if it works in his set.

mp20748 · Posted: Mon Apr 08, 2013 11:53 am Post subject:

Went out there yesterday loaded with a back plane board and mother board prepared to tear the projector down on the ceiling and replace these parts. But before doing so I told Jeff that I would spend about an hour on it before tearing it down to make sure I'll not have the same problem after hours and hours required to literally disassemble the projector while still on the ceiling.

Started out by asking for a Sony Blu Ray to be loaded to look at a few test patterns on the disk.

After loading the disk and looking at one of the test patterns, I saw what I was looking for. there was a bunch of moving and flashing dots in the image. I then told Jeff, those dots are what's causing the problem.

I then gave thought to where and how that interference could get into the projector. I started with the IR sensor to later move to removing the Moome card.

After removing the Moome card, the remote worked and all was fine.. Very Happy

I've had this same problem before years back in several commercial installs, when the remote would not work, and the problem was related to external interference. I've seen this caused from the IR sensor picking up trash data in or near some technical environment, that the fix for this problem was to remove and/or disable the IR sensor and use the hard wired or external wired (plug into the CLM) remote.

The CPU on the CLM will shut down further control of the CPU when it receives trash or garbled data. It does that to prevent trash data from allowing the CPU to wrongfully enable any control feature of CPU. The turn on/off part of the CLM is done using the sub or standby CPU function.

So the problem is now solved. The Moome card is now violating FCC Rule part 15 - that is when a CPU device somehow transmits its computing data beyond its build area. I took an FCC compliance class on this.