Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Slic3r PE 'Send to printer'?

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    12
    36
    5.7k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • robmundefined
      robm
      last edited by

      I use the development version from GitHub, but if you're handy with perl, they're not too far diverged and you don't need to support OctoPrint you can probably just hardcode the changes. This part is all perl so there is no compiling, just hack it and see if it works 🙂

      The file is Plater.pm, on the Mac this is in Contents/MacOS/local-lib/lib/perl5/Slic3r/GUI/Plater.pm in the Application bundle.
      The routine is send_gcode(), find the parts that match under 'if($self->{config}->host_type eq 'octoprint')' and replace them with the parts under 'else'.

      [[Perl]]
      sub send_gcode {
          my ($self) = @_;
      
          $self->statusbar->StartBusy;
      
          my $ua = LWP::UserAgent->new;
          $ua->timeout(180);
      
          my $path = Slic3r::encode_path($self->{send_gcode_file});
          my $filename = basename($self->{print}->output_filepath($main::opt{output} // ''));
          my $res;
          if($self->{config}->print_host){
              if($self->{config}->host_type eq 'octoprint'){
                  $res = $ua->post(
                      "http://" . $self->{config}->print_host . "/api/files/local",
                      Content_Type => 'form-data',
                      'X-Api-Key' => $self->{config}->octoprint_apikey,
                      Content => [
                          # OctoPrint doesn't like Windows paths so we use basename()
                          # Also, since we need to read from filesystem we process it through encode_path()
                          file => [ $path, basename($path) ],
                          print => $self->{send_gcode_file_print} ? 1 : 0,
                      ],
                  );
              }else{
                  # slurp the file we would send into a string - should be someplace to reference this but could not find it?
                  local $/=undef;
                  open (my $gch,$path);
                  my $gcode=<$gch>;
                  close($gch);
      
                  # get the time string            
                  my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
                  my $t = sprintf("%4d-%02d-%02dT%02d:%02d:%02d",$year+1900,$mon+1,$mday,$hour,$min,$sec);
      
                  my $req = HTTP::Request->new(POST => "http://" . $self->{config}->print_host . "/rr_upload?name=0:/gcodes/" . basename($path) . "&time=$t",);
                  $req->content( $gcode );
                  $res = $ua->request($req);
      
                  if ($res->is_success) {
                      if ($self->{send_gcode_file_print}) {
                          $res = $ua->get(
                              "http://" . $self->{config}->print_host . "/rr_gcode?gcode=M32%20" . basename($path),
                          );
                      }
                  }
              }
          }
      
          $self->statusbar->StopBusy;
      
          if ($res->is_success) {
              $self->statusbar->SetStatusText("G-code file successfully uploaded to the " . $self->{config}->host_type . " server");
          } else {
              my $message = "Error while uploading to the " . $self->{config}->host_type . " server: " . $res->status_line;
              Slic3r::GUI::show_error($self, $message);
              $self->statusbar->SetStatusText($message);
          }
      }
      
      

      There may be something to disable 'send to printer' unless the OctoPrint API test has worked, sorry you're on your own to find and disable that.

      1 Reply Last reply Reply Quote 0
      • AlexLinundefined
        AlexLin
        last edited by

        Thanks for that as a start… Should be able look at it soon.... I read a thread here that slic3r supported duet again but that is maybe not in the PE branch. If I get the Perl script to work I'll post it....

        1 Reply Last reply Reply Quote 0
        • bartolomeusundefined
          bartolomeus
          last edited by

          Slic3r has it, Slic3rPE does not (yet?).
          What are the main differences between the two anyway? Apart from PE being developed towards the Prusa machines.

          1 Reply Last reply Reply Quote 0
          • darookeeundefined
            darookee
            last edited by

            I doubt that this feature will be integrated into the prusa edition - the main audience of the software are users of prusa printers, which don't use Duet boards. 😕

            1 Reply Last reply Reply Quote 0
            • AlexLinundefined
              AlexLin
              last edited by

              the PE version has a lot of improvements and has a higher development rate…so I would like to stick with that...but as said the perl script is an option i will investigate

              1 Reply Last reply Reply Quote 0
              • bartolomeusundefined
                bartolomeus
                last edited by

                I thought so aswell, but Slic3r is actually updated regularly. Last update is from 26th feb.

                1 Reply Last reply Reply Quote 0
                • AlexLinundefined
                  AlexLin
                  last edited by

                  OK I found a solution. It is a bit of a hack where I use the ip address /url to determine whether to send it to an octopi or a duet
                  my octopi has address octopi.local
                  my duet has address hevo.local
                  I needed to do this since the PE version doesn't have the member variables that the orginal slic3r has compiled in c++. And there is no host_type as in the code above. And I have no urge to compile it all ..
                  it is a hack an I will need to change it for every new releae..however I'm so use with my octopi just to hit 'send to printer', that it is worth it for me.
                  for windows you will need to change the file (1.39 as example)
                  C:\Slic3r-1.39.1-beta1-prusa3d-win64-full-201802221543\Slic3r-1.39.1-beta1-prusa3d-win64-full-201802221543\lib\Slic3r\GUI\Plater.pm
                  sub send_gcode at line 1459 to

                  [[perl]]
                  sub send_gcode {
                      my ($self) = @_;
                  
                      $self->statusbar->StartBusy;
                  
                      my $ua = LWP::UserAgent->new;
                      $ua->timeout(180);
                      my $res;
                       if($self->{config}->octoprint_host eq 'octopi.local'){
                  		$res = $ua->post(
                          "http://" . $self->{config}->octoprint_host . "/api/files/local",
                          Content_Type => 'form-data',
                          'X-Api-Key' => $self->{config}->octoprint_apikey,
                          Content => [
                              file => [ 
                                  # On Windows, the path has to be encoded in local code page for perl to be able to open it.
                                  Slic3r::encode_path($self->{send_gcode_file}),
                                  # Remove the UTF-8 flag from the perl string, so the LWP::UserAgent can insert 
                                  # the UTF-8 encoded string into the request as a byte stream.
                                  Slic3r::path_to_filename_raw($self->{send_gcode_file})
                              ],
                              print => $self->{send_gcode_file_print} ? 1 : 0,
                          ],
                      );
                      }
                  	else{
                           # slurp the file we would send into a string - should be someplace to reference this but could not find it?
                           local $/=undef;
                           open (my $gch,Slic3r::encode_path($self->{send_gcode_file}));
                           my $gcode=<$gch>;
                           close($gch);
                  #
                           # get the time string            
                           my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
                           my $t = sprintf("%4d-%02d-%02dT%02d:%02d:%02d",$year+1900,$mon+1,$mday,$hour,$min,$sec);
                  
                           my $req = HTTP::Request->new(POST => "http://" . $self->{config}->octoprint_host . "/rr_upload?name=0:/gcodes/" . basename(Slic3r::encode_path($self->{send_gcode_file})) . "&time=$t",);
                           $req->content( $gcode );
                           $res = $ua->request($req);
                  
                           if ($res->is_success) {
                               if ($self->{send_gcode_file_print}) {
                                   $res = $ua->get(
                                       "http://" . $self->{config}->octoprint_host . "/rr_gcode?gcode=M32%20" . basename(Slic3r::encode_path($self->{send_gcode_file})),
                                   );
                               }
                           }
                       }
                      $self->statusbar->StopBusy;
                  
                      if ($res->is_success) {
                          $self->statusbar->SetStatusText("G-code file successfully uploaded to the OctoPrint server");
                      } else {
                          my $message = "Error while uploading to the OctoPrint server: " . $res->status_line;
                          Slic3r::GUI::show_error($self, $message);
                          $self->statusbar->SetStatusText($message);
                      }
                  }
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator
                    last edited by

                    I wonder if it would be possible to just do a pull request for Slic3r PE to take the Duet connectivity from the main Slic3r dev branch that already has it working.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • AlexLinundefined
                      AlexLin
                      last edited by

                      It seems prusa hasn't merged that code from slic3r. I checked the source code of 1.39 and didn't find the changes in PE

                      1 Reply Last reply Reply Quote 0
                      • DADIYundefined
                        DADIY
                        last edited by

                        @AlexLin:

                        OK I found a solution. It is a bit of a hack where I use the ip address /url to determine whether to send it to an octopi or a duet
                        my octopi has address octopi.local
                        my duet has address hevo.local
                        I needed to do this since the PE version doesn't have the member variables that the orginal slic3r has compiled in c++. And there is no host_type as in the code above. And I have no urge to compile it all ..
                        it is a hack an I will need to change it for every new releae..however I'm so use with my octopi just to hit 'send to printer', that it is worth it for me.
                        for windows you will need to change the file (1.39 as example)
                        C:\Slic3r-1.39.1-beta1-prusa3d-win64-full-201802221543\Slic3r-1.39.1-beta1-prusa3d-win64-full-201802221543\lib\Slic3r\GUI\Plater.pm
                        sub send_gcode at line 1459 to

                        [[perl]]
                        sub send_gcode {
                            my ($self) = @_;
                            
                            $self->statusbar->StartBusy;
                            
                            my $ua = LWP::UserAgent->new;
                            $ua->timeout(180);
                            my $res;
                             if($self->{config}->octoprint_host eq 'octopi.local'){
                        		$res = $ua->post(
                                "http://" . $self->{config}->octoprint_host . "/api/files/local",
                                Content_Type => 'form-data',
                                'X-Api-Key' => $self->{config}->octoprint_apikey,
                                Content => [
                                    file => [ 
                                        # On Windows, the path has to be encoded in local code page for perl to be able to open it.
                                        Slic3r::encode_path($self->{send_gcode_file}),
                                        # Remove the UTF-8 flag from the perl string, so the LWP::UserAgent can insert 
                                        # the UTF-8 encoded string into the request as a byte stream.
                                        Slic3r::path_to_filename_raw($self->{send_gcode_file})
                                    ],
                                    print => $self->{send_gcode_file_print} ? 1 : 0,
                                ],
                            );
                            }
                        	else{
                                 # slurp the file we would send into a string - should be someplace to reference this but could not find it?
                                 local $/=undef;
                                 open (my $gch,Slic3r::encode_path($self->{send_gcode_file}));
                                 my $gcode=<$gch>;
                                 close($gch);
                        #
                                 # get the time string            
                                 my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
                                 my $t = sprintf("%4d-%02d-%02dT%02d:%02d:%02d",$year+1900,$mon+1,$mday,$hour,$min,$sec);
                        
                                 my $req = HTTP::Request->new(POST => "http://" . $self->{config}->octoprint_host . "/rr_upload?name=0:/gcodes/" . basename(Slic3r::encode_path($self->{send_gcode_file})) . "&time=$t",);
                                 $req->content( $gcode );
                                 $res = $ua->request($req);
                        
                                 if ($res->is_success) {
                                     if ($self->{send_gcode_file_print}) {
                                         $res = $ua->get(
                                             "http://" . $self->{config}->octoprint_host . "/rr_gcode?gcode=M32%20" . basename(Slic3r::encode_path($self->{send_gcode_file})),
                                         );
                                     }
                                 }
                             }
                            $self->statusbar->StopBusy;
                            
                            if ($res->is_success) {
                                $self->statusbar->SetStatusText("G-code file successfully uploaded to the OctoPrint server");
                            } else {
                                my $message = "Error while uploading to the OctoPrint server: " . $res->status_line;
                                Slic3r::GUI::show_error($self, $message);
                                $self->statusbar->SetStatusText($message);
                            }
                        }
                        
                        

                        Thanks, that worked for me on 1.38.5.

                        1 Reply Last reply Reply Quote 0
                        • AlexLinundefined
                          AlexLin
                          last edited by

                          nice , somebody else can use it;-)

                          1 Reply Last reply Reply Quote 0
                          • darookeeundefined
                            darookee
                            last edited by

                            @Phaedrux:

                            I wonder if it would be possible to just do a pull request for Slic3r PE to take the Duet connectivity from the main Slic3r dev branch that already has it working.

                            It looks like it is this commit https://github.com/alexrj/Slic3r/commit/1c74067da09a9a23ce66227b55146af6182d747d, it should be possible to pull it in and build your 'own' slic3r version, but I guess that these are not the only changes needed. 5fbb245b9790193b6924735fd985dc3cd2350ee6 and 13f121e3d952cca33b1ee5fdd73c12d85bf54d0e also mention the duet.

                            Edit: As I said before, I doubt that this would get accepted 😕

                            0 emaker committed to alexrj/Slic3r
                            Octoprint settings functionality expanded to allow upload to RepRapFi… (#4028)
                            
                            * Octoprint settings functionality expanded to allow upload to RepRapFirmware on a Duet controller.
                            
                            * octoprint_host renamed to print_host to enhance code readability.
                            
                            Fixes #4022
                            1 Reply Last reply Reply Quote 0
                            • robmundefined
                              robm
                              last edited by

                              @AlexLin:

                              OK I found a solution. It is a bit of a hack where I use the ip address /url to determine whether to send it to an octopi or a duet

                              Nice work, well done. (in lieu of a 'like' button for an individual post) 🙂

                              1 Reply Last reply Reply Quote 0
                              • mloidlundefined
                                mloidl
                                last edited by

                                I don't think prusa will accept a pull request for this issue at the moment.
                                On github i found the following open issue https://github.com/prusa3d/Slic3r/issues/695, seems they will do some refactoring.

                                Today they committed a change which seems to be part of the refactoring.
                                https://github.com/prusa3d/Slic3r/commit/4a90ab1f6a1390df4ce332b342536ee61db6ebfd

                                cbusillo created this issue in prusa3d/Slic3r

                                closed Feature request: Duet Wifi connect #695

                                0 bubnikv committed to prusa3d/Slic3r
                                Merge branch 'octoprint'
                                1 Reply Last reply Reply Quote 0
                                • thehairundefined
                                  thehair
                                  last edited by

                                  We'll see if we get a response to the most recently opened issue on Github https://github.com/prusa3d/Slic3r/issues/935. I'm not too hopeful that the Prusa version will ever add in support for the Duet. I ended up making a post processing script that uploads the gcode file. The script is basically just the perl code that slic3r usually uses to upload files.

                                  #!/usr/bin/perl -i
                                  
                                  use strict;
                                  use warnings;
                                  use LWP::UserAgent;
                                  use File::Slurp;
                                  use File::Basename;
                                  
                                  # Set up filepath and filename
                                  my $filepath = $ARGV[0];
                                  $filepath =~ tr|\\|/|;
                                  my $filename = basename($filepath);
                                  
                                  my $ua = LWP::UserAgent->new;
                                  my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
                                  my $t = sprintf("%4d-%02d-%02dT%02d:%02d:%02d",$year+1900,$mon+1,$mday,$hour,$min,$sec);
                                  
                                  my $server_endpoint = "http://192.168.X.XX/rr_upload?name=gcodes/$filename&time=$t";
                                  my $req = HTTP::Request->new(POST => $server_endpoint);
                                  my $data_file = read_file( $filepath, { binmode => ':raw' } );
                                  $req->content($data_file);
                                   
                                  my $resp = $ua->request($req);
                                  
                                  if ($resp->is_success) { 
                                      my $message = $resp->decoded_content;
                                      print "Received reply: $message\n";
                                  }else {  
                                      print "HTTP POST error code: ", $resp->code, "\n";
                                      print "HTTP POST error message: ", $resp->message, "\n";   
                                  }
                                  

                                  You'll have to put the address of your Duet where the "XXX" are in the $server_endpoint var. I run all my post processing scripts from a windows bat file which looks sort of like this at the end:

                                  pause
                                  perl "C:\Program Files\Slic3r\uploadgcodefile.pl" %1
                                  del /f %1 
                                  pause
                                  

                                  The bat file uploads the gcode file and then deletes it. The first pause allows me to close the command window to cancel the upload/delete command. The last pause allows me to verify the upload worked.

                                  This process definitely isn't perfect, but is easier than manually uploading files.

                                  Xphomegra created this issue in prusa3d/Slic3r

                                  closed [Request] Add duet/reprapfirmware upload (From slic3r 1.3.0-dev) #935

                                  1 Reply Last reply Reply Quote 0
                                  • mloidlundefined
                                    mloidl
                                    last edited by

                                    Hi,

                                    I've added the option for sending G-Codes to Duet and already created a pull request for it (https://github.com/prusa3d/Slic3r/pull/1051)
                                    Let's see if Prusa will overtake it into their repo.

                                    If someone is interested in testing it can be cloned from https://github.com/mloidl/Slic3r/tree/duet

                                    Best regards,
                                    Martin

                                    mloidl opened this pull request in prusa3d/Slic3r

                                    closed Added possibility for upload to Duet #1051

                                    Phaedruxundefined AlexLinundefined Mordekainundefined 3 Replies Last reply Reply Quote 3
                                    • Phaedruxundefined
                                      Phaedrux Moderator @mloidl
                                      last edited by

                                      @mloidl Great work, I hope they take it for the next release.

                                      Z-Bot CoreXY Build | Thingiverse Profile

                                      1 Reply Last reply Reply Quote 0
                                      • AlexLinundefined
                                        AlexLin @mloidl
                                        last edited by

                                        @mloidl nice,well done!!

                                        1 Reply Last reply Reply Quote 0
                                        • Mordekainundefined
                                          Mordekain @mloidl
                                          last edited by

                                          @mloidl thanks for the work! great to see it was accepted!

                                          If it's not too much trouble, do you think you could post a release already built with the commit?

                                          mloidlundefined 1 Reply Last reply Reply Quote 0
                                          • mloidlundefined
                                            mloidl @Mordekain
                                            last edited by

                                            @mordekain I have not yet tried to build a release for another pc than mine. I'll try to create a linux appimage for testing. I'm not able to provide a windows or mac executable.
                                            On the other hand i assume prusa will release another beta or release candiate soon (current beta was released 19 days ago)

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA