Please note: the forum is closed.
No new user registrations are accepted. For more info, please click here.
No new user registrations are accepted. For more info, please click here.
Anyone have Octoprint running?
Richy_T
Posts: 142๐ Super Member ๐
I look like I'm basically there. I'm just having issues with the comms.
The printer connects fine and it'll be chatting back and forth in the background. It'll do this all day long.
It's when I try and do anything else, it starts hitting timeout errors. For example, trying to do anything with any of the axis...
Hmm. Didn't have that issue with the temperature controls. So maybe it is just G91? I'll try some manual stuff and maybe a print.
The printer connects fine and it'll be chatting back and forth in the background. It'll do this all day long.
Send: M105 Recv: ok T:20.9 /0.0 B:22.5 /0.0 @:0 B@:0 Recv: M105
It's when I try and do anything else, it starts hitting timeout errors. For example, trying to do anything with any of the axis...
Send: G91 Recv: relative_mode = TRUE;ok Recv: G91Then a long wait then
Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves. Send: G1 Z10 F200 Recv: ok Recv: G1 Z10 F200 Send: G90 Recv: ok Recv: G90Then it's back to the M105s. Unless I have multiple commands queued and then it repeats the communication timeout stuff. I have increased the communication timeout settings but it doesn't seem like that would be the issue.
Hmm. Didn't have that issue with the temperature controls. So maybe it is just G91? I'll try some manual stuff and maybe a print.
Post edited by Richy_T on
Comments
Samuel -- That would actually be incredibly helpful. Thank you! In the meantime, are there any settings you would suggest that I check on my own and test?
"Hi,
I tried the firmware they sent (it's a version that's not currently available on this website) and successfully applied it. Frustratingly, it made things much worse. Pronterface can kinda-sorta connect and send basic commands, but the logs are full of errors:
"Connecting...
echo:
Printer is now online.
M105
echo:
M105
echo:
M105
echo:
M105
relative_mode = TRUE;G91
Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting)G0 Y10.0 F3000
G90
M114
echo:
M105
relative_mode = TRUE;G91
Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting)G0 Y-10.0 F3000"
OctoPrint, on the other hand, cannot connect AT ALL now. Not even a little bit. Sometimes lines come back that are full of garbage, too:
"Connecting to: /dev/cu.wchusbserial410
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0x11073b990, open=True>(port='/dev/cu.wchusbserial410', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=15.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Starting baud rate detection...
Changing monitoring state from "Opening serial port" to "Detecting baudrate"
Trying baudrate: 115200
Send: N0 M110 N0*125
Recv: M(-Hj%M%ZM%ZM%XJ
Recv: N0 M110 N0*125
Baudrate test retry #1"
My guess is that Pronterface is more tolerant of errors than OctoPrint, but neither of them is having a good time with this printer. I don't think this is a physical defect, either. My guess is that this is a function of the new A5S design.
The JGAURORA A5 and the A5S have different mainboards and completely different firmware. JGAURORA went with their own in-house firmware for the newer printer, too. It's becoming clear that this new configuration isn't conducive to interoperability with open standards. That's pretty aggravating, considering the whole reason I bought this printer is because my A5's heated print bed died due to bad design.
I've sent a final request to JGAURORA for any additional steps I might try, but I'm not optimistic. I think this printer is probably going back to Amazon, and I'm probably moving to the CR-20 for my next attempt. This is the third printer I've had from JGAURORA, and I never even got toย see the second one. (JGAURORA's shipping department did a poor job, and the printer was damaged/destroyed en route to me. Amazon auto-returned it, but couldn't file a replacement order without my intervention for some reason. Then JGAURORA started e-mailing me, asking why I "returned" the printer that I never received in the first place.)
Sorry if I'm coming across a bit "ranty." I loved my A5 right up until it failed, and everything since then has been downright aggravating.
Howdy, Stranger!
RegisterIt looks like you've been lurking for a while.
If you register, we will remember what you have read and notify you about new comments. You will also be able to participate in discussions.
So if you'd like to get involved, register for an account, it'll only take you a minute!