Printrun icon indicating copy to clipboard operation
Printrun copied to clipboard
verified publisher icon kliment

echo:busy: processing

Open nomeursie opened this issue 5 years ago • 7 comments

Hello,

When i connect my ender 3 to pronterface and do autohome , i get not information from my printer it say echo:busy: processing I have bltouch from antclabs on my ender 3. Can you tell what the problem is. Best Regards Henk v Meurs

nomeursie avatar Nov 27 '20 13:11 nomeursie

Hi @nomeursie sorry for the late response. Were you able to connect? If not, could you please tell us what operating system are you using? What version of Printrun? I'm assuming you run the pronterface app and not the console app, do any other messages come up on the messages area?

rockstorm101 avatar Dec 12 '20 17:12 rockstorm101

I'm not the original poster, but I'm having the same issue. When I click to auto home, I get Echo:busy: Processing while the printer auto-home. If I try to send a command, I just get "Sending" but it never sends. I'm on windows 10 using an ender 3 with BLTouch and a SKR-Mini E3. Attached a screenshot. Pronterface error

crclardy11 avatar Dec 24 '20 00:12 crclardy11

@crclardy11 , version 1.6 although official is very old. Try rc7 or run from source for the latest updates. Check the "Debug communications" checkbox from the menu and post the log.

volconst avatar Dec 28 '20 18:12 volconst

Hi @crclardy11 / @nomeursie did you try the latest 2.0.0rc7 version?. Does Printrun now work now as expected?

rockstorm101 avatar Jan 31 '21 09:01 rockstorm101

Sorry for not responding. been a busy month. I had no luck with RC7, I haven't had time to go back and mess with it since trying after your suggestion.

crclardy11 avatar Feb 02 '21 15:02 crclardy11

I'm having this problem as well. After homing in pronterface the printer constantly echoes echo:busy:processing Any commands sent don't report back

ItsGoldeneyes avatar May 14 '22 14:05 ItsGoldeneyes

Printrun V1.6 will not run correctly with windows 10. One problem is the usb communication. This is well known.

The actual 2.x RC versions also will not run with all localized Windows 10 versions because of the locale wxAssertionError. This problem was solved last year with the developer version of wxPython.

You need a Printrun 2.0 RC compiled with the developer version of wxPython (actual is version 4.1.2a1.dev5310+af8cca51).

Related issues: https://github.com/kliment/Printrun/issues/1230, https://github.com/kliment/Printrun/issues/1208, https://github.com/kliment/Printrun/issues/1170, https://github.com/kliment/Printrun/issues/1174

DivingDuck avatar May 14 '22 16:05 DivingDuck