Closed kscheff closed 8 years ago
The issue might be related to the Slic3r settings. When using Simplify3D the sizes and speeds seem to match. I have set the extrusion multiplier in Simplify3D to 1.25, so there might bas till some differences on the extruder steps/mm despite the extruder itself looks very much the same to the UP Mini one.
So you can use the transcoder for the Cetus? Do you send data to it by typing cetus in stead of box, mini or plus?
@Gitty-Hub Yes, but this version is not yet released here. You may take a look in https://github.com/UP3D-gcode/UP3D in the future to get this support. You have a Cetus3D on your desk?
I added basic support for cetus today based on your findings.
Let's work out pull requests to merge more of your work.
Maik
Hi, I have an Cetus3D prototype and it reports back a different PID. System info tells me:
So I modified up3dcomm.c to incorporate the new PID to see what it reports. Here is the result:
Not sure what all the information should tell me, but I like to build support for this this printer into the transcoder.
Update: I extended the the setting in up3dtranscode for the Cetus. Mainly I copied the mini settings and changed the resolution to 160 steps/mm for yxz. Running the transcoder and uploading it to the Cetus works. Printing starts work, but I get some way to high speed during infill,e.g. it seems at least a factor 3 too high. Brim, first Layer, Perimeters and top layer are OK. Only the wired infill speed.
I use the newest Slic3r 1.2.9 on OS-X. Transcoding for the UP! Mini works without this speedy infill.