Refer to the remap.ini link at the top of the fdm-gcode page. You should also be familiar with the content of the integrator manual:
http://www.machinekit.io/docs/index-integrator/ ...and remapping in general: http://www.machinekit.io/docs/remap/structure/ Note that my machine configurations are pretty old and are not currently setup to use remapped codes. Instead I post-process the gcode files produced for more mainstream "RepRap" 3D printer controllers (eg: the various Arduino and Cortex-M controllers) to make it compatible with Machinekit's gcode support. The RepRap folk have somewhat haphazardly extended "conventional" gcode for 3D printing. On 1/21/2019 12:39 PM, Ömür Ceran wrote: > Thank you for you answer charles,but ı am new at linux,so can you explain > specifically how can ı add subroutines? > > 21 Ocak 2019 Pazartesi 21:18:36 UTC+3 tarihinde Charles Steinkuehler yazdı: >> >> On 1/21/2019 1:29 AM, Ömür Ceran wrote: >>> Hello, >>> I was trying to make a 3d printer but when I try to print any 3d model >> it >>> gives an unknown M code problem. I search it on internet and I found >> that >>> it is extruder temperature code. How can I solve this problem? Also I >> want >>> to ask you a question about files format for machinekit. Is it used only >>> with .ngc file format ? Because I want to print 3d model which file >> format >>> is .stl, I have to convert it .ngc file format therefore I should use a >>> program which is extension at Cura program whose name is NGCwriter. >> After >>> converting .stl file to .ngc file format, machinekit gives temperature >>> problem again(unknown M104 code problem). >> >> You need to add subroutines and remap the missing M codes: >> >> http://www.machinekit.io/docs/fdm/fdm-gcode/ >> >>> Also I have another question, I want to make CoreXY machine, but my >>> configuration is CoreXZ which is taken from Charles Steinkuehler >>> configuration. How can I convert from CoreXZ to CoreXY? >>> Which option should I use that are given below? >>> >>> Option 1 : Changing the Y and Z axis pins physically on the BBB. >>> Option 2 : Changing the Y and Z axis on the code which is in the .hal >> file >>> if it is necessary. >>> Option 3 : If you have a CoreXY configuration, can you send me it with >>> installing explanation? >> >> Change the HAL file (option 2). >> >> Swap the axis.2.motor-pos-cmd/fb signals (the Z axis) with >> axis.1.motor-pos-cmd/fb (the Y axis). >> >> The *-cmd signals are the desired motor position driven by the motion >> planner. The *-fb signals are the current physical motor position. >> >> The CoreXY module is between the motion controller (axis.N.motor- >> signals) and the stepper driver signals (corexz.X/corexz.Y) and >> performs the simple math needed for CoreXY type machines in both the >> command and feedback directions. >> >> -- >> Charles Steinkuehler >> [email protected] <javascript:> >> > -- Charles Steinkuehler [email protected] -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
