Shop OBEX P1 Docs P2 Docs Learn Events
Display problems again — Parallax Forums

Display problems again

ArchiverArchiver Posts: 46,084
edited 2003-02-05 13:51 in General Discussion
Hi,
I've posted a question (see number 28672) About a display connected
to a BS2p40, they suggested to change my program code, which I did,
and the problem wasn't solved, I still see weird stuff on te display
(all characters exist, just it's not what I would like to see)

Thanks

Hans


'{$STAMP BS2p}
n9600 con 16468
I con 254
CLR con 13
L1 con 128
L2 con 192

pause 1000
serout 0, n9600, [noparse][[/noparse]I, CLR]
pause 1000
serout 0, n9600, [noparse][[/noparse]L1, "Message 1"]
pause 1000
serout 0, n9600, [noparse][[/noparse]L2, "Message 2"]

Comments

  • ArchiverArchiver Posts: 46,084
    edited 2003-02-04 22:53
    In a message dated 02/04/2003 17:48:02 Eastern Standard Time,
    herrhanz@y... writes:


    > I've posted a question (see number 28672) About a display connected
    > to a BS2p40, they suggested to change my program code, which I did,
    > and the problem wasn't solved, I still see weird stuff on te display
    > (all characters exist, just it's not what I would like to see)
    >
    >

    Hans, I didn't realize you were using the P40. Change

    N9600 to 16624 or $FOFO

    Sid


    [noparse][[/noparse]Non-text portions of this message have been removed]
  • ArchiverArchiver Posts: 46,084
    edited 2003-02-05 05:35
    Hans-

    1. 9600 non-inverted on the BS2p requires baud value 16624.

    2. If your program really ends as you have shown, your program
    enters the END state and the serial output line will glitch every
    couple of seconds (see END or SLEEP in the manual for more details).
    This may cause spurious data to be received by the display. Try a
    last line like:

    STOP

    or:

    here:
    GOTO here

    Either one will cause your outputs to remain driven as last set.

    Regards,

    Steve


    On 4 Feb 03 at 22:46, herrhanz herrhanz@y... wrote:

    > Hi,
    > I've posted a question (see number 28672) About a display connected
    > to a BS2p40, they suggested to change my program code, which I did,
    > and the problem wasn't solved, I still see weird stuff on te display
    > (all characters exist, just it's not what I would like to see)
    >
    > Thanks
    >
    > Hans
    >
    >
    > '{$STAMP BS2p}
    > n9600 con 16468
    > I con 254
    > CLR con 13
    > L1 con 128
    > L2 con 192
    >
    > pause 1000
    > serout 0, n9600, [noparse][[/noparse]I, CLR]
    > pause 1000
    > serout 0, n9600, [noparse][[/noparse]L1, "Message 1"]
    > pause 1000
    > serout 0, n9600, [noparse][[/noparse]L2, "Message 2"]
    >
  • ArchiverArchiver Posts: 46,084
    edited 2003-02-05 13:33
    On 5 Feb 03 at 8:51, Newzed@a... wrote:

    > In a message dated 02/05/2003 01:37:15 Eastern Standard Time,
    > parkiss@e... writes:
    >
    >
    > > 1. 9600 non-inverted on the BS2p requires baud value 16624.
    > >
    >
    > Steve, 16624 is inverted.
    >
    > Sid

    Sid-

    You're right, my mistake. It's probably the correct baud value for
    Hans, but I did refer to it by the wrong designation. Regret any
    resultant confusion.

    Regards,

    Steve
  • ArchiverArchiver Posts: 46,084
    edited 2003-02-05 13:51
    In a message dated 02/05/2003 01:37:15 Eastern Standard Time,
    parkiss@e... writes:


    > 1. 9600 non-inverted on the BS2p requires baud value 16624.
    >

    Steve, 16624 is inverted.

    Sid


    [noparse][[/noparse]Non-text portions of this message have been removed]
Sign In or Register to comment.