Posts made by luc

@dc42 said in Duet 2 wifi AND LIS3DH:

@luc did you have any fans running when you did the measurements? If so then the 74Hz spike may have been vibration from a fan. 74Hz is 4440 rpm.

No, fans off. I did the standard test as it is set up by default. I know I have a very small play on the X-axis linear guide (it is a XY core). But I am not sure if the 74Hz is caused by the guide or all by the guide. Tomorrow I will try to tie a weight on my head to see if it changes. If you have any ideas for some tests I would be happy to do them. Thanks for your interest.

@droftarts
That 74Hz spike was there before without applying any shaper.
I think that spike is because of a very slight play (which I discovered a few days ago) that the linear X-axis drive. I think it affects both X and Y. In fact I have to disassemble and try to change the balls. After that I can compare and see if that spike was due to that and whether to uncommpare.
It is an xy core and apart from that nasty 7aHz spike it seems to me that there is no excessive vibration/resonance also because the Amplitude is at most 0.010 for a part but mostly within 0.005.

The paper you linked me I had studied, po thought there was some with more graphs and different examples.

You are so kind, thank you again!

I am using duet 2 wifi e firmware 3.5.4.

And this is my M122:

4/04/2025, 15:09:29: m122: === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.4 (2024-11-24 10:43:42) running on Duet WiFi 1.02 or later + DueX2
Board ID: 08DJM-9178L-L4MSJ-6J1DL-3S46R-TV3GP
Used output buffers: 4 of 26 (25 max)
=== RTOS ===
Static ram: 23488
Dynamic ram: 75300 of which 152 recycled
Never used RAM 11420, free system stack 118 words
Tasks: NETWORK(1,ready,16.6%,217) ACCEL(6,nWait 5,0.0%,249) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,258) DUEX(5,nWait 5,0.0%,23) MAIN(1,running,83.3%,746) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:46:02 ago, cause: software
Last software reset at 2025-04-04 14:23, reason: User, Gcodes spinning, available RAM 11364, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 19.1, current 19.6, max 19.8
Supply voltage: min 12.3, current 12.4, max 12.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/16/16, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2025-04-04 15:09:27
Cache data hit count 4294967295
Slowest loop: 6.95ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 11, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 38, completed 38, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle 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
=== DueX ===
Read count 0, 0.00 reads/min
=== Network ===
Slowest loop: 20.99ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.0
MAC address b4:e6:2d:60:b9:99
Module reset reason: Turned on by main processor, Vcc 3.32, flash size 4194304, free heap 39192
WiFi IP address 192.168.0.40
Signal strength -43dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

@droftarts said in Duet 2 wifi AND LIS3DH:

@luc said in Duet 2 wifi AND LIS3DH:

Entered the following string in config.g:
M955 P0 C “spi.cs4+spi.cs3”

Make sure you are using straight quote marks, not curly quote marks, ie the above should be

M955 P0 C"spi.cs4+spi.cs3"

I try to send M955 and get the following message:
Error: M955: missing parameter 'P'

What firmware version are you using? Send M122 and post the response.

Ian
All ok, thank you too!

The first test performed is what I insierite a few posts above.

Can you give me your opinion on the result?

Is there a document to read that explains how to interpret the values?

@tas
OK...It's ok. Now with m955 po no longer gives error and responds with parameters

many thanks

@tas said in Duet 2 wifi AND LIS3DH:

M955 P0 I25 S1344 R10 ; S1344 is 1344Hz sample rate. R10 is 10 bit resolution for LIS3DH.

Thank you for your response.
I added M955 P0 I20 S1344 R10 but if I send m955 I always get: Error: M955: missing parameter 'P'

Despite the error in my previous post I tried to see if it worked and it did....did the first test.
I attach the image and I would like to know from you who are experts what you think. I got an idea nma would like your opinion. Thank you

Connected as per the description above. The acelerometer led is on green.

Entered the following string in config.g:
M955 P0 C “spi.cs4+spi.cs3”

I try to send M955 and get the following message:

Error: M955: missing parameter 'P'

I read the guidea and for the connection type it seems to me that P0 is correct. What am I doing wrong?

