Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Sending control codes to a printer

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Sending control codes to a printer

    Has anyone had success in sending control codes to a USB printer either directly through XBASIC
    or perhaps through an XBASIC driven command window action?

    Specifically, I need to send the following string of hex codes to an Epson receipt printer:

    1B 70 00 32 F9

    This will cause the printer to send the signal to open a cash drawer.

    Thank you.

    Gene
    [email protected]

    #2
    Re: Sending control codes to a printer

    Do an Advanced Search on this message board. Search term "cash drawer" (with the quotes)


    Asked and answered fairly often.
    There can be only one.

    Comment


      #3
      Re: Sending control codes to a printer

      Thank you very much Stan.

      Gene

      Comment


        #4
        Re: Sending control codes to a printer

        Looking at all the chatter regarding opening cash drawers seems to indicate that the real issue/need is not understood. The real need has to do with not having to open the drawer with every printing as can certainly be done by setting the printer parameters but rather being able to trigger an opening as needed. The receipt is not the only thing that a user would like to print. Opening the drawer with all other kinds of "reports" is unnecessary.

        Perhaps this can be tackled in smaller steps?

        How would one send a carriage return to the receipt printer via a USB connection from xBasic? Once sending a CHR$(13) down the line is accomplished perhaps we can expand upon that to send a hex code string?

        Anyone?

        Gene FitzPatrick

        Comment


          #5
          Re: Sending control codes to a printer

          my okidata is on NE004 if I am noit mistaken - if it helps you

          Alpha 4 could do this easily. it had most of the codes included for popular printers at the time. It is one of the features that never came over that I saw.
          Dave Mason
          [email protected]
          Skype is dave.mason46

          Comment


            #6
            Re: Sending control codes to a printer

            How would one send a carriage return to the receipt printer via a USB connection from xBasic? Once sending a CHR$(13) down the line is accomplished perhaps we can expand upon that to send a hex code string?
            while i have not tried this yet ( hoping to play with this concept this weekend)
            if you are able to write a short program in a language you are familiar and compile that one, and if that one sends the CHR$(13) successfully via the usb connection to the printer then you could call that short program
            sys_shell("c:your_program_directory\your_program_name") and alpha will execute that program.
            if you succeed then rest will be history.

            remember i have not done this yet.
            thanks for reading

            gandhi

            version 11 3381 - 4096
            mysql backend
            http://www.alphawebprogramming.blogspot.com
            [email protected]
            Skype:[email protected]
            1 914 924 5171

            Comment


              #7
              Re: Sending control codes to a printer

              Thank you Gandhi

              This seems to be a strong enough need for the A5 crew to consider adding don't you think?

              Good luck this weekend and please let us all know how it goes for you.

              Gene

              Comment


                #8
                Re: Sending control codes to a printer

                Thanks Dave.

                My vote is in to request the Alpha crew add the ability to send control codes to printers via USB!

                How about you?

                Gene

                Comment


                  #9
                  Re: Sending control codes to a printer

                  Somewhere in the code archive or a thread here is a downloadable exe written by Jim Chapman that will send printer codes, but only to lpt and com ports.

                  In php, these were taken care of around 2004 +- with some serious code where you could actually find and use the printer name.

                  I have not run across the code in java script(haven't looked for it).

                  I believe the code is there in powerbasic, where somebody wrote it and donated. That would be a dos app(I think), but could be called from alpha.( they have windows and dos tools there).
                  Dave Mason
                  [email protected]
                  Skype is dave.mason46

                  Comment


                    #10
                    Re: Sending control codes to a printer

                    This is not perfect, but it does work for me. It might not work for a softprinter (ie. printer with no built in intelligence that relies on the host to do all of its processing).


                    To print directly to a USB (or any) printer first share the printer.

                    Then create a new file to the UNC path of the printer.

                    Finally, write to the file like you normally would any other file.

                    An example:
                    \\jacob-pc is the host computer
                    p is the printer share
                    the UNC path is \\jacob-pc\p

                    Code:
                    dim file_pointer as P
                    dim text as C
                    
                    file_pointer = file.create("\\jacob-pc\p", FILE_RW_SHARED)
                    
                    text="this is a test" + chr(13) + chr(10) + "hi ho" + chr(8) + "e" + chr(11)
                    
                    file_pointer.write(text)
                    
                    file_pointer.close()
                    There are some control codes to test if it is working, if it is working you should see:
                    Code:
                    This is a test
                    hi he
                    Last edited by jacobe; 06-07-2013, 02:15 PM.

                    Comment


                      #11
                      Re: Sending control codes to a printer

                      Nice Jacob.

                      For my HP this outputs your text and ejects the page.

                      Code:
                      dim file_pointer as P
                      dim text as C
                      file_pointer = file.create("\\ACNIELSEN\HPLaserJ", FILE_RW_SHARED)
                      text="this is a test" + chr(13) + chr(10) + "hi ho" + chr(8) + "e" + chr(11)
                      file_pointer.write(text)
                      text=chr(027)+chr(038)+chr(108)+chr(048)+chr(072)+ chr(40)+chr(104)+chr(41)
                      file_pointer.write(text)
                      file_pointer.flush()
                      file_pointer.close()
                      There can be only one.

                      Comment


                        #12
                        Re: Sending control codes to a printer

                        This did work for me.

                        sys_shell("c:\sendstr.exe 2 27 112 00 100 250",2)
                        sys_shell("c:\sendstr.exe 1 27 112 00 100 250",2)

                        Comment


                          #13
                          Re: Sending control codes to a printer

                          The code you refer to is Jim Chapman's sendstr.exe. Like you said that does not work with USB printers.

                          Comment


                            #14
                            Re: Sending control codes to a printer

                            This works well Jacob. Thank you.

                            Do you know the format to allow the sending of HEX codes to the printer?

                            Thanks,

                            Gene

                            Comment


                              #15
                              Re: Sending control codes to a printer

                              Probably

                              text= chr(hex_to_dec("1B"))+chr(hex_to_dec("70"))+chr(hex_to_dec("00"))+chr(hex_to_dec("32"))+chr(hex_to_dec("F9"))
                              There can be only one.

                              Comment

                              Working...
                              X