Giter Site home page Giter Site logo

m33-fio's People

Contributors

abbradar avatar dgdev91 avatar donovan6000 avatar dragondgold avatar foosel avatar markbastiaans avatar ra100 avatar stremlau avatar tonylhansen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

m33-fio's Issues

Octoprint API integration?

It would be very helpful if the readme specified whether this plugin makes changes to the octoprint API.

It brings many great features to the slicing functionality, like rotation of the model and other options, and it would be great if they were accessible in the API if they aren't already.

Slicing doesn't work - Invalid cross-device link

Now I'm getting this error

2015-12-07 17:20:25,453 - octoprint - ERROR - Exception on /plugin/m3dfio/upload [POST]
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1817, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1477, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1381, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/local/lib/python2.7/dist-packages/octoprint_m3dfio/__init__.py", line 4244, in upload
    os.rename(modelLocation, modelTemp)
OSError: [Errno 18] Invalid cross-device link

[Suggestion] Add plugin to the OctoPrint Plugin Repository

Hey,

It would be great if you added that plugin to plugins.octoprint.org - unless there's a particular reason that is not possible?

Instructions can be found here - you'll basically just have to clone a repository and add a file to it. If you don't want to, I could also add it, just don't want to add any plugins without asking the authors first.

Cheers,
Gina 🐙

print speed

Hi Donovan,

I got some stange problem and want to ask if anyone can reproduce this or if this is only my problem.

I got a M3D micro, a raspberry pi 2, octoprint 1.2.7 and m3d fio 0.17.

A small testcube with some details on it prints usually in 1 hour, with octopi 7 hours. Then I figured out what’s going wrong. Maybe this helps to fix this bug

The gcode
'G1 X10’ moves the printhead 10mm right. works fine.
‘G1 X10 F3000’ should move it 10mm right with 3000mm/min or 50mm/sec.
‘G1 X10 F300’ should do the same with 300mm/min or 5mm/sec.

It turnes out that F300 moves the printhead ways faster than F3000. So I think the Fxxxx will be interpreted as duration fot the step instead of the speed.

Can you reproduce this?

Thanks a lot.

regards,
Björn

M3D stops printing after ~6h

I have been printing a relative big model for over 6h but then the printer just stops moving. I was still heating and octoprint seams to send the commands to the printer but for some reason the printer ignores those commands. I tried it another time and again after more then 6h the same issue happened. However this time the printer printer the model a bit longer then the first time. Does someone know what could be going in here? I know that this might be an issue with the printer itself or with octoprint but since octoprint is not supported by the official m3d team, this project is my only hope for a solution.

Fan not turning off on completion

Have just finished calibrating (for the second time) and printed test border, which has come out fine; however the fan then continued to run at full volume. Not sure whether it's intended that it runs for a period after the print, I left it for a minute and then turned it off manually - is/should there be an "on completion" script which turns the fan off?

Print Quality

Hi,

I usually generate my model with Cura under windows, and send it to the printer with M3D spooler.
I'm trying M3D-Fio with the same model, and the print quality is poor. Printer's movements are not the same, M3D-Fio do a lot of random movements...

I don't understand since it come from the same gcode.

The question is, does Fio use M3D preprocessors when receiving a gcode from octroprint?

Printer is also slower while printing...

Double movement when manually calibrating

While manual calibration or during complete calibration in manual phase the head moves sometimes twice to the center.
Here is head movement: position: Center, Back, Front, Left, Right
B->R->C->FL->B->R->C->B->R->C->FR->B->R->C->BR->B->R->C->B->R->C->BL
See, there is double sequence B->R->C between FL and FR and BR and BL positions.
When using on-the-fly settings is a bit different:
B->R->C->FL->FR->B->R->C->BR->BL
(B->R->C sequence is obviously movement to "reset" positions and move to center)

Permission denied for /octoprint_m3dfio/static/temp/

