Hi.
Programming Editor ver 5.1.5, 14M firmware 9.B
How can you make CR and LF be sent on pin2 of the 14M?
The programming editor moans that you can't send variables on any other pin then pin0, which is odd, as you can send CR and LF on any other picaxe on any output pin that supports SEROUT. [F4] results in a correct syntax check, with no problems, yet when you try to program the chip with [F5], you get the following error: Firmware issue means serout of variables can only be used on output0. (Firmware v9.B)
Example:
SEROUT 2,T2400,("Hello.",CR,LF)
This works on the likes of 08, 08M, 18A, 18X etc, etc, but NOT on the 14M.
I made the assumption that it would, and have already produced the PCB(as the exact same syntax works on the other chips), however, only the prototype, so I can change the pattern if it must be done, but I am hoping there is a way around it...
I also tried adding another serout line below the one shown above:
SEROUT 2,T2400,(13,10)
...hoping that I could manually send the decimal CR and LF bytes, but this also produces the same error - most strange.
Any advise?
Programming Editor ver 5.1.5, 14M firmware 9.B
How can you make CR and LF be sent on pin2 of the 14M?
The programming editor moans that you can't send variables on any other pin then pin0, which is odd, as you can send CR and LF on any other picaxe on any output pin that supports SEROUT. [F4] results in a correct syntax check, with no problems, yet when you try to program the chip with [F5], you get the following error: Firmware issue means serout of variables can only be used on output0. (Firmware v9.B)
Example:
SEROUT 2,T2400,("Hello.",CR,LF)
This works on the likes of 08, 08M, 18A, 18X etc, etc, but NOT on the 14M.
I made the assumption that it would, and have already produced the PCB(as the exact same syntax works on the other chips), however, only the prototype, so I can change the pattern if it must be done, but I am hoping there is a way around it...
I also tried adding another serout line below the one shown above:
SEROUT 2,T2400,(13,10)
...hoping that I could manually send the decimal CR and LF bytes, but this also produces the same error - most strange.
Any advise?