You say that as if i'am not trying too, if you have any ideas to help out speak up, i'am not trying to write a book neither i just want to find a solution.
Your current line of debugging is based on a bunch of assumptions that may or may not be true. As I and several others have mentioned you really need a scope, otherwise we will be up to post 261 and still no further along.
As I previously pointed out, with 4 photodiodes and two emitters I think it is obvious this is not a TV type remote.
Assuming the lows are 6us, then you'd get a frequency in the 1000000/(6+21)= 37037Hz to 1000000/(6+37)= 23255Hz range.
It seems you are trying to demodulate an unknown carrier frequency signal in code by measuring individual pulse lengths of the carrier wave.
I'm not sure that's what the encoding is. You need to find someone with an oscilloscope and take a look at a whole message, not just 100 (50? 150?) oscillations (2100us? 3700us?) worth of the carrier(?) signal.
It's beem mentioned at least a dozen times in the past 162 posts.
1 Like
I know and as i said i'm not the one who buys the material, i can't expect my company to pay something of that price like that, i was trying to find a solution without it, but i get it.
Yeah. It seems the communications channel needs additional redundancy to make it through the filters.
Your right but I think he finally caught on.
I did not mean pay, I meant borrow some time:
Folks who own an oscilloscope are happy to show off how to use it.
I've never heard about it in portugal but i will try to find out something about it.
Hm. Portuguese Electrial Engineers, Hams, Technicians, and hobbyists sound terrible.
True there isn't much available in this country for me to work with, and since i'am still a student i didn't even knew it was possible to borrow oscilloscopes.
Do you have any other Arduinos except for the Uno R4?
What test equipment does your company have?
None, all the equipment i have now is some i though of using and asked the company to buy, but as arduinos aren´t as expensive as an scope i might try talk to my boss to buy another one and use wicope.
The equipment i have is :
The photodiode (BPV22NF)
Amplifier (OPA344PA) and (TL081)
TSOPxx (30kHz, 36kHz, 38kHz)
E12 Series resistors and two potentiometers
Some LEDs
10nF and 100nF capacitors
Cables and a Breadboard
I don't mean borrow the oscilloscope, I mean take your circuit to someone (perhaps an electronics teacher) and ask them your question. I'm sure they will at least show you the details, even if they don't let you operate/touch the oscilloscope.
Folks in my country would love to demonstrate that the expensive gizmos they bought were wise investments and cans solve real problems for real people. You might have to listen to them pontificate on their wisdom for a while, or at worst, it would cost you a cup of coffee. But you could come out of it with the answer to your question about the frequency, a photograph or three of the whole signal, its details, and probably some advice about decoding it.
That would be great and i understood i was supposed to take the system and bring it in, but the problem is that my school isn't in portugal and i know no one in electronics in this country, i will see what i can do, and even if i need to listen to them pontificate on their wisdom i would gladly ear it after taking care of this problem that i have for so long.
I sympathise with you.
It's almost like you are trying to build a nuclear reactor using rubber bands and toothpicks.
And it will be my main grade this year, meanning if i fuck this up i'm kinda fucked for life, im sorry for making so many posts about this i also just want to find a solution to the problem as quickly as possible!!
Is there any arduino that would have an utility as a scope , for instance, using a classic one with wicope would work?
The wicope is suposed to work with an Uno R3 or a classic nano but I only recommended it because I thought you already had an R3. That scope may not be fast enough to capture the signal if it is a modulated carrier but I though if you had an R3 it would be worth trying anyway
1 Like
If you want to do it alone, take a good read of:
..and try some different assumptions about the coding that your code is aimed at.
It could be possible to get a lot of information about the system by filtering the input through debouncing with different time scales and measuring things.
Is your 'bit' tens of microseconds long? hundreds of microseconds long, milliseconds long?
Your current code is aimed at bit lengths measured in microseconds.
1 Like
I will continue reading but i guess i might have found what the transmission is inspired by, the NEC Code, since :
I literally have 22 pulses, plus there is only a single bit if i keep pressing the same key.
Still have doubts about the timers, since my pulses aren't the same kind of this protocol, but it is close tho.