Zebra LP2844 will not print EPL2 commands ( Page mode ), only EPL1 ( Line mode) works - zebra-printers

I have an LP2844 that seems to take a print job just fine, but ignores it, I don't get any errors, and no change to the LED on the printer to indicate that it got the message.
The diagnostic prints out when I hold the button down at start up, so I knew the print head and things worked.
I managed to find that you could use the button to switch the printer to EPL1/Line Mode, and when I did that, all the text I send to it prints out, but none of the drivers are written for this anymore.
So I know the print head works, the USB cable works, and so on, because I can print in line mode, but when I switch it back to Page mode, it stops responding to commands.
I tried to do a factory reset as described on Zebra website, but when I hold down the feed button, it just keeps feeding, and never does the blinking that is described there.
Has anyone seen anything like this.


What you're experiecing looks like an issue with the EPL syntax.
Does the led blinks when you send the data and have you also checked if the EPL syntax is correct?
Have you tried to use zebradesigner to create and print a label?

Related

Resetting GRBL command not working in arduino IDE serial monitor

I am testing Grbl CNC Shield with my Arduino Uno. Everything is working except for the ctrl-x command. I tried on the Arduino IDE serial monitor but it appears that it dont recognize.
Does anyone how to solve this?
Any help would be appreciated.
I Tried:
Holding Ctrl with x and nothing happend.
sending ^X or ^x but the console responded "Error: Excepted command Letter"
sending 0x18 on the console and it responded "Error: Bad Number Format"
When the reset command is triggered and it's in the Alarm lock it should reset the grbl and show that message again. This would happen too if the grbl is running normally

cnc_ard = serial.Serial('COM11',115200)
y= "\n" #(ctrl-x)
cnc_ard.write(y.encode())
Here is what I did with Python. Open cmd from there just press ctrl + x. It will come there^X. After entering it will show there . From there copy this inside note+. It will come there "CAN" like this. Copy that and enter this in Serial monitor. Please check these pictures attached below.

in python the comand 0x18 is b'\x18'

Just one chance for a debugger session

In my application, I can debug one time ! I change some lines in a "file".js.You can see what I get on the screen during my first debug session in this first copy screen.
and the second time....I receive a completely white screen...
I must precise that I don't receive the same comportement if I try the tutorial SuperHero !

I've seen this too and it seems to be a bug. Before running the code again, make sure you close the Debugger tab in the left side panel. If that tab is left open after debugging, subsequent debugging produces a blank code area.

close all debugger tabs from the studio (including the one that shows current paused threads) and open the following URL in your browser : http://127.0.0.1:8080/debugger
There is an issue currently being processed about the subject : https://github.com/Wakanda/wakanda-issues/issues/216

PyCharm: can't get input() from keyboard while debugging / stepping through

I can't figure out how to input from my keyboard while debugging the program. The only place I can write something is on 'Console', but when I do, a message pop ups saying "Pause the process to use comand-line".
It's been hours, I couldn't find a solution to this. Thanks in advance.
When running the program all works fine, I can write the input normally.
But when debugging, I get stuck when program reaches "input()" line.

Here's link that should solve your problem. The issue is that your debugger is defaulting to the python console.
PyCharm: How to debug `raw_input()` input from keyboard?

MICR Check Printing not working on Windows-7

I maintain a PowerBuilder Classic 12.5 application which has functionality to print checks on a Source Technologies MICR printer. The application has been running fine in a Windows XP environment. We are trying to move to a Windows-7 operating system and the check printing no longer works.
Here is the issue. PowerBuilder issues a PrintOpen followed by several Print commands to send command strings to the printer to unlock MICR mode and various secure fonts:
il_job = PrintOpen( )
Print(il_job,'&%STF[password]$')
Print(il_job,'&%SMCPFFFF$')
Print(il_job,'&%STP10003$')
Print(il_job,'&%STP10002$')
Print(il_job,'&%STP10001$')
Print(il_job,'&%1B$&u600D')
Print(il_job,'&%1B$*t600R')
This works fine on XP, and if you redirect the printer to "print to file", you can see the command strings right there in the file.
In Windows-7, the printer does not recognize the command strings, and in fact, just prints the commands on the check stock. If you do the same "print to file", you can see the commands in there, but each character in the command string is separated by other characters.
The following is a sample taken from the "print to" file, and you can see the string '&%SMCPFFFF$' by looking at each character that precedes an asterisk (*).
*p171Y&*p50X%*p100XS*p150XM*p200XC*p250XP*p300XF*p350XF*p400XF*p450XF*p500X$
This would seem to be a print driver issue, and in fact, Source Technologies now provides a "Universal Print Driver" which we have been told to use. Our PC support person was able to get the check printing working temporarily by re-installing the old print driver that we used on Windows XP, but as soon as the printer is turned off and on again, it resets to the new universal driver.
I tried using PrintDefineFont and PrintSetFont, to set the font to Courier Regular 8pt (which is what the Tech Support guy at Source Technologies told us we needed), but that didn't help:
PrintDefineFont(il_job, 1, "Courier", -8, 400, Fixed!, AnyFont!, FALSE, FALSE)
PrintSetFont(il_job, 1)
Can anyone help me with this issue? Or suggest where I might get help.
Thanks.

Try this: Add a new printer. Select the port your printer is connected to. Select Manufacturer: Generic, Printer: Generic/Text only. When you print to this printer it should send exactly what's in your Print statements to the printer.

Thanks Hugh, I tried your suggestion which sounded good, but unfortunately it had no effect.
As it happens, as of yesterday I did resolve the last of the printing issues. I had to address each of the special fonts (micr line, signature, check amount etc.) individually, and used a combination of using PrintDefineFont/PrintSetFont, embedded printer command strings to reset the font, and changing a Column control in the datawindow to a Text control (a printer command string is moved into this field as well as the data, and the one worked, the other didn't).
Appreciate your help.
Les

Please right click on your software and go to compatibility mode and select "Windows XP with SP3" in it, click APPLY and OK.
Confirm if the software now send print commands perfectly?

How to find source of print() or NSLog() console output in Xcode

I'm not sure if this is possible. Here is an example situation:
Something is printing to my console and I don't know where it is coming from in the code. I did a quick search using the Finder in Xcode on terms such as 'NSLog' and 'print'. Nothing relevant came up.
Is there any quick way that Xcode has of finding where the source of the output is coming from ?
Kind of like when you right click on a method and you have all the options of exploring different parts of the code associated with that method.
Also: are there other functions that print besides NSLog and print?
Thanks so much!

Try running in the debugger, with breakpoints set on printf, NSLog, etc. When you hit a breakpoint do a backtrace (bt) to see where it's being called from

There's a plugin LinkedLog for that. You replace all NSLogs with LLogs and then will be able to just tap on link in Xcode's console to get to the line caused it to appear.
Didn't try it myself, but definitely will.

Resources