Mimicking BS2 DEBUG with Propeller

AwesomeCronkAwesomeCronk Posts: 494
edited 2018-08-15 - 18:34:14 in General Discussion
Hello, I am looking to debug to MakerPlot with the Propeller(p1, that is). MakerPlot communicates with a BS2 via DEBUG, just like the PBASIC Editor's DEBUG window. How can this be mimicked using the Propeller?
Cows say “moo”, right? Well Greek cows say “μ”


  • The BS2's DEBUG statement is just a SEROUT statement that accesses a "virtual" I/O pin #16 and has a fixed Baud ... 9600 I believe for the BS2, 19200 for the BS2px. Look at the Basic Stamp Syntax and Reference Manual chapter on the DEBUG statement.

    You can use any of the Propeller serial I/O drivers to mimic this. Keep in mind that the Propeller's I/O pins are 3.3V logic levels while the Stamp I/O pins are 5V logic levels. MakerPlot runs on a PC and would need a USB to serial adapter for Stamp use. You'd just use a 3.3V USB to serial adapter for the Propeller ... like the ones built into most Propeller boards.
  • Thank you, Mike. What I gather is that I can just use a driver for the Parallax Serial LCDs and set it to use p30 or p31 as Tx(cannot remember which). Correct?
    Cows say “moo”, right? Well Greek cows say “μ”
  • Hold up, how will the FTDI driver chip on the PropBOE affect this?
    Cows say “moo”, right? Well Greek cows say “μ”
  • It won't. Connect your serial object (usually FullDuplexSerial) to pins 31 (RX) and 30 (TX) and the desired baud rate. You can't send compound output in a single line, but you'll be able to do anything you need to do.
    Jon McPhalen
    Hollywood, CA
    It's Jon or JonnyMac -- please do not call me Jonny.
  • AwesomeCronkAwesomeCronk Posts: 494
    edited 2018-08-15 - 20:59:55
    Thank you JonnyMac! I will begin putting together a .spin object to test a MakerPlot connection soon!
    Any idea on how to mimic "DEBUG CR"? This piece is critical to separate data entries.
    Cows say “moo”, right? Well Greek cows say “μ”
  • pst.newline
    Re-inventing the wheel is not a waste of time if, when you are done, you understand why it is round.
  • DEBUG CR just sends a single carriage return character as if you had written SEROUT pin,...,[CR] with "..." being the appropriate stuff for SEROUT.

    Use ser.tx(ser#CR) in Spin assuming you declare your FullDuplexSerial object as ser. Notice that FullDuplexSerial has constants for all of the special characters normally used with SEROUT or DEBUG.

Sign In or Register to comment.