×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Charles,
Found the hex dump capabilities. For the archives concerning a Zebra
GK420t: turn off device, hold the feed button while turning on device,
release feed button once light turns green (it will turn red and then
amber and then green).
hex dump output:
00 00 00 00 00 00 00 00
00 00 00 00 00 15 5F E7
C1 00 0D 00 15 5F D3 C8
F3 F0 6B F3 F0 00 0D 00
15 5F C8 D8 F2 F0 6B F1
F0 5F C1 C4 5F C8 C4 E9
C5 C2 D9 C1 5F C8 E2 00
0D 00 15 5F C8 D8 F2 F0
6B F6 F0 5F C2 F3 5F C6
C4 C1 C1 C1 F0 F0 F1 5F
C8 E2 00 0D 00 15 5F E7
E9 00 0D 0C 1E 5E 41 1B 58 5A
Screen shot of spool file:
¬XA
¬LH30,30
¬FO20,10¬AD¬FDZEBRA¬FS
¬FO20,60¬B3¬FDAAA001¬FS
¬XZ
As you can see there are a bunch of additional characters being sent
down in addition to the spool file data. If I am not mistaken, the ¬
character is being sent down as a x'5F' (per your other comment), so I
am thinking it is getting sent straight through *without* an EBCDIC to
ASCII conversion.
I am going to look into all of the device creation scenarios I have
done so far and see what conversion options I have (i.e. HPT, etc).
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
On Fri, Jul 23, 2010 at 7:28 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
Aaron,
Did you turn on the hex dump mode at the printer?
What hex characters is it receiving?
Charles
midrange.com
