at the circle pressure the pressure always stops



  • I make myself through various topics read here but still found no solution.

    my attitude are as follows:

    M584 X4 Y3:0 Z2:1 E5:6:7:8:9 ; Apply custom drive mapping
    M350 X64 Y64 Z64 E32:32:32:32:32 I0 ; Configure microstepping without interpolation
    M92 X1066.66 Y1066.66 Z6400 E953.00:953.00:953.00:953.00:953.00 ; Set steps per mm
    M566 X900.00 Y900.00 Z12.00 E900.00:900.00:900.00:900.00:900.00 ; Set maximum instantaneous speed changes (mm/min)
    M203 X18000.00 Y18000.00 Z800.00 E6000.00:6000.00:6000.00:6000.00:6000.00 ; Set maximum speeds (mm/min)
    M201 X400.00 Y400.00 Z10.00 E250.00:250.00:250.00:250.00:250.00 ; Set accelerations (mm/s^2)
    M906 X1800.00 Y1800.00 Z1800.00 E800.00:800.00:800.00:800.00:800.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    0_1556604333899_Schubladen-Teiler.gcode

    I would be happy about your help.

    greetings soon

    Michel



  • I have now found that I have the same problem synonymous with solid infill when the lines are about 12mm long and.

    with reduction of the speed I have the problem no more.

    It may be that I'm too high with the steps.

    I use spindles on all axes.

    thx



  • can you post some pictures? i dont quite understand what you mean.





  • @3dware said in at the circle pressure the pressure always stops:

    It may be that I'm too high with the steps.

    I think you're right.

    Can you post the results of M122 diagnostics? I think we'll see hiccups.

    @3dware said in at the circle pressure the pressure always stops:

    M350 X64 Y64 Z64 E32

    Try M350 X16 Y16 Z16 E16 I1 instead. This will use 16 microsteps for the calculation and interpolate the step pulses to 256 at the driver, which should be much quieter as well.

    You'll have to modify your M92 steps per mm to match x16 microsteps.



  • 16:49:08
    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03beta3 running on Duet WiFi 1.02 or later + DueX5
    Board ID: 08DGM-917DA-G4MSD-6J1F8-3SN6N-KSTM9
    Used output buffers: 3 of 20 (18 max)
    === RTOS ===
    Static ram: 25632
    Dynamic ram: 97108 of which 0 recycled
    Exception stack ram used: 472
    Never used ram: 7860
    Tasks: NETWORK(ready,564) HEAT(blocked,1172) MAIN(running,3732) IDLE(ready,196)
    Owned mutexes:
    === Platform ===
    Last reset 00:46:12 ago, cause: software
    Last software reset at 2019-04-30 16:02, reason: User, spinning module GCodes, available RAM 7856 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 8
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 26.3, current 26.6, max 26.9
    Supply voltage: min 23.8, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: ok, SG min/max 0/349
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: ok, SG min/max 49/399
    Driver 4: ok, SG min/max 78/367
    Driver 5: ok, SG min/max not available
    Driver 6: standstill, SG min/max not available
    Driver 7: standstill, SG min/max not available
    Driver 8: standstill, SG min/max not available
    Driver 9: standstill, SG min/max not available
    Date/time: 2019-04-30 16:49:07
    Cache data hit count 4294967295
    Slowest loop: 6.89ms; fastest: 0.09ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, FreeDm: 165, MinFreeDm: 158, MaxWait: 0ms
    Bed compensation in use: mesh
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === MainDDARing ===
    Scheduled moves: 788, completed moves: 784, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = 6 -1
    Heater 0 is on, I-accum = 0.1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 1, aux move: no
    Stack records: 2 allocated, 0 in use
    Movement lock held by null
    http is idle in state(s) 0
    telnet is idle in state(s) 0
    file is idle in state(s) 2
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 167.81ms; fastest: 0.08ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.21
      WiFi MAC address cc:50:e3:0d:1b:66
      WiFi Vcc 3.42, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 16344
      WiFi IP address 192.168.55.202
      WiFi signal strength -55dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0


  • Is that from immediately after the pauses in the print?



  • Hello

    No, I have the M122 anywhere in between.

    I have now set 1/16 and I1 and it seems to be exactly that.
    now it looks good.

    thanks for the competent help.

    regards


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.