I am/was getting this error OSError: [Errno 13] Permission denied: '/usr/local/lib/python2.7/dist-packages/OctoPrint_M3DFio-0.22-py2.7.egg/octoprint_m3dfio/static/temp/'

I fixed it, for now, by creating temp folder and setting permissions to 777. But I think, this shouldn't work that way. I'm not running octoprint asi root but asi user "pi" with root privileges.

Printer stopped in the middle of the print

Hello donovan,
i started a little bigger print job (20.3MB) with the M3D Fio (0.15) installed as plugin on octoprint (via manual pip install). Everything was working as expected and i went away letting it print when i came back it had just stopped middle print (at 6.1MB printed) with this in the log file.
Do you know what could be the issue? Should i adress this somewhere else?

Thanks for the awsome work!

Recv: ok 139302
Recv: ok 139303
Send: N139306 G1 X31.963608 Y47.860776 Z13.474178 E4241.907177_4
Send: N139307 G1 X33.377822 Y49.274990 Z13.490765 E4241.965382_5
Recv: ok 139304
Serial timeout while writing to serial port, trying again.
Unexpected error while writing to serial port: AttributeError: ''NoneType' object has no attribute 'write'' @ comm.py:_doSendWithoutChecksum:1639
Closing down send loop
Send: N139308 G1 X34.792035 Y50.689203 Z13.507351 E4242.023587*4
Unexpected error while writing to serial port: TypeError: ''NoneType' object is not callable' @ comm.py:_doSendWithoutChecksum:1635
Changing monitoring state from 'Printing' to 'Error: TypeError: ''NoneType' object is not callable' @ comm.py:_doSendWithoutChecksum:1635'
Recv: ok 139305
Connection closed, closing down monitor
Closing down send loop
Unexpected error while setting baudrate: 230400 SerialTimeoutException: 'Write timeout' @ comm.py:_monitor:1048
Connection closed, closing down monitor

M3D will stop on Raspberry Pi

I tried several models that print without a problem on M3D default software. When I print via Octoprint on Raspberry Pi , the raft or the brim print fine than the printer will start the first layer and stop before it's done. The GCode viewer and terminal continue to send commands.

I also tried gcode generated on another Cura and the same happens.

Zits in the upper region using octopi and M3D-Fio

