4 replies to this topic

[dvhecke]

Hi all,

 

I am working on a VP cabinet based on the pinscape controller board, which I think is fantastic by the way!

Of course I have no experience with the other systems.... ;-)

All functions on the controller seem to be working but I cannot get the IR remote to work.

When I choose 'learn' on the IR settings screen no codes or raw data comes in.

I tried different remotes, Salora (some kind of whitelabel re-brand), a JVC and a 12 year old Panasonic.

None of these produce any codes in the Pinscape software.

 

The hardware for this IR receiver is so incredibly simple and I used the correct components.

I understand that the TSOP38438 almost never breaks down... So where do I start fixing this problem?

Is it possible that we use a different carrier frequency than 38kHz in Europe? 

 

I will introduce myself shortly with some pictures of my cabinet.

 

With regards, Diederik.

[mjr]

> Is it possible that we use a different carrier frequency than 38kHz in Europe? 

Not that I'm aware of.  Every manufacturer is unique, but as far as I know they don't vary by region, just by manufacturer.  JVC and Panasonic both use the same protocol, with a 37 kHz carrier - which isn't exactly 38 kHz, but it's close enough that the 38 kHz receivers will normally pick it up just fine.

 

Given that you're not seeing any readings with any of the remotes you've tested, I'd guess that you have problem on the receiver end - either a bad chip, or a wiring problem, or something wrong in the software configuration.  I'm afraid I don't have any good tips for troubleshooting.  It's difficult to troubleshoot these things because there isn't a lot you can check.  If you have an oscilloscope, you could look at the signal coming out of the TSOP38238 to at least see if it's showing any signs of life electrically, but other than that I can't suggest any diagnostics.  So I'd just triple-check everything, and if you're absolutely sure everything's right in the wiring and configuration, I'd probably try replacing the TSOP38238 in the hope that it's just a bad chip.

[dvhecke]

Okay, thanks mjr.

I checked the components visually and all seemed fine, so I will replace the TSOP38438.

A new TSOP38238 is on it's way so I'll keep my fingers crossed :-)

[dvhecke]

Sorry for this late reply, I fixed it the next day 

 

Thanks mjr, it was a faulty TSOP. It works like a charm now.

[mjr]

Glad to hear that solved it!