In another thread I promoted using serial LCD displays instead of cluttering up pins and code:
Hippy's reply to the second link seemed to refute the notion of SEROUT and HSEROUT problems:
Since I use SEROUT a lot I'm interested in what others have to say about this.
Another forum member begged to differ:If you need to save pins (and/or code space) use serial displays like the AXE133Y instead of driving the display with your project Picaxe.
If you need more pins, use a PICAXE-40X2. Serial LCDscanwill cause problems with interrupts, timers, servos, background i2c, background hardware serial and others so it's best to avoid them if there is the possibility that one of those will be needed or they are needed.
I'm still puzzled:Using the serout command to control the LCD will disable all interrupts and cause problems with any interrupt-based things like background hardware i2c slave mode, timers and background hardware serial.
I have never experienced any of these problems even though I have used timers and the DS1307 via i2c extensively with serial for LCD and data logging to SD cards. I don't want to drag this thread off course so your insistence should quickly provide proof via a code sample, reference to documentation or relevant forum posts. Failing that this discussion needs to move to another thread.
The first link seems to be about SERTXD. While handy for debugging I can't imagine running an LCD that way.Good idea - some relevant forum threads:
Hippy's reply to the second link seemed to refute the notion of SEROUT and HSEROUT problems:
Both of these work for me. Run for 1000 PICAXE 'time' seconds (16:40) results were as follows -
SEROUT : 1007 real seconds, approx 0.7% accuracy
HSEROUT : 999 real seconds, approx 0.1% accuracy
Since I use SEROUT a lot I'm interested in what others have to say about this.