• Welcome to the new Distech Automation Forum!
  • Feel free to post questions, comments, and feedback.
  • Ask us anything!
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Anyone install P System on a Rostock Max V2?
#1
Id love to install this, but loathe to take my printer offline, especially as I suspect I will need to print some parts to make it fit which wont be evident till later! 

What I can't get my head around is physically, how am I meant to wire in the extra extruder? The stock Rostock runs all the wires in the pillars with no room to spare. I dont want to have a bunch of wires just hanging off the side.. how did others tackle this on an already built Rostock. 

Im also unsure what effector platform to print out first or what exactly a "flying config" is or why I need it. 


Currently Im using the Rostock v3 balljoint arms and ball joint hot molded platform  with a Prometheus V2 hotend. Some pictures of the Prometheus System on a Rostock V2 would help heaps!
 
Reply
#2
Well, I've installed it all physically, recalibrated the Rostock after changing to a "flying mount" setup, which took hours as usual. At the point of trying to setup Simplify3D.. holy crap the steps in the User guide are incomplete.The terminology is different in the program, it talks about bulk editing process which doesnt seem to work (or explain how), "Primary Extruder" setting in Layer tab only has.. "Primary Extruder" as an option, not Extruder 1/2 as per User Guide..

Any updated, corrected instructions?


thanks
 
Reply
#3
@kodachrome

We just added some explanation to that part of the instructions. Note that that last step you were referencing is not necessary for using the S3D Dual Extrusion Wizard for dual color prints. You can skip it. Please follow the instructions in the User Guide and you will find that the process is actually very quick and easy!
 
Reply
#4
Thanks for getting back to me. The Wizard was erroring out, I hadnt realised in addition to the FRM import for Firmware config, I need to use (and import) a custom process FFF file too. I guess its a matter of tweaking the settings based on my library of known good settings for various filaments, pity S3D isnt smart enough to allow pairing of existing processes.

Ill go try it out now anyhow!

Ok, after getting the dual extrusion wizard to open, adding some random models, click ok then...

File Error: Unable to import firmware settings from selected location.


It appears the FilaSwitch_PRO_V2.fff profile is set to override the Firmware config (and set to standard 1 extruder RepRap) by default. Ive unticked that option and the error is gone, but which setting is correct?


PS: How do you print 1 model with support but with two extruders ? The wizard requires two models and doesnt count support as a model.. ? I guess to do that you don't use the wizard and set the Support Extruder to #2 (or whatever), anything else?
 
Reply
#5
(09-13-2017, 09:48 AM)kodachrome Wrote: Thanks for getting back to me. The Wizard was erroring out, I hadnt realised in addition to the FRM import for Firmware config, I need to use (and import) a custom process FFF file too.  I guess its a matter of tweaking the settings based on my library of known good settings for various filaments, pity S3D isnt smart enough to allow pairing of existing processes.

Ill go try it out now anyhow!

Ok, after getting the dual extrusion wizard to open, adding some random models, click ok then...

File Error: Unable to import firmware settings from selected location.


It appears the FilaSwitch_PRO_V2.fff profile is set to override the  Firmware config (and set to standard 1 extruder RepRap) by default. Ive unticked that option and the error is gone, but which setting is correct?


PS: How do you print 1 model with support but with two extruders ? The wizard requires two models and doesnt count support as a model.. ?  I guess to do that you don't use the wizard and set the Support Extruder to #2 (or whatever), anything else?

Still trying!

Terminology is still inconsistent:
The user guide still calls the Extruders 1 and 2, when Simplify 3D calls them Tool 0 and 1. This should be consistent one way or another.

The processed GCode file name is not "your-g-code_fs", I assume you mean something like 
""XXXX_fs.gcode" , where XXXX is your file name."


Other problems:
Going in and editing the processes, Simplify3D keeps looking to add a Unique ID for each Temp sensor, which when allowed creates a dummy "Extruder 1 Temperature" in the temp tab. Not sure if its doing anything good or bad. 

Critical Failure:
But the worst is... I swear Im following the guide, trying to print the keychain, loading ("preview gcode"?) the processed gcode but the printer keeps going down to the print bed, prints for 1sec, goes home, goes down to bed, goes home in a loop!!

