it's only because you can't redefine the DEBUG settings. Use SEROUT, SEROUT2 instead
it's only because you can't redefine the DEBUG settings. Use SEROUT, SEROUT2 instead
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
droptail, the second instance is the only one that gets compiled as the first instance gets re-defined at compile time. The way PBP works is that you can only have 1 defined set of DEBUG parameters. That is why the second set of instructions works and not the first.
Dave Purola,
N8NTA
I see. I had worked on SERIN/OUT for a few days and couldn't get it to work. It is working now. Need I pause between these statements or just run them together. There seems to be a long time to go from master PIC to slave then to display on an LCD.
master:
SerOut2 PORTA.0,N2400,["A",w2]
SerOut2 PORTB.6,N2400,["A",w2]
SerOut2 PORTB.7,N2400,["A",w2]
slave:
SerIn2 PORTB.0,N2400,[wait ("A"),w2]
Gosub LCD
SerOut PORTA.3,N2400,[12,27,"F",65,#w3," ",#w2]
One other thing, what is compile timeout (ver 2.40)?
James
droptail, I am unfamiliar with the term "compiler timeout". What do you mean?
If you are talking about the time that is required for the compile process it varies depending on the size of the program. The longer the program the longer the compile process.
Dave Purola,
N8NTA
i guess it's the SERIN timeout.
Here's a quote of the PBP manual
An optional Timeout and Label may be included to allow the program to continue if a character is not received within a certain amount of time. Timeout is specified in units of 1 millisecond.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Its a PBP window that pops up after programming 6 - 10 times, and won't compile, just says "compiler timeout..." as if its waiting for something, long after the normal few secs it takes to compile. I close the file or program and re-pull it up to continue working.
James
Bookmarks