Mrnt / OctoPrint-FlashForge

OctoPrint plugin to support closed source printers from FlashForge, PowerSpec, Dremel
GNU General Public License v3.0
87 stars 12 forks source link

FlashForge Finder 2.0 - Controlling Movement #29

Open rmhalvorsen opened 4 years ago

rmhalvorsen commented 4 years ago

Flashforge Finder v2.0 Firmware 2.2.7.299 F2.12.2 20181203

controlling print head from #control tab with arrow buttons doesnt work as desired and dosent take home buttons at all.

ie. setting stepsize 10 and press arrow will move head one time in that direction at that distance only relative to start position. will not move any further by pressing arrow again, will only go one step in any direction and on time back.

from terminal tab printer does not respond to G28 command for homing all axis, it only respond to G28 ( = X, Y or Z), and will not take multiple axis at same command

dosent seams printer respond well as desired to commands G90, G91, G92 from terminal eighter.

Mrnt commented 3 years ago

@TorStava @rmhalvorsen if you could start off with a clean log, make sure debugging for the FlashForge plugin is turned on (as described in the troubleshooting section of the readme) (and preferably no other plugins enabled apart from the ones that actually come with OctoPrint and the FlashForge plugin) and do the following:

Install the dev branch as mentioned above, then:

  1. Check that the setting in the Settings > "Printer Profiles" > printer profile for your printer > "Axes" tab where you need check the box next to "G91 Not Supported" then connect to the printer and then use the controls X,Y,Z to see what happens - upload log if not working correctly
  2. Try uploading a gcode file to the SD card using the "Upload to SD" button - you should see upload progress go to 100% and then OctoPrint should immediately go into print mode showing print progress and wait for the extruder/bed to warm up.
  3. Try printing directly from OctoPrint using the "Upload" button and then starting the print process (during this process you should also see print progress in the "GCode Viewer" tab).

If any of these steps fail it will likely be early on but having a detailed log file should really help identify the issue.

TorStava commented 3 years ago

@Mrnt, here are the results of the tests. Let me know if you need anything else, I'll be happy to assist.

Test 1: Controls

Test 2: Upload to SD

Test 3: Upload then Print

Test 4: Upload then Print 2

Mrnt commented 3 years ago

@TorStava Awesome - thanks for breaking them into separate named files!

Looks like on the first log the printer is not recognizing the M400 (wait for movement to finish) command - can you verify this by just making a connection, go to the Terminal tab, type M400 and send it and then OctoPrint will should stop sending commands?

TorStava commented 3 years ago

@Mrnt, You're welcome. It seems the dev version is close to working as expected now. I can print with this version both with Upload to SD and by using Upload then Print. Although some small issues would be nice to solve, this works! Big kudos to you sir!

I tested sending the M400 command and the same thing happened as in Test 1; No more communication was received, and after a short time the connection to the printer was dropped.

octoprint_finder_m400_2020-08-29.log

TorStava commented 3 years ago

I did some additional testing using the Terminal tab:

Mrnt commented 3 years ago

@TorStava, @rmhalvorsen I made a new branch and added a fixes for:

Can you re-test by installing the Finder_2 branch using the Plugin Manager > Get More... > and under "...from URL" enter this URL:

https://github.com/Mrnt/OctoPrint-FlashForge/archive/Finder_2.zip

Mrnt commented 3 years ago

@TorStava can you also try doing a clean connection to the printer, making it do some movements to ensure they are talking to each other and then go to the Terminal tab and enter M132 X Y Z A B (like you did for M400) and see if it also drops the connection.

Mrnt commented 3 years ago

Forget the M132 test looks like it doesn't handle the command when printing directly even though it seems ok in a file on the SD card (does not bode well for other commands).

I just pushed an update to the Finder_2 branch that disables the M132 command. To test you will need to reinstall using the URL above.