@jay_s_uk Okay, thank you.
So do I just use M955 P0 I20 or not even that which seems to me that by default it considers it oriented according to the axis direction of the sensor?

Here I am again!

Continuing to study the settings, I arrived at the M955 setting.
From what I understand in config.g I enter:

M955 P0 C “spi.cs4+spi.cs3” (change cs4 and cs3 if I use different pins)

But I also need to set the orientation (which for me will follow the axis orientation) so I add:
M955 P0 I20

I am not clear if I also have to add the S and R paramenters so it becomes:
M955 P0 I20 S5000 R10 ?

@droftarts said in Duet 2 wifi AND LIS3DH:

@luc Like I said, it's better to use:

CS / PIN 1 SPI_CS2 cavo arancione
INT1 / PIN 3 SPI_CS1 cavo verde

If you add a temperature daughterboard in the future, you won't have to change the wiring when you plug the accelerometer in on top of the temperature daughterboard, only the configuration.

Ian

Yeah, yeah...okay, thank you.

Yes thank you, I had noticed that.

This should be the correct connection with the wire colors that I will use:

Accelerometer / Duet

Red 3 Volt / PIN 8 + 3,3 cavo rosso
SDA (MOSI) / PIN 5 SPI_MOSI cavo blu
SDO (MISO) / PIN 6 SPI_MISO cavo giallo
SCL / PIN 4 SPI_SCK cavo viola
GND / PIN 2 GND cavo nero

CS / PIN 9 SPI_CS4 cavo arancione
INT1 / PIN 7 SPI_CS3 cavo verde

@droftarts

No, I haven't mounted it yet. The accelerometer should arrive on friday and I was studying the situation to prepare the wiring in advance.

I thank you, it is clearer to me now.

Hi guys, for the connection of a Duet 2 wifi and the LIS3DH accelerometer I am a bit confused as I read different connections between the instructions and some posts of other users.
In the instructions (https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_Accelerometer) I read:
Duet LIS3DH
SDA (MOSI) PIN 5 (MOSI)
SDO (MISO) PIN 8 (MISO)
SCL PIN 4
GND PIN 3

and I don't seem to have any doubts up to here but for the following I read different connections in various posts than the instructions and I have doubts. How should they be connected?
CS PIN 1 or PIN 9?
INT1 PIN 3 or PIN 7?

Maybe I can connect them as I want but is it enough then to use the correct M955?
M955 P0 C “spi.cs3+spi.cs1”
M955 P0 C “spi.cs9+spi.cs7”

Sorry if this sounds like a stupid question but I couldn't figure it out by myself?
Thank you

@Phaedrux Okay, thank you very much!

@Phaedrux
Thank you very much for your helpfulness but let me ask one last question:

Assuming that I think everything works as I printed two quick things ....
How come some words are in red color?

@Phaedrux said in Update Duet 2 wifi from 3.1.1 to 3.5.4:

@luc said in Update Duet 2 wifi from 3.1.1 to 3.5.4:

Where he reads 737°C?

This is just a warning telling you what the predicted max temperature for that heater would be in an uncontrolled situation.

So the syntax in config.g should be correct. Is that right?

@Phaedrux said in Update Duet 2 wifi from 3.1.1 to 3.5.4:

Panel two after a certain time turns off the display (goes to standby) despite from its menu I selected scrennsaver =0);

Can you share a photo of your settings tab on the PanelDue?
I may have solved it by setting "Newer dim"

@Phaedrux said in Update Duet 2 wifi from 3.1.1 to 3.5.4:

You can also send M98 P"config.g" in the gcode console and any errors in syntax in config.g will be returned.

I just get this message:

But going to check in config.g the entry H1 i read M143 H1 S280 . Where he reads 737°C?

hi guys,
I upgraded first to 3.3 and later to 3.54 the duet 2 wifi and also the panel two 5. I did two quick and easy test prints and everything seems to work, even the automatic bed level which I had doubts about.

I would like to ask for help on two issues:

1. Panel two after a certain time turns off the display (goes to standby) despite from its menu I selected scrennsaver =0);

2. The DWC is different from my old version. Where can I find information to read for pluging? Basically the ones that are present are all in a stopped state, is that right?