Attached is my GCode file, can you see whats going wrong?


Attached Files
.zip   Keychain_1_fs.zip (Size: 144.29 KB / Downloads: 2)
 
Reply
#6
@kodachrome

Sorry for your trouble. Please note that you should familiarize yourself with Simplify3D before trying to print dual color prints with the software. S3D has a high learning curve as-is, and that is made more difficult with the dual color printing. That being said, the instructions are properly laid out and outline the necessary steps for users who are familiar with the software.

The G-code file looks fine. Have you tried printing with a single color with S3D? You need to get that working with your printer before you can move to dual extrusion. That will save you A LOT of time with troubleshooting.

I hope this helps!
 
Reply
#7
Well no, thats not super helpful! 
Ive been exclusively an S3D user since March 2015 and part of their beta program. I can print single colours with the Prometheus System (and the 2 Prometheus Hotends I bought prior) just fine. 
Thats why Im pointing out the array of inconsistencies in your guide vs S3D.  Also in this case we are integrating 3rd party gcode tweaking back into S3D which introduces non-S3D quirks.
Id suggest you maybe make a video of exactly how you are printing the keychain in S3D, it would be far more useful than the adhoc text. You'd also spot all the different terms and unmentioned error/notice messages that pop up. Wink
Also verify your guide (and 3rd party gcode) is compatible with S3D 4.0 as it explicitly mentions 3.1 which has been replaced.
 
Reply
#8
Looking at the g-code, I see few things:
- hot end temp is set to 290, is this really needed? Doesn't really matter regards the movement problems, but curious as the material is set to PETG.
- bed temperature is not set properly (M140 S[bed0_temperature]), Again, should not affect the movement but should be addressed for future
- check that the machine type matches your printer, i.e. set to Delta or Cartesian
- check that the bed dimensions are correct. In the g-code there are negative coordinates, I assume your bed 0,0 position is set to center of the bed and matches what the firmware thinks. I had weird movements when accidentally trying to print g-code that has coordinates out of the printers limits...

As for the use of external program: since S3D doesn't support this kind of hw setup out of the box, that's kind of only option. And it seems S3D isn't planning on supporting it any time soon so meh.

S3D in general: getting it configured right, especially with dual color prints, requires some getting used to. The dual color wizard works quite well, but can still cause some weird problems now and the if changing the profiles after the wizard.
 
Reply
#9
(09-14-2017, 09:47 AM)spegelius Wrote: Looking at the g-code, I see few things:
- hot end temp is set to 290, is this really needed? Doesn't really matter regards the movement problems, but curious as the material is set to PETG.
- bed temperature is not set properly (M140 S[bed0_temperature]), Again, should not affect the movement but should be addressed for future
- check that the machine type matches your printer, i.e. set to Delta or Cartesian
- check that the bed dimensions are correct. In the g-code there are negative coordinates, I assume your bed 0,0 position is set to center of the bed and matches what the firmware thinks. I had weird movements when accidentally trying to print g-code that has coordinates out of the printers limits...

Thanks for the tips. 

- Yes, 290 is needed as I only have PC to print with as a test here. I wanted to get it working before buying something more suitable/usable.
- Not sure on the bed temp.. Im not doing anything exotic, just selecting it in Temp tab as normal in the process?? What should I be doing?
- Machine type (in General Options) is delta etc, however you are aware your FFF profile is set to override machine type values? Ive disabled that, but it was catching me out originally. Your settings are way off for a Rostock, probably shouldnt force them "on" in all machines that use your FFF!
- bed dimensions are set as per standard rostock settings and also as per the Config Wizard in Simplify3d (4) which now lists the Rostock. 

Ive tried about 8 times now, clearing/removing FFF and FRM settings, doing it from scratch. Exactly the same each time, the printer head bounds up and down, tried to print, up/down again etc. So frustrating. 

Here is the gcode comms during the attempted print, note the Format Read Errors.. unsure on their significance:

