Maybe all you want then is just:
Serin PrgIn,1,5000,MainLoop, ProgIDRx
?
Troy
Type: Posts; User: rocket_troy; Keyword(s):
Maybe all you want then is just:
Serin PrgIn,1,5000,MainLoop, ProgIDRx
?
Troy
Yes, I'm aware you declare it, but you don't assign anything to it. It's there as a newly declared variable with the contents of null. So, I'm guessing serin is waiting for a null character to arrive...
Well, that's what I'm confused about. Don't you need to actually nominate something as the qualifier rather than an empty variable?
p207 of the manual:
"list of data items to be received may be...
Then, don't you need to nominate the qualifier as being something? like:
Serin PrgIn,1,5000,PassProg,["ABC"],IDByteRx ' Wait for 5 seconds for "ABC" to arrive then put contents in IDByteRx?
Troy
I don't really use serin so I can't be of much help, but just to educate me: isn't the contents inside the square brackets a qualifier or filter - like the WAIT modifier in serin2?
Troy
Ioannis, I owe a you a beer or 3 :) My voltage reg was underrated to that required 3.5A. I got away with it for the 2W modules, but not these. I never would've thought of that being the culprit for...
Okay, that's something that could be an issue. I normally run a 2W transceiver on this system and I remember checking battery and voltage reg to ensure capability there; but I have to fess, it's one...
It's just weird that I'm only transmitting at 9600 baud, and the same thing happens no matter how long the 1st string is. Only happens with that transceiver module, none of the other models from the...
Okay, interesting. So that small delay might be triggering the RF transceiver to interpret the end of the packet. I'm running an 8mhz clock on a PIC18F26K83 so there is scope to play with clock...
Hi Ioannis,
The problem isn't with the validity of the code, it's more to do with... well... the combination of the transceiver and the way PBP sends the packet. So, for a statement like that:
...
Is there any switch/setting that can send everything in a serout2 command in the 1 complete packet?
eg
MyValue = 100
serout2 PORTB.1, 84, ["This is my value:", dec MyValue, 13,10]
can be sent...
Can anyone confirm that Darrel Taylor's NBit math routines are all *un*signed? ie. if I had negative numbers, I'm restricted to PBP's longs for processing?
Also, is there any way of converting a...
Definitely resolved for me. Gone from never getting through at all to (now) getting through every time.
Troy
I've just got through today AND for my 1st attempt :) This is the 1st time I've managed to get through for months.
Troy
I get exactly the same thing. I've just accepted that it might take 20-30 attempts to open the forum page. It's been happening for a long time and only happens with this site. I'm also using Chrome. ...
Thanks Richard, that clears that up. No biggy anyway.
edit: actually the one working fine was 18x24 (I was mixing up the width & height)
Troy
Okay, so fixed widths can have a wider limitation?
Troy
Hi Richard,
Finished up giving up on the serial connection as it was just a bit flaky ie. characters and graphics didn't always display cleanly etc. That might've been a wiring issue - not sure....
Cool, so assuming that fixes the FillRect (I'll find out this evening) everything should be dandy.
Troy
Another Question:
In your graphics file for the FillRect code you have:
frect:
s_ystart=y0
s_yend=y0
while y1
s_xstart=x0
Richard,
Curious Question:
I was feeding a 10bit rotary encoder into the PIC (RB0-RB5 & RA0-RA3) with the display connected and I was stumped to figure out why I wasn't getting any input signal...
Worked! I can now run things on the smaller package.
Legend!
Troy
Power supply going into the PIC was a PicKit2 and that doesn't appear to be the issue. I was doing all these tests on a 18F26K22 SOIC package. After you mentioned the power requirements issues, I...
I have a few 18F26K83s that I've used for various projects. Worth trying one of these? They can source/sink twice the current on each pin apparently.
Scrub that... Different architecture
Troy
There's one other thing I haven't done which might be required. I haven't pulled up the I2C clock or data lines with weak pull up resistors. Because the static display code appeared to be working...