understanding the pulse.

[geckogrotto]

Thanks for the help guys hehe, question tho I was reading the voltage with a scope I thought that would give me an accurate voltage?

[mister_e]

well, if the i/o was set as an output, it's impedance become really low (assume a short) hence why the level was as this low.

Now what happen when you read it on a 'input configured' i/o?

and depending what your scope measure... the mean, RMS, peak-to-peak, results will differ

[geckogrotto]

I was measuring it before not connected to anything. Just connected to the ground pin and the probe to the signal pin.

I think I have enough to get me started now tho.

Bit confused about the signal its putting out, looking at the scope I can see what I need to do but using the pulsin data its kinda jumpy.

I have done the standard servos like mentioned above 1-2 ms constant freq but this signal is not a constant freq it seems. On the scope it looks like the width and freq changes.

Standard servo I don't remember the exacts but like 100 to 225 or something that would be the pulse width.
Can you explain what I should be reading on the pulsin when the freq changes?

[mister_e]

and how fast does it change?

will this help to do few reading and do and average... but reject those which are to away of the midpoint...

How about using count... or an internal timer?

what's the most important? the frequency or the duty cycle?

sorry i don't know anything in RC receiver..

[skimask]

I was measuring it before not connected to anything. Just connected to the ground pin and the probe to the signal pin.

I think I have enough to get me started now tho.

Bit confused about the signal its putting out, looking at the scope I can see what I need to do but using the pulsin data its kinda jumpy.

I have done the standard servos like mentioned above 1-2 ms constant freq but this signal is not a constant freq it seems. On the scope it looks like the width and freq changes.

Standard servo I don't remember the exacts but like 100 to 225 or something that would be the pulse width.
Can you explain what I should be reading on the pulsin when the freq changes?

The frequency isn't changing, although it might look like it is changing based on what the rest of the servo's are doing. In other words, say you've got 4 servos...1-3 are all at one end with a pulse width of 1ms and the 4th servo is the one you're playing with. It'll look like one thing on the 'scope. Then if servo's 1-3 go to the other extreme at 2ms, the signal off the 4th servo will look like something else on the 'scope.

It might be a bit jumpy because the input frequency is 'only' 50hz or so, and it's supposed to vary a little bit. Play around with your trigger and 'sweep delay' if you have one on your 'scope. You should be able to get it to smooth out. I've got a Tek 2246A, 4 channel 'scope, I can plug 4 servo's into it at once and be able to see the pulse's on all 4 and they are all steady. But, I have to play with the trigger and sweep delay a bit before they steady out.

[geckogrotto]

skimask, I don't think this is the case.
This isn't a standard servo im working with, When I measure a signal from a standard servo I see what your talking about and it works as expected.

Here is a little pic to help explain I hope.


I don't know how to figure out to read the signal because is moving around unlike the standard servo signal.

Mister_e
Will reply to you in another post

[geckogrotto]

>>and how fast does it change?
Looks like its repeating every 14ms on one end and 6.5 on the other end.

>>will this help to do few reading and do and average... but reject those >>which are to away of the midpoint...

I'm not sure if that would work here

>>How about using count... or an internal timer?
I am not sure how to do that with the signal im getting.

>>what's the most important? the frequency or the duty cycle?
In this case I think its the frequency that matters. But I don't know how to get the freq from picbasic.

[mister_e]

only the duty cycle change, Ton+Toff remain the same. so using Pulsin to read it should work. case not, the internal timer would be perfect...

' just a snip... not the whole thing...
while InputIO=0 : wend ' wait for rising edge
Start timer
Whiel InputIO=1 : wend ' wai for falling edge
stop timer
copy Timer register to a variable
enjoy!

Or use an interrupt to start and stop the timer and dump the results to a variable.

[mister_e]

>>How about using count... or an internal timer?
I am not sure how to do that with the signal im getting.

forget the frequency, from your picture, it's only the dutycycle that change.

>>what's the most important? the frequency or the duty cycle?
In this case I think its the frequency that matters. But I don't know how to get the freq from picbasic.

to get frequency, you could use COUNT, but in your case it should always be the same.

[skimask]

skimask, I don't think this is the case.
This isn't a standard servo im working with, When I measure a signal from a standard servo I see what your talking about and it works as expected.

Here is a little pic to help explain I hope.


I don't know how to figure out to read the signal because is moving around unlike the standard servo signal.

(reference the picture from the earlier post)
That's what my picture on my 'scope looked like when I had the 4 channels plugged in. If the first servo's pulse changed, the rest of the pulses changed with it (i.e. the 2-4 pulses slid back and forth) if I was triggering off Channel 1. and I was using a standard Futaba FM RX for aircraft.

What kind of servo is it? What brand or whatever?

[geckogrotto]

If your look at the pic there are 2 sets of signals.
top 2 are 1 signal(standard futaba)
bottom 2 are the 2nd signal (unknow)

The first 2 are from a standard servo signal. Thats normal futaba whatever.
No matter how long the pulse is the peaks start at a set interval.

The 2nd 2 are from off brand cheapo thing. It if you notice looks different than the top 2 at the same settings. When the low shrinks the pulses get closer.

I'm getting it now tho.