Hi,
Thanks for the wonderful plugin, I am experiencing an issue though with a raspberry pi B (2015-12-15_2015-11-21-octopi-jessie-0.13.0.zip) and printing. I get lots of zits in the upper region (see attached image).
This is the test print to calibrate backlash (https://printm3d.com/solutions/article.php?id=80).
On the left is the octopi print, on the right is from M3D's software.
I have tried many settings and they all produce the same results (the print on the left uses the default plugin settings).
Steps tried:

  1. Overclock raspberry pi (no change)
  2. Use stable octopi 1.2 (no change)
  3. Use the latest git from here (no change, like the autodetect feature though).

Am I missing something obvious?

Dougie
dsc_0225

1.3.0 can't print test border on RPi without Display manager

There are maybe more problems together. I ran calibrations and wanted to printe test border. I've got this from log:

2016-01-16 19:51:48,868 - octoprint.settings - WARNING - Could not convert '' to a valid integer when getting option []
2016-01-16 19:51:48,926 - octoprint - ERROR - Exception on /api/plugin/m3dfio [POST]
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1817, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1477, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1381, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint-1.3.0.dev810+g3b35d92-py2.7.egg/octoprint/server/util/flask.py", line 709, in decorated_view
    return flask.ext.login.login_required(func)(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/Flask_Login-0.2.2-py2.7.egg/flask_login.py", line 637, in decorated_view
    return func(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint-1.3.0.dev810+g3b35d92-py2.7.egg/octoprint/server/api/__init__.py", line 97, in pluginCommand
    response = api_plugin.on_api_command(command, data)
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint_M3DFio-0.24.3-py2.7.egg/octoprint_m3dfio/__init__.py", line 1349, in on_api_command
    self.sendCommands(self.getSaveCommands())
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint_M3DFio-0.24.3-py2.7.egg/octoprint_m3dfio/__init__.py", line 4052, in getSaveCommands
    packed = struct.pack('f', softwareBackLeftOffset)
error: required argument is not a float
2016-01-16 19:51:48,951 - tornado.access - ERROR - 500 POST /api/plugin/m3dfio (192.168.150.11) 108.64ms
2016-01-16 19:51:59,051 - octoprint.plugin - ERROR - Error while calling plugin m3dfio
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint-1.3.0.dev810+g3b35d92-py2.7.egg/octoprint/plugin/__init__.py", line 242, in call_plugin
    result = getattr(plugin, method)(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint_M3DFio-0.24.3-py2.7.egg/octoprint_m3dfio/__init__.py", line 2707, in on_event
    self.disableSleep()
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint_M3DFio-0.24.3-py2.7.egg/octoprint_m3dfio/__init__.py", line 6113, in disableSleep
    bus = dbus.SessionBus()
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 211, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
DBusException: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
2016-01-16 19:51:59,155 - tornado.access - WARNING - 404 GET /api/files/local/test_border (192.168.150.11) 67.60ms
2016-01-16 19:52:02,730 - tornado.access - WARNING - 404 GET /api/files/local/test_border (192.168.150.11) 56.82ms
2016-01-16 19:52:02,941 - tornado.access - WARNING - 404 GET /api/files/local/test_border (192.168.150.11) 57.81ms

I see one problem might be with test_border extension? 404 GET /api/files/local/test_border.
And another that I don't start display manager on my RPi, it's just in console.

octoprint calibration offset (z-axis)

Hello

My octopi + micro3d setup is almost working fine. It seems the automatic calibration is a bit off and the print is not sticking to the board.
Can I somehow manually offset the z0 in octoprint (like you can on the native micro3d software) ?

On the octoprint forum they suggested to make a custom gcode control, but they had doubts how this would integrate with the custom plugin for the Micro ...

Any suggestions welcome.

thx for helping out :)

OctoPrint disconnects on Calibration

I've had this problem also with older versions. Everytime I try to Calibrate Z0, bed orientation or complete calibration. Calibratino starts, but after few seconds I get message, that I'm disconnected from server. I can reconnect after a while, but also after half an hour, the calibration "modal" doesn't hide. I have to refresh window. Seem that calibration gets done, but with Complete calibration it gets stuck after first "step" (maybe center Z0?) and I don't get any instructions. I can't find anything wrong in logs.

Cannot install v0.25 on fresh octoprint install

Hi. I cannot install v0.25 neither from command line nor from web interface.

Please find attached steps:

root@odroid:~/OctoPrint# ./venv/bin/octoprint --version
OctoPrint version 1.2.8.post0.dev0+gdedadbc
root@odroid:~/OctoPrint# /root/OctoPrint/venv/bin/pip install https://github.com/donovan6000/M3D-Fio/archive/master.zip
Downloading/unpacking https://github.com/donovan6000/M3D-Fio/archive/master.zip
  Downloading master.zip (4.8Mb): 4.8Mb downloaded
  Running setup.py egg_info for package from https://github.com/donovan6000/M3D-Fio/archive/master.zip

Cleaning up...
root@odroid:~/OctoPrint# service octoprint restart
Restarting Octoprint Daemon: Octoprint.

After restart there is no M3D Fio menu under settings. But when I install V0.24.3 then plugin installs correctly:

root@odroid:~/OctoPrint# /root/OctoPrint/venv/bin/pip install https://github.com/donovan6000/M3D-Fio/archive/V0.24.3.zip
Downloading/unpacking https://github.com/donovan6000/M3D-Fio/archive/V0.24.3.zip
  Downloading V0.24.3.zip (unknown size): 4.6Mb downloaded
  Running setup.py egg_info for package from https://github.com/donovan6000/M3D-Fio/archive/V0.24.3.zip

Installing collected packages: OctoPrint-M3DFio
  Found existing installation: OctoPrint-M3DFio 0.25
    Not uninstalling OctoPrint-M3DFio at /usr/local/lib/python2.7/dist-packages, outside environment /root/OctoPrint/venv
  Running setup.py install for OctoPrint-M3DFio

Successfully installed OctoPrint-M3DFio
Cleaning up...
root@odroid:~/OctoPrint# service octoprint restart
Restarting Octoprint Daemon: Octoprint.

Brainstorming: spliting M3D-Fio into parts

At the moment M3D-Fio doesn't integrate nicely with Octoprint. The way it hacks itself into the printer log and read / write functions isn't the way Octoprint developers intended things to work. It is also a mixture of things specific to the M3D Micro and more general problems. Therefore I would like to propose splitting M3D-Fio into parts and to use the parts of the Octoprint API that where mend to be used. I've already send a pull request to Octoprint to support the gcode.queing hook to return multiple commands and this could then be used in the various preprocessor steps to do on-the-fly conversion cleanly.

M3DSerial

Unlike other printers the M3D Micro does not speak plain ascii G-Code. It also has a bootloader mode and printing mode. I believe the right mechanism for this is to use the serial factory hook and translate between ascii G-Code and M3D binary there. The serial object would need a few extra methods to handle reading and writing of the eeprom and firmware updates but that shouldn't be a problem.

I would also include the feed rate conversion in this step. Actually I would make that part non-optional and part of the gcode ascii <-> binary conversion in gcode.py.

Backlash

Backlash is a problem with all printers and not all of them handle that in firmware (or you don't want to mess with the firmware). I propose splitting this off as it's own plugin and provide hooks for the M3D plugin to get/set the values from the printers eeprom.

Bed Compensation

Again a common problem with printers. And even if I can level the printers bed perfectly I sometimes wish to adjust the bed height to make the first layer be squished down more to stick better. Or the print bed is simply warped and can only be compensated for in software. Again I propose splitting this off as it's own plugin with interface to the M3D plugin.

Raft Plugin

This would be a new plugin very similar to the Bed Compensation. Or more precise instead of the Bed Compensation. Instead of warping the whole print to match a warped print bed I want to print a raft below the object with variable heights so that the bottom of the raft fits the warped print bed and the top is horizontal. The object itself would then only be printed some constant amount higher. The reason I mention it here is that the M3D plugin should interface with this the same way it would interface with the Bed Compensation.

Wave Bonding and Thermal Bonding

I'm unsure about those two and I use neither. I think I already handle thermal bonding in my slic3r settings so never needed it. Totally in he dark what Wave Bonding is supposed to be.

Centering and Print Volume Check

Both are things every printer could use. In fact they are so elemental I wonder why Octoprint doesn't already have them built-in. One point though. The Octoprint printer profile only has rectangular and circular print beds as option. This ignores the fact that the print volume isn't always a perfect cube or cylinder. In slic3r one can upload a STL file as print volume. This might work as a more generic format to specify the print volume and the M3D plugin would supply the proper shape for a generic plugin.

M3D Plugin

This would be whatever is left after splitting of stuff and the glue to hold the rest together. Namely handling the eeprom, fan profile, extruder current, calibration, and supplying the right settings to the split off plugins.

Comments? Ideas? Objections?

Bed calibration not saved

I tried to run Calibrate Bed orietation more times and the values in M3DFio settings stayed the same. Also M3D-Linux showed that same values. Than I tried to run M107, G32, M117 commands in M3D-Linux and those values finally changed, but in OctoPrint I see the old values. Seems like "Obtain printer settings automatically when a Micro 3D printer connects" doesn't work as expected.

Heated Bed Integration

My apologies for this not being an issue.

I wanted to get in touch with you guys about integrating support for Chase's Heated Bed. I'm the FW dev for the controller and I'd love to see integration with your octoprint extensions.

Chase mentioned that he had given my info to a couple of different people who were interested in adding support for the heated bed. I don't know if we were ever in contact or not.

If your willing let me know and we can collaborate to get that done. Should be pretty easy. It just uses a serial connection.

Thanks,

loswave

Latest commit will not print at all

Commit: 083fde3

I can send manual commands, but when printing, it fails. Octoprint log is showing an error calling the m3dfio plugin. It's running on OctoPi.

2016-01-16 13:06:56,621 - octoprint.plugin - ERROR - Error while calling plugin m3dfio
Traceback (most recent call last):
  File "/home/pi/oprint/local/lib/python2.7/site-packages/OctoPrint-1.2.8-py2.7.egg/octoprint/plugin/__init__.py", line 204, in call_plugin
    result = getattr(plugin, method)(*args, **kwargs)
  File "/home/pi/oprint/local/lib/python2.7/site-packages/OctoPrint_M3DFio-0.24.3-py2.7.egg/octoprint_m3dfio/__init__.py", line 2680, in on_event
    if not self.disableSleep() :
  File "/home/pi/oprint/local/lib/python2.7/site-packages/OctoPrint_M3DFio-0.24.3-py2.7.egg/octoprint_m3dfio/__init__.py", line 6113, in disableSleep
    bus = dbus.SessionBus()
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 211, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)

serial_fail.log 2.zip
octoprint.log.zip

Slicing profile gets deleted after slicing

I know, that tihs is not finished yet, but when I use my custom slicing profile, it gets removed after model is sliced. I need to copy that profile again to profiles folder.

error 'M3DFioPlugin' object has no attribute 'printerBacklashX'

It does seem, everytihng works, but OctoPrint log/console output I see this error.

2015-12-07 18:52:38,296 - octoprint - ERROR - Exception on /api/plugin/m3dfio [POST]
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1817, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1477, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1381, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/media/nidhogg/pi/devel/OctoPrint/venv/local/lib/python2.7/site-packages/OctoPrint-1.2.9.dev1+g547dcdd-py2.7.egg/octoprint/server/util/flask.py", line 491, in decorated_view
    return flask.ext.login.login_required(func)(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/Flask_Login-0.2.2-py2.7.egg/flask_login.py", line 637, in decorated_view
    return func(*args, **kwargs)
  File "/media/nidhogg/pi/devel/OctoPrint/venv/local/lib/python2.7/site-packages/OctoPrint-1.2.9.dev1+g547dcdd-py2.7.egg/octoprint/server/api/__init__.py", line 96, in pluginCommand
    response = api_plugin.on_api_command(command, data)
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint_M3DFio-0.22-py2.7.egg/octoprint_m3dfio/__init__.py", line 897, in on_api_command
    self._printer.commands(self.getSaveCommands())
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint_M3DFio-0.22-py2.7.egg/octoprint_m3dfio/__init__.py", line 2439, in getSaveCommands
    if self.printerBacklashX != softwareBacklashX :
AttributeError: 'M3DFioPlugin' object has no attribute 'printerBacklashX'

Test border - No fan speed has been detected

When printing test border I get No fan speed has been detected in this file which could cause the print to fail. but it's probably just my problem with HW. I couldn't get the fan to spin for some time now, already tried to change fan. And now, I've got external power supply for fan.
And I've got second (original) fan still connected to printer power supply.

Cannot manually change bed orientation

When I attempt to change the values for bed orientations in the M3D-Fio settings pannel and reload they return to their previous value. Here is a snippet from the terminal when I try to change the values:

Send: M618 S5 P3218932656
Send: M619 S5
Recv: ok Target address out of range
Recv: ok
Recv: ok PT:5 DT:-1076034652

This is from chaning the Front Right Orientation from "1.726674" to "1.726675"

Front Right Offset is not being saved

When editing printer settings and changing offset with enabled "Obtain printer settings automatically when a Micro 3D printer connects", Front Right Offset is not saved and rewritten by Front Right Orientation.

Octoprint UI not working with m3dFio settings in config.yaml

After octoprint restart, I must first remove m3dfio settings from config.yaml to make it work again. Otherwise it doesn't who "Settings" menu and "Connection" panel. And I see nothing suspicious in logs.
Is there a way to enable m3dfio debug log?
This happens on master, maintenance and devel branch of octoprint.

Extruder temperature / Filament temperature / manual control

Trying to troubleshoot my temperature issues ...

  • am I right in thinking that the "Filament Temperature" setting in the "M3D FIO" tab of the Settings page is intended to set the general target temperature? (subject to any pre-processor or manual changes that are made)
  • does the temperature setting here then pre-set the temperature control in the "Extruder" section of the Control tab?

Without calibrated Z0 offsets, print fails

OctoPrint 1.2.8 (master branch).
This is with default settings - on-the-fly with and without shared library

Send: N21 G0 X1 Y9.5 Z0.15 F900*55
Recv: wait
Send: N22 G0 X1.000000 Y9.500000 Z-nan F630.003333**116
Unexpected error while writing to serial port: ValueError: 'could not convert string to float: -' @ comm.py:_doSendWithoutChecksum:1689
Changing monitoring state from 'Printing' to 'Error: ValueError: 'could not convert string to float: -' @ comm.py:_doSendWithoutChecksum:1689'

I also get this, octoprint ui acts like print is in progress, but printer is not responding - on-the-fly without share library, the same is without onthefly and withou shared library

Send: N21 G0 X1.000000 Y9.500000 Znan F630.003333**90
Recv: wait
Send: N22 G0 Z0.4 E6*26
Recv: wait
Send: N23 G0 Znan E6**122
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Serial timeout while writing to serial port, trying again.
Recv: wait

Seems like problem with sending Znan.

Suggest re-labelling the "Complete Bed Calibration" button ...

... going through a clean install to see whether I can overcome my temperature/quality issues, and having run through the calibration steps I tapped on the "complete ..." button in order to finish the calibration process ... and then realised that it's now going to run the complete process from scratch!

It's not a mistake that anyone's going to make twice, but maybe add the word "Run" at the start?

on-the-fly commands are out of order

2015-12-25 17:31:48,059 - SERIAL - DEBUG - Send: N40 G1 X34.350338 Y37.338277 Z0.065165 E2.25762040
2015-12-25 17:31:48,199 - SERIAL - DEBUG - Recv: ok 40
2015-12-25 17:31:48,201 - SERIAL - DEBUG - Send: N41 G1 X36.252507 Y36.720416 Z0.067163 E2.337615
42
2015-12-25 17:31:48,341 - SERIAL - DEBUG - Recv: ok 41
2015-12-25 17:31:48,343 - SERIAL - DEBUG - Send: N42 G1 X38.154676 Y36.102554 Z0.069160 E2.41760935
2015-12-25 17:31:48,483 - SERIAL - DEBUG - Recv: ok 42
2015-12-25 17:31:48,484 - SERIAL - DEBUG - Send: N43 G1 X40.373000 Y35.382000 Z0.069993 E2.51090
20
2015-12-25 17:31:48,625 - SERIAL - DEBUG - Recv: ok 43
2015-12-25 17:31:48,626 - SERIAL - DEBUG - Send: N44 M105_23
2015-12-25 17:31:48,791 - SERIAL - DEBUG - Recv: ok 44
2015-12-25 17:31:48,792 - SERIAL - DEBUG - Recv: T:240.0716
2015-12-25 17:31:48,793 - SERIAL - DEBUG - Send: N45 G1 X35.295 Y31.445 E2.59128_89
2015-12-25 17:31:48,796 - SERIAL - DEBUG - Recv: ok 45
2015-12-25 17:31:48,797 - SERIAL - DEBUG - Send: N46 G1 X39.256 Y31.280 E2.74986_85
2015-12-25 17:31:48,944 - SERIAL - DEBUG - Recv: ok 46
2015-12-25 17:31:48,945 - SERIAL - DEBUG - Send: N47 G1 X67.929 Y31.280 E3.89677_94
2015-12-25 17:31:49,237 - SERIAL - DEBUG - Recv: ok 47
2015-12-25 17:31:49,238 - SERIAL - DEBUG - Send: N48 G1 X50.311000 Y34.859000 Z0.056362 E2.90985939
2015-12-25 17:31:49,385 - SERIAL - DEBUG - Recv: ok 48
2015-12-25 17:31:49,386 - SERIAL - DEBUG - Send: N49 G1 X52.311000 Y34.859000 Z0.054643 E2.989858
41
2015-12-25 17:31:49,534 - SERIAL - DEBUG - Recv: ok 49
2015-12-25 17:31:49,535 - SERIAL - DEBUG - Send: N50 G1 X54.311000 Y34.859000 Z0.052924 E3.06985738
2015-12-25 17:31:49,682 - SERIAL - DEBUG - Recv: ok 50
2015-12-25 17:31:49,685 - SERIAL - DEBUG - Send: N51 G1 X56.311000 Y34.859000 Z0.051205 E3.149857
45
2015-12-25 17:31:49,830 - SERIAL - DEBUG - Recv: ok 51

If you look at N47 you can see that the position is a big step from N46 and the E value is larger. But then N49.. draws an earlier line with lower E values.

on-the-fly conversion inserts more and more G4 gcodes

I'm printing a Dalek salt and pepper shaker and I noticed that as time goes on the printer pauses for longer and longer times mid print. Looking at the octoprint stdout I see:

2015-12-13 19:55:02,257 - octoprint.plugins.m3dfio - INFO - N369472 G4
2015-12-13 19:55:02,289 - octoprint.plugins.m3dfio - INFO - N369473 G4
2015-12-13 19:55:02,302 - octoprint.plugins.m3dfio - INFO - N369474 G4
2015-12-13 19:55:02,321 - octoprint.plugins.m3dfio - INFO - N369475 G4
2015-12-13 19:55:02,339 - octoprint.plugins.m3dfio - INFO - N369476 G4
2015-12-13 19:55:02,357 - octoprint.plugins.m3dfio - INFO - N369477 G4

I see runs of this going on and on for 400-500 lines and they seem to get longer.

Printer stops extruding shortly after start

Hi!
My issue is that after a while of printing, the printer stops extruding filament but the printhead keeps moving and rises in height for every layer.
If I restart the print, it will stop extruding relatively precise where it stopped the last time. Every model has an other point where it stops extruding.
The lastest M3D software is working fine though.
Do you have any tips on which information I should provide that could be helpful?

Your plugin is very cool, I love it already!

Print test border fails

Using M3D Fio 0.9 and using Control -> Print test border, I receive the following error message:

2015-08-13 12:05:38,022 - octoprint - ERROR - Exception on /api/plugin/m3dfio [POST]
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1817, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1477, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1381, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint-1.2.4-py2.7.egg/octoprint/server/util/flask.py", line 414, in decorated_view
    return flask.ext.login.login_required(func)(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/flask_login.py", line 637, in decorated_view
    return func(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint-1.2.4-py2.7.egg/octoprint/server/api/__init__.py", line 94, in pluginCommand
    response = api_plugin.on_api_command(command, data)
  File "/usr/local/lib/python2.7/dist-packages/octoprint_m3dfio/__init__.py", line 367, in on_api_command
    self.getPrintInformation(temp)
  File "/usr/local/lib/python2.7/dist-packages/octoprint_m3dfio/__init__.py", line 1339, in getPrintInformation
    if self.minZExtruder < self.bedLowMinZ or self.maxZExtruder > self.bedHighMaxZ or self.maxXExtruderLow > self.bedLowMaxX or self.maxXExtruderMedium > self.bedMediumMaxX or self.maxXExtruderHigh > self.bedHighMaxX or self.maxYExtruderLow > self.bedLowMaxY or self.maxYExtruderMedium > self.bedMediumMaxY or self.maxYExtruderHigh > self.bedHighMaxY or self.minXExtruderLow < self.bedLowMinX or self.minXExtruderMedium < self.bedMediumMinX or self.minXExtruderHigh < self.bedHighMinX or self.minYExtruderLow < self.bedLowMinY or self.minYExtruderMedium < self.bedMediumMinY or self.minYExtruderHigh < self.bedHighMinY :
AttributeError: 'M3DFioPlugin' object has no attribute 'minZExtruder'

M3d fio is pretty cool.

You can close this issue straight away. Anyway, just wanted say M3D fio is pretty cool. It's helped me a lot. :0

Linux i686 shared library

The platform I'm running M3D Fio on is based on an Intel Atom processor which doesn't have a 64-bit instruction set. Would it be possible to add a Linux i686 shared preprocessing library to M3D Fio?

It would be great if you could take a look at this!

Can't print with new release

Just installed your new release let me tell you it's great! We now can use the GCode Viewer and you don't have to slice every time you change something like bed leveling!

But now I can't even print, once the hotend finished heating and the printer has to move the printer just sends "Resend ", M3D-Fio keeps sending the following lines and the printer stays still while Octoprint sends all the GCode!

firmware update issue

When I connect a new m3d I get a request to update firmware to 2016010812. I then had to disconnect from USB to raspi/octoprint, power cycle printer before it would attempt to communicate again with printer. Then it would request to calibrate the bed. Calibration was slow then crashed completely. Moving the m3d back to mac laptop with m3d software it listed it as incompatible firmware and reverts it to 2015102303 before the printer works again. Octoprint is latest rpi image, then it updates itself and then I installed the m3d plugin. Pi is a B+. Maybe that is my issue and I should move it to a Pi2.

High memory usage on model preparation

When trying to slice large model 3MB and more, the memory usage is over 250 MB, which can be sometimes problem on Raspberry Pi. I tried 3MB and 4MB model, and both consumed about same ammout of memory, with 1MB it has been much less. I didn't do any exact measurements, just watched htop after hittin "Slice", most memory usage was while "Applying changes" phase.
It is not as issue as suggestion for performance improvement.

large model

Need to set temperature 50° higher than usual

I've got this issue a long time, maybe more than month. I need to set PLA temperature to 260°C to make it print, so pla it doesn't get stuck in printhead. Before I've been able to print from 190°C.
I already contacted m3d support and they responded that it's OK, to set the temperature to value that works for me. But I'm not sure what caused this change. Could this be extrude current issue? I've always had 500mA setting and it didn't change, but it keeps me thinking if I shouldn't try 660mA, but I don't want to damage heater. I also wanted to know from m3d which extruder I have, but there is no way to know, as they said.

OctoPrint 1.3.0 model loading fail

Just in case you'll be working on support for OctoPrint 1.3.0. I get error in console when loading stl file:

tornado.access - WARNING - 404 GET /downloads/files/local/filter 

It seems that somewhere in the process extension gets lost, url should be /downloads/files/local/filter.

From time to time I am trying to run M3DFio with dev branch of OctoPrint.

Tall print stops 3-4 layers from the top

Twice in a row, with different gcode files (slight changes to the model), the print stops 3-4 layers from the top, about the same place. The head is stuck to the print where it just stopped printing/moving. I'm running another print logging the serial communication. 0.24.3. Octoprint marks the print as successful.

Frame_fail.gcode.zip
Update: Had serial logging already on
serial.log.zip
At line 10816, you see the end of the print, with way off command/ack numbers
2016-01-14 02:02:51,853 - SERIAL - DEBUG - Send: N245372 M18*47
2016-01-14 02:02:51,863 - SERIAL - DEBUG - Recv: ok 244723
Even at the start of the captured log, they seem to be wonky
2016-01-14 01:22:05,229 - SERIAL - DEBUG - Send: N240766 G1 X55.660 Y52.660 E2.9994*107
2016-01-14 01:22:05,258 - SERIAL - DEBUG - Recv: ok 240123
I'll capture the entire communication log next.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.