In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Zoot wrote: The Inkjet Board documentation is separate: [url]http://parallax.com/Portals/0/Downloads/docs/prod/robo/InkjetKitDocs-v1.0.pdf[/url], but it does include pin assignments for the serial header, etc. The serial is TTL -- since it goes to a pin on the SX on the board. The board has it's own voltage reg for 5v and for the charge pump for the higher voltage print head. It's an LDO reg. on the 5v side, so it works OK with 5v in, but I usually use 6v and I get more reliable printing. There are definitely some inconsistencies between the documentation, the inkjet book by Gilliand and the actual delivered board. For one, Gilliand's book mentions in passing that there is more than one font pre-loaded on the board EEPROM -- this is not the case (at least it wasn't for the two boards I received). Indeed, in my tests, the entire upper half of the font set was blank (chars $80-$FF). Another is that some of the remarks refer to a 32 byte text buffer, some to a 64-byte buffer (the pre-loaded SXB driver indeed is a 64 byte buffer). I've got a slightly revised version of the SXB driver -- I've been trying to find some time to post it -- basically it allows for higher baud rate, letting the host (optionally) sample the serial line as "busy" signal, etc. Plus I created most of the characters in the "enhanced" font set (the bolder font that uses all dots top to bottom for larger, bolder letters). I have the latter as a .bs2 program that downloads the enhanced font to chars $80-$FF so that setting bit7 of any sent char will get you bold, clearing bit7 of any char gives you the pre-installed "utility" font. I'll try to get those posted sometime today or tomorrow. ---------- End of Message ---------- You can view the post on-line at: http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=254803#m255335 Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2008 (http://www.dotNetBB.com)