Code:
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: Fanspeed:255
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M105
SENT: M190 S[bed0_temperature]
READ: Fanspeed:0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: TargetExtr0:260
READ: ok 0
READ: T:258.57 B:69.81 B@:182 @:255 T0:258.57 @0:255 T1:258.57 @1:0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: Fanspeed:255
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M190 S[bed0_temperature]
READ: Fanspeed:0
READ: ok 0
READ: TargetExtr0:260
READ: ok 0
SENT: M109 S260  T0
READ: ok 0
SENT: G28
SENT: G90
SENT: G92 E0
SENT: G1 Z0.500 F12000
SENT: G1 X-27.400 Y26.646 F12000
READ: ok 0
READ: Fanspeed:255
READ: ok 0
READ: ok 0
SENT: G1 Z0.2 F12000
SENT: G91
READ: Fanspeed:0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: TargetExtr0:260
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: ok 0
READ: TargetExtr0:260
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: ok 0
SENT: M105
READ: ok 0
READ: ok 0
SENT: M190 S[bed0_temperature]
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M109 S260  T0
READ: ok 0
SENT: G28
SENT: G90
SENT: G92 E0
SENT: G1 Z0.500 F12000
SENT: G1 X-27.400 Y26.646 F12000
READ: ok 0
READ: Fanspeed:255
READ: ok 0
READ: ok 0
SENT: M105
READ: Fanspeed:0
READ: ok 0
SENT: G1 Z0.2 F12000
SENT: G91
READ: TargetExtr0:260
READ: ok 0
SENT: G1 X54.800 E2.1920 F2000
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: ok 0
READ: TargetExtr0:260
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: ok 0
SENT: M105
READ: ok 0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: ok 0
READ: ok 0
SENT: M105
READ: ok 0
SENT: M190 S[bed0_temperature]
READ: ok 0
READ: Fanspeed:255
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: ok 0
READ: ok 0
SENT: M105
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M190 S[bed0_temperature]
READ: Fanspeed:0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: TargetExtr0:260
READ: ok 0
READ: T:260.56 B:69.92 B@:178 @:201 T0:260.56 @0:201 T1:260.56 @1:0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: Fanspeed:255
READ: ok 0
READ: ok 0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: ok 0
READ: ok 0
SENT: M105
READ: Fanspeed:0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: TargetExtr0:260
READ: ok 0
READ: ok 0
READ: Fanspeed:255
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: ok 0
READ: ok 0
READ: Fanspeed:0
READ: ok 0
SENT: M190 S[bed0_temperature]
READ: TargetExtr0:260
READ: ok 0
READ: ok 0
SENT: M109 S260  T0
READ: ok 0
SENT: G28
SENT: G90
SENT: G92 E0
SENT: G1 Z0.500 F12000
SENT: G1 X-27.400 Y26.646 F12000
READ: Fanspeed:255
READ: ok 0
READ: ok 0
READ: Fanspeed:0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: TargetExtr0:260
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
READ: Fanspeed:255
READ: ok 0
READ: ok 0
READ: ok 0
SENT: M190 S[bed0_temperature]
READ: Fanspeed:0
READ: Error:Format error
READ:
READ: Resend:1
READ: ok
SENT: G90
SENT: M83
SENT: M106 S255
SENT: G4 P500
SENT: M106 S0
SENT: M104 S260  T0
READ: TargetExtr0:260
READ: ok 0
READ: TargetExtr0:260
READ: ok 0
READ: ok 0
SENT: M140 S[bed0_temperature]
SENT: M112
Total build time: 0.29 minutes
Disconnected.
Emergency stop issued! Attempting to reconnect...
 
Reply
#10
SENT: M190 S[bed0_temperature]
READ: Fanspeed:0
READ: Error:Format error

That M190 line should be "M190 S60" (or whatever the bed temperature is supposed to be).
[bed0_temperature] is S3D internal variable and for some reason it's not converted to actual numeric value.
I'd check the temperature section for the bed and also check what the S3D variable name should be. I don't think S3D has those handily available anywhere...?

I haven't used that FFF profile myself, I have cartesian printer with RAMPS/Marlin and I usually configure my profiles from scratch. I kinda expect the provided FFF profile to be a baseline that one can use as reference, not something to use without tuning it first.
 
Reply
  


Forum Jump:


Browsing: 1 Guest(s)