Posts made by 3DOeste

@droftarts Hi droftarts, what I mean by closed loop board and software is that, aside from the closed loop driver which take care if the motor lags behind, the other motors don't take that into account. You can have closed loop drivers, but the system continue to be open loop.
In a real closed loop CNC system, if a motor lags behind, the control board and software (path planning) will notice, trhough feedback from the encoders, and coorect the other motors to keep the syncronicity of the system.
So for example if you are milling a part and at some point there is more matterial, some motor might lag behind, it will be corrected by the driver, but since the others motors didn't encounter that perturbance, those won't lag, and you will end with a dent in your part. In a closed loop system, that is corrected by the software and you won't end with a dent but instead with a smooth surface which is dimmensionally accurate.
At the time of this writing, only closed loop software available (which support step and dir) is linuxCNC with mesa cards. But it would be good to have a newer alternative, without reaching the costs professional CNC controllers like fanuc.

Hi, I'm currently modfifying a cnc router with closed loop steppers and I'm looking for control alternatives which are closed loop.
I could only find LinuxCNC which works with mesa cards and have inputs for the motor encoders, I mean not only the drivers are closed loop but also the control board and the software (in the way professional CNC controllers are).
By any chance do you have in development something like that aim at CNC?
There are more options if you go the route of ethercat, but it's way more expensive.

Hi, I recently change the nozzle of my printer with a CHT 0.6 nozzle from Bondtech and did the max flow rate test from 20 to 50mm3.
It started fine, but at the midle of the print it began to do staggered movements, like for the next 10mm or so, but then it began to move fine again, which was at a much higher speed. So no problem with aceleration or jerk. Also the SD card is new and works perfect.
But I notice that while it now reponds fine to panel due, it has not near the perfomance that it has with firmware 3.5.1.
From 3.5.2 I have web disconections, that is fixed now, but panel due takes always time to connect and to read information, web works fine though.

@T3P3Tony Ok, It seems to be working fine with 3.6beta3+1, no delays I could notice.

@T3P3Tony Hi Tony, I tried but 3.6beta3 wroke connection with DWC, I'm trying to fix it now.

Hi, I have the same problem. I'm trying to update through paneldue console, I send M997 S0, it says firmware updating, connection is lost, I reset the board but firmware file is not changed, is it possible to do it this way or only through USB?

@dc42 Hi, I tried that, and it works ok. Today I installed 3.5.3, same behaviour as 3.5.2, but if after homing, I enter the panel due setup page, and then back to status, everything works as it should, without weird delays. It doesn't happen with 3.5.1.

It's connected with a 4-wire cable. I'll test disconnecting the PanelDue as soon as the current print is finished.

Hi, I'm sure DWC was on 3.5.2, and also try again from 3.5.1 to 3.5.2 and I have the slow response from commands from panel due (and also from DWC), back to 3.5.1 again and everithing runs fine.

I reflashed 3.5.1 and all the awkward delays are gone. Commands from panel due are instantaneous.
With 3.5.2 everything works, but has a delay before commands are executed.
So for now I'll stay with 3.5.1.

Well, it took me some time since I needed to finish some jobs, but I changed the SD card, although I couldn't find anything wrong with the old one. I was trying the .dummy upload with a large file, and it disconnect after a short while. I I run M122 after it reconnect I can see 250ms for longest read time, but inmediately after if I run M122 again it shows 5.2ms.
It's worth mentioning that I have absolutely no problems while printing. I didn't have a single print failure even after 3 days of continuous printing.

Also while writing this I tried to do a large simulation and it did it ok without disconnections.

@Phaedrux No.. Do I just flash previus firmware or do I need to do some steps?

@3DOeste Also, If I try to get a response from M122 while simulating, it constinuosly disconnect and it's almost imposible for the response to appear on the console.

@gloomyandy M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.2 (2024-06-11 17:13:43) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BNL-MGPSJ-6J1FJ-3S86T-12ZMW
Used output buffers: 3 of 26 (26 max)
=== RTOS ===
Static ram: 23384
Dynamic ram: 70716 of which 312 recycled
Never used RAM 15084, free system stack 108 words
Tasks: NETWORK(1,ready,33.3%,181) ACCEL(6,nWait 5,0.0%,345) HEAT(3,nWait 5,0.1%,292) Move(4,nWait 5,3.4%,258) MAIN(1,running,63.1%,718) IDLE(0,ready,0.2%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 04:57:38 ago, cause: reset button or watchdog
Last software reset at 2024-07-16 09:21, reason: User, Gcodes spinning, available RAM 15924, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x14
Aux0 errors 0,0,0
MCU temperature: min 18.4, current 41.2, max 41.8
Supply voltage: min 23.7, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/9, heap memory allocated/used/recyclable 2048/1228/668, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: ok, SG min 0
Driver 1: ok, SG min 0
Driver 2: standstill, SG min 0
Driver 3: ok, SG min 0
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2024-08-06 14:29:52
Cache data hit count 4294967295
Slowest loop: 1390.97ms; fastest: 0.11ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 250.0ms, write time 568.1ms, max retries 0
=== Move ===
DMs created 83, segments created 33, maxWait 1026836ms, bed compensation in use: mesh, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00
next step interrupt due in 48 ticks, disabled
Moves shaped first try 104888, on retry 24746, too short 95483, wrong shape 524445, maybepossible 14011
=== DDARing 0 ===
Scheduled moves 352551, completed 352511, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 12], CDDA state 3
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X153.209 Y155.89 F12000" in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 569.00ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
Interface state active, link 100Mbps full duplex
Socket states: 1 2 2 2 2 2

I recently upgraded my Duet2 ethernet from 3.5.1 to 3.5.2 and sice then I have some issues.
The most annoying is that connnection to the web server is lost all the time when simulating a file.
Printer is slow to respond, if I try to move it from panel due it responds almost a second later.
Accelerometer is mostly never found, that happens some time but now is 90% of the time.
BLtouch won't probe multiple times, only one and message says probe already trigger, but that's not what happening, the probe works ok, is becasue of the slow react time that this error occurs.
I include my config.g file, but it didn't change from 3.5.1.config.g

@Sejl you don’t need a special post processor, just use a fanuc one and remove the canned cycles. All the Gs and Ms in every line are no longer needed, it behaves as a normal industrial Cnc, once a command is sent, all the lines following are under that command, unless you change it again.

Industrial cnc systems show real-time position of the movements. What I don’t know is if that position shown is read from the encoders or generated from the gcode. The control definitely knows encoder position off all axis and can make corrections.

I used S3D for two years, I'm using superslicer now, and I'm very happy with it and get much better quality parts than S3D and CURA. CURA is slow. The only feature I missed from S3D is the ability to easily removed unwanted supports, appart from that, slicer works much much better.

Hi! You should provide your specific hardware, movement kinematic, and extruder type before anyone could help you.

@Phaedrux said in Problem with babystepping V3.01 RC10 and DWC 2.1.5.:

So you're saying that if you set the baby stepping once during a print it is being applied again on the second print?

Thats right. It started since the V3 release. I forgot to mention that every consecutive print re home all the axis. I have a bltouch 2.0 and I get excellent repeatability when homing so I don't think thats the problem.
I'll try RC11 next week and test if there are any changes.