Fusion 360 & post processor

New Home Forum Software / Firmware Development Fusion 360 & post processor

This topic contains 402 replies, has 78 voices, and was last updated by  Ryan 2 days, 22 hours ago.

Viewing 30 posts - 361 through 390 (of 403 total)
  • Author
    Posts
  • #95854

    Guffy
    Participant

    As i remember the post processor doesn’t issue M80. It’s power supply management command for 3d printers and it’s usually not useful for cnc.

    Same for m140. So i have no idea what gcode you was running

    #95856

    Bobby
    Participant

    Yeah, I think those two were from the hosts, I tried both Repetier and Simplify3D. M80 was from Repetier and M140 was from Simplify. G21 unknown happened both times as it was in the gcode itself from post. I looked in the firmware as-released and it looks like G21 might be disabled?

    // G20/G21 Inch mode support
    //
    //#define INCH_MODE_SUPPORT

    #95861

    Guffy
    Participant

    G21 is switching machine to metric mode. I guess marlin must handle it.

    Anyway if your design is in metric then it should work well

    #95864

    Bobby
    Participant

    I’m not sure any of those errors were fatal like I thought anyway, turns out it was just waiting for me to confirm spindle-on with the LCD which I hadn’t installed yet. Lol. Up and running now, thanks!

    #100859

    Edward
    Participant

    I’m having trouble setting something up, either with Fusion or the post processor.

    The gcode is being sent by Repetier Host to a RAMPS board over USB.

    The file mills perfectly, but incredibly slowly.  It seems to be moving along in very small steps when milling.  Travel moves are quick, and so are straight sections of milling.  I’ve set it up to enforce the feedreate, and there is an F900 at the end of each G1/G2/G3 command.

    The file generated from Fusion has 21000 lines of code, while the same design run through Estlcam is only 640 lines.  The Estlcam file is milling in about 2 minutes, while the Fusion file takes about 10.  Both look the same in the end.

    I’m obviously doing something wrong, but so far what it is is eluding me.

    #100866

    Jeffeb3
    Participant

    Do you have adaptive milling turned on? The high resolution of the gcode is why it’s slow. You might get faster by running straight from the SD/LCD, but ithas to transmit those 21k lines a few at a time over a slow connection.

    #100871

    Edward
    Participant

    This is a contouring run.  I tried it with both pocket and contour and got similar file sizes.  Turning down the tolerance helped reduce the line count, but then you get nasty looking curves and you miss bits.

    I can’t help but think there’s a little check box, tucked away under a drop down menu, in a separate tab, that I need to clear.

    An SD card and screen might be the solution, but the 32 – 1 line count can’t be normal.

    #100874

    Guffy
    Participant

    the post processor is pretty verbose in comments by default. usually it’s not a problem because comments take a few percents of a file. but yo can turn comments off.

    also a few screenshots can be handy

    #100897

    Edward
    Participant

    I’m positive now that it’s Fusion cutting the curves into remarkably small line segments.  I’ve turned off all the comments in the post processor.

    There is a mention of the problem in the Autodesk Knowledge Network, they suggest setting the compensation to “in control” from “in computer”.  The trouble is that this requires lead in and lead out, but when I turn those on it decides it can’t get the tool into the pockets and doesn’t generate toolpaths properly.

    I’m going to take this to an Autodesk forum, sorry for putting it here.

    *EDIT*

    I posted the issue in the Autodesk forum and got an instant reply to turn on Smoothing in the Passes tab at 0.02mm.  My line count dropped from 21000 to 1240.  Still not as efficient as Estlcam, but very workable.

     

     

    1 user thanked author for this post.
    #101052

    Bill Vance
    Participant

    Hi guys, I was hoping for a little help with Fusion 360 pp.

    First some basics: Standard MPCNC, no lcd, no modifications, not using duel endstops, 18×18 build area. I can run gcode from ESTLcam without problems and can manually jog through repetier without issues.

    I’ve downloaded the newest version of the pp, have it installed and it seems to be working to spit out a proper G-Code.  I then open the file in repetier, make sure its on the board and look at the travel and all seems right. Repetier list the print time as 1 Minute 1 second (just a test square), before I hit start. Once I start the print, a little g-code runs through the bottom window but nothing happens.  The ETE in the bottom right lists 53 seconds.  There are some errors in the code listed, G20 and M80 but those look the same as what Bobby listed above.  I don’t have an LCD hooked up so I can’t tell if its just waiting on a verification like Bobby’s was.  Is there any way to see on a computer what would be displayed on the LCD? If it is waiting on a confirmation, can this be taken out of the code?  I don’t have any tool changes listed so I don’t have a need for a pause.

    I’ve listed what was in the log below.

    Thanks!

    18:08:38.285 : Preferred name from C:\Users\dell\Desktop\try 2.gcode to try 2
    18:08:38.466 : OpenGL version:4.4.0 – Build 20.19.15.4835
    18:08:38.466 : OpenGL extensions:GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_blend_color GL_EXT_abgr GL_EXT_texture3D GL_EXT_clip_volume_hint GL_EXT_compiled_vertex_array GL_SGIS_texture_edge_clamp GL_SGIS_generate_mipmap GL_EXT_draw_range_elements GL_SGIS_texture_lod GL_EXT_rescale_normal GL_EXT_packed_pixels GL_EXT_texture_edge_clamp GL_EXT_separate_specular_color GL_ARB_multitexture GL_ARB_map_buffer_alignment GL_ARB_conservative_depth GL_EXT_texture_env_combine GL_EXT_bgra GL_EXT_blend_func_separate GL_EXT_secondary_color GL_EXT_fog_coord GL_EXT_texture_env_add GL_ARB_texture_cube_map GL_ARB_transpose_matrix GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_texture_env_add GL_IBM_texture_mirrored_repeat GL_ARB_texture_mirrored_repeat GL_EXT_multi_draw_arrays GL_SUN_multi_draw_arrays GL_NV_blend_square GL_ARB_texture_compression GL_3DFX_texture_compression_FXT1 GL_EXT_texture_filter_anisotropic GL_ARB_texture_border_clamp GL_ARB_point_parameters GL_ARB_texture_env_combine GL_ARB_texture_env_dot3 GL_ARB_texture_env_crossbar GL_EXT_texture_compression_s3tc GL_ARB_shadow GL_ARB_window_pos GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_ARB_vertex_program GL_EXT_texture_rectangle GL_ARB_fragment_program GL_EXT_stencil_two_side GL_ATI_separate_stencil GL_ARB_vertex_buffer_object GL_EXT_texture_lod_bias GL_ARB_occlusion_query GL_ARB_fragment_shader GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_texture_non_power_of_two GL_ARB_vertex_shader GL_NV_texgen_reflection GL_ARB_point_sprite GL_ARB_fragment_program_shadow GL_EXT_blend_equation_separate GL_ARB_depth_texture GL_ARB_texture_rectangle GL_ARB_draw_buffers GL_ARB_color_buffer_float GL_ARB_half_float_pixel GL_ARB_texture_float GL_ARB_pixel_buffer_object GL_ARB_texture_barrier GL_EXT_framebuffer_object GL_ARB_draw_instanced GL_ARB_half_float_vertex GL_ARB_occlusion_query2 GL_EXT_draw_buffers2 GL_WIN_swap_hint GL_EXT_texture_sRGB GL_ARB_multisample GL_EXT_packed_float GL_EXT_texture_shared_exponent GL_ARB_texture_rg GL_ARB_texture_compression_rgtc GL_NV_conditional_render GL_ARB_texture_swizzle GL_EXT_texture_swizzle GL_ARB_texture_gather GL_ARB_sync GL_ARB_cl_event GL_ARB_framebuffer_sRGB GL_EXT_packed_depth_stencil GL_ARB_depth_buffer_float GL_EXT_transform_feedback GL_ARB_transform_feedback2 GL_ARB_draw_indirect GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_ARB_framebuffer_object GL_ARB_framebuffer_no_attachments GL_EXT_texture_array GL_EXT_texture_integer GL_ARB_map_buffer_range GL_ARB_texture_buffer_range GL_EXT_texture_snorm GL_ARB_blend_func_extended GL_INTEL_performance_query GL_ARB_copy_buffer GL_ARB_sampler_objects GL_NV_primitive_restart GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_uniform_buffer_object GL_ARB_depth_clamp GL_ARB_vertex_array_bgra GL_ARB_shader_bit_encoding GL_ARB_draw_buffers_blend GL_ARB_geometry_shader4 GL_EXT_geometry_shader4 GL_ARB_texture_query_lod GL_ARB_explicit_attrib_location GL_ARB_draw_elements_base_vertex GL_EXT_shader_integer_mix GL_ARB_instanced_arrays GL_ARB_base_instance GL_ARB_fragment_coord_conventions GL_EXT_gpu_program_parameters GL_ARB_texture_buffer_object_rgb32 GL_ARB_compatibility GL_ARB_texture_rgb10_a2ui GL_ARB_texture_multisample GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_timer_query GL_EXT_timer_query GL_ARB_tessellation_shader GL_ARB_vertex_array_object GL_ARB_provoking_vertex GL_ARB_sample_shading GL_ARB_texture_cube_map_array GL_EXT_gpu_shader4 GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_INTEL_fragment_shader_ordering GL_ARB_fragment_shader_interlock GL_ARB_clip_control GL_ARB_shader_subroutine GL_ARB_transform_feedback3 GL_ARB_get_program_binary GL_ARB_separate_shader_objects GL_ARB_shader_precision GL_ARB_vertex_attrib_64bit GL_ARB_viewport_array GL_ARB_transform_feedback_instanced GL_ARB_compressed_texture_pixel_storage GL_ARB_shader_atomic_counters GL_ARB_shading_language_packing GL_ARB_shader_image_load_store GL_ARB_shading_language_420pack GL_ARB_texture_storage GL_EXT_texture_storage GL_ARB_compute_shader GL_ARB_vertex_attrib_binding GL_ARB_texture_view GL_ARB_fragment_layer_viewport GL_ARB_multi_draw_indirect GL_ARB_program_interface_query GL_ARB_shader_image_size GL_ARB_shader_storage_buffer_object GL_ARB_texture_storage_multisample GL_ARB_buffer_storage GL_AMD_vertex_shader_layer GL_AMD_vertex_shader_viewport_index GL_ARB_query_buffer_object GL_EXT_polygon_offset_clamp GL_ARB_clear_texture GL_ARB_texture_mirror_clamp_to_edge GL_ARB_debug_output GL_ARB_enhanced_layouts GL_KHR_debug GL_ARB_arrays_of_arrays GL_ARB_texture_query_levels GL_ARB_invalidate_subdata GL_ARB_clear_buffer_object GL_INTEL_map_texture GL_ARB_texture_compression_bptc GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_robustness GL_ARB_robust_buffer_access_behavior GL_EXT_texture_sRGB_decode GL_ARB_copy_image GL_KHR_blend_equation_advanced GL_EXT_direct_state_access GL_ARB_stencil_texturing GL_ARB_texture_stencil8 GL_ARB_explicit_uniform_location GL_ARB_multi_bind GL_ARB_indirect_parameters
    18:08:38.466 : OpenGL renderer:Intel(R) HD Graphics 5500
    18:08:38.466 : Using fast VBOs for rendering is possible
    18:08:42.828 : Printer reset detected – initalizing
    18:08:42.831 : start
    18:08:42.831 : echo:Marlin bugfix-2.0.x
    18:08:42.832 : echo: Last Updated: 2018-01-20 | Author: (V1 Engineering, Ryan, 302)
    18:08:42.832 : echo:Compiled: Apr 5 2019
    18:08:42.836 : echo: Free Memory: 3635 PlannerBufferBytes: 1488
    18:08:42.836 : echo:Hardcoded Default Settings Loaded
    18:08:42.836 : echo: G21 ; Units in mm (mm)
    18:08:42.840 : echo: M149 C ; Units in Celsius
    18:08:42.840 : echo:Filament settings: Disabled
    18:08:42.840 : echo: M200 D3.00
    18:08:42.840 : echo: M200 D0
    18:08:42.844 : echo:Steps per unit:
    18:08:42.844 : echo: M92 X100.00 Y100.00 Z400.00 E100.00
    18:08:42.844 : echo:Maximum feedrates (units/s):
    18:08:42.848 : echo: M203 X120.00 Y120.00 Z30.00 E25.00
    18:08:42.848 : echo:Maximum Acceleration (units/s2):
    18:08:42.852 : echo: M201 X400.00 Y400.00 Z200.00 E2000.00
    18:08:42.856 : echo:Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel>
    18:08:42.856 : echo: M204 P400.00 R3000.00 T400.00
    18:08:42.860 : echo:Advanced: B<min_segment_time_us> S<min_feedrate> T<min_travel_feedrate> J<junc_dev>
    18:08:42.860 : echo: M205 B20000.00 S0.00 T0.00 J0.00
    18:08:42.860 : echo:Home offset:
    18:08:42.864 : echo: M206 X0.00 Y0.00 Z0.00
    18:08:42.864 : echo:Material heatup parameters:
    18:08:42.864 : echo: M145 S0 H196 B92 F0
    18:08:42.868 : echo: M145 S1 H240 B110 F0
    18:08:42.869 : echo:PID settings:
    18:08:42.869 : echo: M301 P17.98 I0.98 D83.62
    18:08:43.084 : N1 M110*34
    18:08:43.084 : N2 M115*36
    18:08:43.084 : N3 M105*36
    18:08:43.084 : N4 M114*35
    18:08:43.084 : N5 M111 S6*98
    18:08:43.085 : N6 T0*60
    18:08:43.085 : N7 M20*22
    18:08:43.086 : N8 M80*19
    18:08:46.076 : N9 M105*46
    18:08:48.461 : N10 M220 S100*80
    18:08:48.466 : FIRMWARE_NAME:Marlin bugfix-2.0.x (Github) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:V1 E CNC EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
    18:08:48.467 : Cap:SERIAL_XON_XOFF:0
    18:08:48.468 : Cap:EEPROM:0
    18:08:48.468 : Cap:VOLUMETRIC:1
    18:08:48.468 : Cap:AUTOREPORT_TEMP:1
    18:08:48.468 : Cap:PROGRESS:0
    18:08:48.468 : Cap:PRINT_JOB:1
    18:08:48.469 : Cap:AUTOLEVEL:0
    18:08:48.469 : Cap:Z_PROBE:0
    18:08:48.469 : Cap:LEVELING_DATA:0
    18:08:48.469 : Cap:BUILD_PERCENT:0
    18:08:48.469 : Cap:SOFTWARE_POWER:0
    18:08:48.469 : Cap:TOGGLE_LIGHTS:0
    18:08:48.472 : Cap:CASE_LIGHT_BRIGHTNESS:0
    18:08:48.472 : Cap:EMERGENCY_PARSER:0
    18:08:48.472 : Cap:AUTOREPORT_SD_STATUS:0
    18:08:48.472 : Cap:THERMAL_PROTECTION:1
    18:08:48.472 : Cap:MOTION_MODES:1
    18:08:48.473 : N11 M221 S100*80
    18:08:48.496 : N12 M111 S6*84
    18:08:48.509 : X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
    18:08:48.511 : N13 T0*8
    18:08:48.524 : echo:DEBUG:INFO,ERRORS
    18:08:48.524 : N14 M155 S1*85
    18:08:48.528 : Begin file list
    18:08:48.531 : End file list
    18:08:48.532 : echo:Unknown command: “M80”
    18:08:48.533 : echo:DEBUG:INFO,ERRORS
    18:09:25.309 : N15 G90*36
    18:09:25.310 : N16 G21*45
    18:09:25.310 : N17 M84 S0*106
    18:09:25.315 : N18 G92 X0 Y0 Z0*96
    18:09:25.315 : N19 M0 Attach ZProbe*32
    18:09:25.317 : N20 G28 Z0*107
    18:09:25.318 : N21 G92 Z0.8*125
    18:09:25.324 : echo:Unknown command: “G21”
    18:09:25.327 : X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
    18:09:25.328 : N22 G0 Z40 F300*50
    18:09:25.328 : N23 M400*22
    18:09:25.328 : N24 M0 Detach ZProbe*58

    #101061

    Jeffeb3
    Participant

    18:09:25.310 : N16 G21*45
    18:09:25.310 : N17 M84 S0*106
    18:09:25.315 : N18 G92 X0 Y0 Z0*96
    18:09:25.315 : N19 M0 Attach ZProbe*32
    18:09:25.317 : N20 G28 Z0*107
    18:09:25.318 : N21 G92 Z0.8*125
    18:09:25.324 : echo:Unknown command: “G21”

    I think the *45 is a checksum. I don’t usually have checksums or line numbers (N16) in my gcode. Is there a checkmark to turn those off?

    1 user thanked author for this post.
    #101062

    Brock
    Participant

    Hi Bill,

    I think the issue is:

    18:09:25.315 : N19 M0 Attach ZProbe*32

    M0 is the pause command
    http://marlinfw.org/docs/gcode/M000-M001.html

    You should disable this in the post processor in fusion.

    If you can’t or you want to test it then you could send M108 from repetier:

    http://marlinfw.org/docs/gcode/M108.html

    • In the case of M0 the M108 command acts like the LCD button, breaking out of M0 and continuing to process the G-code queue.

    1 user thanked author for this post.
    #101092

    Jan
    Participant

    I am trying to include an external file for the probe, as defined in “Extern: Probe File”, but that does not seem to do anything.

    What am I missing there?

    #101093

    Bill Vance
    Participant

    Thanks guys.  I deleted the M0 line and it ran fine.  I’ll have to check the PP when I get back to my other computer to see if you can turn it off.

    This place is the best!

    Bill

    #101124

    Guffy
    Participant

    post processor is primarily designed to work with SD card + LCD. So it issues M0 gcode commands  to pause execution.
    to work with repetier host you may manually replace “M0 some display message” to @pause
    https://forum.repetier.com/discussion/2053/how-to-insert-a-pause-in-gcode

    1 user thanked author for this post.
    #101254

    Brock
    Participant

    You could setup one of the custom code buttons in repetier to issue M108 and use it as an LCD button and save you having to remember the gcode. The custom buttons are the numbers ones in the middle on the manual control page.

    1 user thanked author for this post.
    #101256

    Bill Vance
    Participant

    Guffy- Thank you for the explanation. All of my past experience with G-Code is with out of the box software so I had no reason to know the ins and outs.  Thank you for putting the PP together, not only is the CNC world learning curve steep but holy cow I feel like Fusion 360 is even steeper, and you’ve been a huge help.

    Brock- That’s a great idea, I’ll give programming that button a try tonight so I don’t have to edit the code every time.

    #101533

    Guffy
    Participant

    also I have found that for headless configuration you can try to enable in Marlin a feature to inform host software about particular actions.
    I didn’t try it, but you may try to use it in your firmware.

    
    /**
     * Host Action Commands
     *
     * Define host streamer action commands in compliance with the standard.
     *
     * See https://reprap.org/wiki/G-code#Action_commands
     * Common commands ........ poweroff, pause, paused, resume, resumed, cancel
     * G29_RETRY_AND_RECOVER .. probe_rewipe, probe_failed
     *
     * Some features add reason codes to extend these commands.
     *
     * Host Prompt Support enables Marlin to use the host for user prompts so
     * filament runout and other processes can be managed from the host side.
     */
    //#define HOST_ACTION_COMMANDS
    #if ENABLED(HOST_ACTION_COMMANDS)
      //#define HOST_PROMPT_SUPPORT
    #endif
    
    #103298

    Tyler
    Participant

    Would there be any reason that when using F360 my z axis would be off. I have depth of pass set to 2mm and it is plunging at least twice that much. My X and Y are spot on but the Z is off and I am not sure why. I can post some of the gcode if necessary but was wondering if I need to edit something in the post processor that I am missing.

    #103299

    Ryan
    Keymaster

    When you manually move it 20mm is exactly 20mm?

    A PP can’t really mess up one axis by a simple mistake, usually all would be messed up.

    #103337

    Tim
    Participant

    Would there be any reason that when using F360 my z axis would be off. I have depth of pass set to 2mm and it is plunging at least twice that much. My X and Y are spot on but the Z is off and I am not sure why. I can post some of the gcode if necessary but was wondering if I need to edit something in the post processor that I am missing.

    Is your work offset setup properly in Fusion?
    Which strategy are you using? Is it possible you have the roughing stepdown set to 4mm and the fine stepdown set to 2mm?

    #103616

    Tyler
    Participant

    XY step perfectly. Work offsets look fine. First pass cuts ~2mm, second pass lifts up to top of piece and then plunges further than it should. So kinda odd.

    #103621

    Tim
    Participant

    XY step perfectly. Work offsets look fine. First pass cuts ~2mm, second pass lifts up to top of piece and then plunges further than it should. So kinda odd.

    Post your F3d file if possible, I’ll take a look

    #103623

    Ryan
    Keymaster

    Yeah typically that is poor rapids on the Z axis, meaning it is not actually picking up as far as you want and plunging 2mm from there.

    #103636

    Tyler
    Participant

    This is just my test file to dial in my settings. Let me know if you see anything I need to change. It was saying that f3d filetypes are not allowed to be uploaded so here is a zip.

     

    Here are my tool settings. Settingshttps://imgur.com/a/EkdTLyv

    Attachments:
    1. Tester1-v1.zip
    1 user thanked author for this post.
    Tim
    #103641

    Ryan
    Keymaster

    What are your rapids, and gcode would be a better choice of file.

    #103642

    Tim
    Participant

    This is just my test file to dial in my settings. Let me know if you see anything I need to change. It was saying that f3d filetypes are not allowed to be uploaded so here is a zip.

    Here are my tool settings. Settingshttps://imgur.com/a/EkdTLyv

    which operation is the one that it’s plunging too deep on? Your cam looks great. Plunge feedrate is set to 180mm/min which is fine.

    There is a setting in the post processor window called “Travel Speed Z” which is supposed to limit all z axis move speeds.

    Is it possible that the area on your work where you’re picking up your origin is warped so your first cut LOOKS like it’s roughly 2mm (but maybe actually only 1mm) then the second pass is actually 2mm thus making it look twice as deep the second pass?

    I assume you’ve run a stock simulation on your actual Fusion CAM to rule out CAM completely?

    Next step I suppose would be posting the gcode in question to rule out the post processor. You should be pretty easily able to look at the Z that it’s calling for and the feed rate.

    #103645

    Tyler
    Participant

    Ill try running it again tonight and seeing if Im crazy haha. I didn’t think CAM was my problem but wanted to rule it out. I will look into that Travel Speed Z before I run tonight/tomorrow and see what I find.

    #103647

    Tim
    Participant

    Ill try running it again tonight and seeing if Im crazy haha. I didn’t think CAM was my problem but wanted to rule it out. I will look into that Travel Speed Z before I run tonight/tomorrow and see what I find.

    The CAM in the file you sent me is perfectly configured so I don’t think it is your issue. Maybe something with the post. We’ll see how your test goes

    #103648

    Tyler
    Participant

    Is there a way to rough a part and then finish it? Or will it always follow its roughing pass with a finishing pass? When using Estlcam it will rough the part and then finish it after which I prefer but still not 100% familiar with the F360 settings.

Viewing 30 posts - 361 through 390 (of 403 total)

You must be logged in to reply to this topic.