Serin serout problem

[lerameur]

ok eee, seems to be working now, am I awake....
thank you thank you
i will try the wireless

what is this line for (was for , or intended to)
'templo = converts[templo] : temphi = converts[temphi]

[skimask]

ok eee, seems to be working now, am I awake....
thank you thank you
i will try the wireless

what is this line for (was for , or intended to)
'templo = converts[templo] : temphi = converts[temphi]

Well, what program are you running right now? I changed some stuff and was about to post it...but if you say it's working correctly at both ends, then I'll go with that.... So, repost the program you're running now (if it works), so I can remember what the line above did.

[lerameur]

using post 118

it works wireless,
does it have to do with the encoding technique ?
but most often its showing good temp.

[lerameur]

could I add a 10v voltage regulator for the RF transmitter to boost up the signal ? I am using the rentron 433mhz chips tws

[skimask]

could I add a 10v voltage regulator for the RF transmitter to boost up the signal ? I am using the rentron 433mhz chips tws

If you're running the module at 5v now, you're good for about 500ft (that's what I've gotten at 9600 a few times, a few errors, but it still worked). and if you read the datasheet, you'll see that you have to run your data input line to the TX module at the same voltage range as your power input.

I've ran that TX module at 2.5v before and gotten 100ft without troubles.

[skimask]

using post 118

it works wireless, I get a lot glitches meaning temperature showing weird numbers like 930 , 445, etc.. it stays at those odd numbers for 3-5 seconds sometimes,
does it have to do with the encoding technique ?
but most often its showing good temp.

Glitches - Probably has to do with the encoding technique because the data isn't encoded (I commented that part out in post #118), but the 'training' bytes are encoded.

Maybe try to add a few more $55 to the serout line in the transmit section. And make sure the char_pacing isn't in the define sections anymore.

[lerameur]

I di dwhat you told me removing the char_spac adding more $55, its worst now,
its constantly showing 360, 445, and sometime the temperature
more often 445

[skimask]

I di dwhat you told me removing the char_spac adding more $55, its worst now,
its constantly showing 360, 445, and sometime the temperature
more often 445

Well, I would think that taking out the char_pacing and adding $55 would help it, but apparently not since none of the data is being encoded, the receiver is picking the $55 up as actual data or something.
Try it the other way around, but do one thing at a time.
1) No char_pacing - a single $55, no $55 (which should not work!)
2) no char_pacing - two $55's
3) no char_pacing - 4 $55's
4) small char_pacing - single $55 (I would think that any char_pacing value above 4000 would mess things up bad enough not to work at all)
....
....
etc.
See which one works out the best...
OR....
you could add you manchester encoding routine back into the program (from way back when, ya know, page 1!!!) and see what happens.

[lerameur]

I added DEFINE CHAR_PACING 2000
also 1000 works good with four $55
But it seems to be long to change the temperature, sometime the receiver seems to hang there with its value.