Posts made by Kulitorum

@dc42 Cool, it works now - dont know why it didnt before, but now it does. Thank you for the help.

@dc42 On most machines we are running Release 3.3 - never machines are 3.4.1

@dc42 Agreed, it just does not seem to make any difference on site. That being said, the printer is in Saudi Arabia and I'm in Denmark, so I do not have hands on myself. We already have people on site and are sending another guy down there to help debug it.

Thank you for the input.

I build concrete printers that are run by a Duet3.

As a sales and information tool I created an app that allows you to configure your concrete printer - https://cobod.com/configurator

I now made a VR version where you can walk around the machine and play with it and I want to add the Duet GUI to the VR version so we can use it for training. To make it as realistic as possible my idea is to include RRF in the code and present the user with the actual webpage (on a handheld device in VR) so you can simulate basically everything.

So to do this I need to compile the core parts of RRF without all the driver and wifi stuff (and probably more) under windows. My hope is to have everything running and feeding XYZE values to my printer simulator setup so you can have the machine running as real life.

But compiling anything eludes me - I have spend two days and gotten nowhere.

Does anybody have something like this running that I can use as a starting point? - RRF compiling on windows for win32 in any capacity?

Any help or ideas are very welcome.

I'd even pay someone to make it for me

@infiniteloop X-2 of cause

@infiniteloop Thanks for the help - yes, I read it all.

You think the P parameter is explained? - Pnnn means what? Is P2 an option?

Yes, it's 23mm over 4900mm I will fix the frame, but right now I have half a house printed and the printer no longer aligns with the print for some unknown reason

It gets better with M556 S100 X-1 P1 and even better with X-1.9 but X-2 throws it way off. I don't get it.

Also the documentation only referes to using the printed test piece, which really does not apply for 12x20m long houses - it does not really explain how it works.

I hope @DC42 will try to explain tomorrow, and maybe update the documentation for others to read later.

Thank again.

What are the parameters for M556? - I can only find one description and I fail to understand it.

I have a machine that's skewed. If I move 4900mm on the X-Axis, the Y is off by 23mm.

So I tried M556 S4900 X23 P1 ( to make it compensate on the Y-axis? - the P parameter is really never explained)

But it does not go as expected - no real difference.

Some documentation says that the X parameter is in Tangent, others in mm (maybe)

Can you help me understand the parameters?

Thank you.

@phaedrux I mailed it to DC42

@dc42 Hello again.

We setup a test where we ran the same gcode with the nozzle rotation configured for the U axis and for the A Axis.

Thinking that the shaking would be clear, I mounted a gopro on the printhead - looking down - and put some gloves on the floor for reference. The most obvious result is that the whole print happens a lot faster when the nozzle is running as the A-axis, but looking at the printer in real life, you also notice some shaking and hard accelerations on the U-axis version.

I have uploaded an (unlisted) video here: https://youtu.be/abVquTFmLH8

I will mail the config files and gcode files (only the first layer) to you.

My conclusion is that the axies cannot be running the same code, something is not right.

Please have a look.

Michael

@dc42 We are updating the firmware today, but this is not a new thing, it has been the case since forever. (4 years) - so I doubt updating will make any difference.

We spend 3 days trying to figure out why we have these uneven movements, and changing the axis "name" to A fixed it.

We will examine further, but it does feel like the Axies are somehow running different code.

@dc42 I know that's the theory. None the less, if we use the A axis everything is smooth, if we use the U axis it's not.

This is true in both cases if we use rotational or linear configuration. Using A is Ok, Using U is not.

PS: I'd still prefer to use U, so I don't have to re-explain this to all my customers and redo all the documentation, manuals etc.

Interesting development here: We renamed the Axis to A and the problem went away......

We are updating now.

There is a bug!

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.3-rc3
Firmware: RepRapFirmware for Duet 3 MB6HC 3.3RC3 (2021-05-26)

We are using the U axis to rotate the nozzle of our printer, and it seems quite clear that the firmware does not take the u-axis into account when calculating G1 moves.

For example, if they U axis is the slower for the move, the firmware will not properly predict the needed slowdown, and rather run the other axies as if the U would not have a problem, and only when we get to where the U axis cannot keep up, all the other axies stalls, and does very uneven moves.

This has always been the case.

Is the UVW axies implemented differently in the firmware? - Can you take a look at it, please?

Thank you.

Michael, COBOD

We replaced the Duet3 with a Duet2 and that runs fine, so we are delivering this machine with a Duet2 and then we can take it up again.

Kulitorum

Ok - we will update firmware on Monday and if problems percist, we will post a logic analyzer output.

Thank you.

@dc42 Any help here?

That worked. Thanks.

Fark.... Powercycling did nothing, it is unreachable

Now what?

Nope

Trying 3.0 now. It pretty fast lost connection to the interface, and now I can't connect to it. How long is this supposed to take? - Looks like it's just gone. How long should I wait before I power cycle it?

When I run M997 S0, it says something like "please wait while firmware is being updated" - Then after a while is says "operation has been canceled" - No explanation.

What to do?

9/6/2020, 7:58:59 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 v0.6 version 3.0alpha running on Duet 3 version v0.6
Board ID: 08DGM-9T66A-G63SJ-6J9FJ-3SD6R-KS0ZA
Used output buffers: 2 of 32 (8 max)
=== RTOS ===
Static ram: 67772
Dynamic ram: 156016 of which 0 recycled
Exception stack ram used: 612
Never used ram: 168816
Tasks: NETWORK(ready,456) HEAT(blocked,1208) CanReceiv(suspended,3804) CanSender(suspended,1496) CanClock(blocked,1432) TMC(blocked,592) MAIN(running,3472) IDLE(ready,156)
Owned mutexes:
=== Platform ===
Last reset 00:02:44 ago, cause: reset button
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 168424 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04429000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 42.7, current 43.2, max 44.1
Supply voltage: min 20.0, current 20.1, max 20.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Driver 0: standstill, reads 4336, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 4338, writes 14 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 4339, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 4341, writes 14 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 4345, writes 11 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 4347, writes 11 timeouts 0, SG min/max 0/0
Date/time: 1970-01-01 00:00:00
Slowest loop: 1.55ms; fastest: 0.29ms
=== Move ===
Hiccups: 0, FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, 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 = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 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) 0
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
lcd is idle in state(s) 0
spi is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 25.26ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• Ethernet -
  State: 5
  Socket states: 5 2 2 2 2 0 0 0
  === Linux interface ===
  State: 0, failed transfers: 0
  Last transfer: 164619ms ago
  RX/TX seq numbers: 0/1
  SPI underruns 0, overruns 0
  Number of disconnects: 0
  Buffer RX/TX: 0/0-0
  9/6/2020, 7:56:19 PM M997 S0
  Operation has been cancelled
  9/6/2020, 7:55:36 PM Connected to 192.168.1.229