anyone know how to control the serial inkjet printer using hyperterminal? thank
lesbleus
Posts: 9
Hi all,
I am using a 96 dpi·Serial Inkjet Printer Development Kit to test the printing.
i'd like to use hyperterminal to control the printing function through USB.
i have correctly installed the FTDI driver.·When i start the hyperterminal program and set it up, I·found that· there is any reponse from the·printing kit. I really don't know·what's the problem.
could anyone·kindly give me some suggestions or advice?
Thanks so much.
george
I am using a 96 dpi·Serial Inkjet Printer Development Kit to test the printing.
i'd like to use hyperterminal to control the printing function through USB.
i have correctly installed the FTDI driver.·When i start the hyperterminal program and set it up, I·found that· there is any reponse from the·printing kit. I really don't know·what's the problem.
could anyone·kindly give me some suggestions or advice?
Thanks so much.
george
Comments
What are you sending with hyperterminal ?
Have you tried the LED display (remember to remove the ink cartridge!).
We need more information...
Bean.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
www.iElectronicDesigns.com
·
As for the power supply of the inkjet board, I am using the the USB port of PC for powering the board because the USB port can suppy 5V which is the same as that described as in the instruction. A USB to RS232 wire is then used to connect the inkjet board to the usb port. I suspect that it's correct.
As said in the instructions for "96 dpi Serial Inkjet Printer Development Kit (#27949)", the screen of the hyperterminal will display the prompt character ">" when the kit is ready to accept data. But I didn't see this character.
Then I tried to send <STX>HELLO<ETX> commands to the kit. There is not any response from the kit.
i tried also the LED display. it seems that i still didn't the prompt character ">". i am wondering if I need additional power supply.
Thanks again, bean.
George
P.S. the instruction of the kit [noparse]:http:[/noparse]//www.parallax.com/dl/docs/prod/robo/InkjetKitDocs-v1.0.pdf
· Why not just use the USB on the printer driver board ? You'll probably need either another USB or a 5V supply to power it.
· Set the USB virtual com port to 9600 baud 8 data bits, 1 stop bit, no parity.·You should receive the ">" prompt everytime you press ENTER in hyperterminal.
Bean.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
www.iElectronicDesigns.com
Post Edited (Bean (Hitt Consulting)) : 1/11/2008 3:03:37 PM GMT
George.
Have you any luck using Hyperterminal to drive the serial inkjet board? I am about ready to do the same. The literature in the kit (and the book) detail how to use the board and the BSII but not much detail on using just USB and Hyperterminal. Any advice on hooking this up would be greatly appreciated.
Thanks, Dan
Luckily I sorted out this problem thanks to bean's suggestion.
I just made a 5-volt power supply for the circuit board and my PC can recognize it with hyperterminal. Good luck.
Now I am trying to use this printing kit to do some printing, but I doesn't work. It seems that I need to download the font map into the EEPROM of the board. Probably you'll also need to test it. If it works for you, could you please tell me how you do it.
Thanks.
George
I just reconfigured my COM1 buffers according to the above information last night. I have not tested them. I have not used Hyperterminal for years as it seemed so counter-intuitive for my needs. I was using Terminal when I needed RS-232 and that is what I used with the Serial Inkjet Printer board.
Additionally, my Serial Inkjet Printer board is put away. I haven't done anything with it either for quite a while. I just happen to have the reference text in my bookshelf, so I responded with what worked for me.
As it stands, I'm involved in different projects -- so I don't really want to spend much time seeing if I can get Hyperterminal to really work. The last time I did a Hyperterminal Loop Back test, it worked fine with maximum buffers. But, I couldn't get it to communicate with whatever I was trying to do. Changing the buffers may be the secret as the Command Line output commands are less than 12 bytes long. At maximum buffers [noparse][[/noparse]12 bytes], they may just be sitting in a FIFO and waiting to be pushed out.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
PLEASE CONSIDER the following:
Do you want a quickly operational black box solution or the knowledge included therein?······