Posts made by phoenix

@jay_s_uk The first screenshot in my original post shows the Machine Settings Tab: on the bottom you see the presets (90 / 85 / 65 / 60). The dropdown (250 /235 / 220 /205 / 195 / 160 / 120 ) is what I get as choices when I go to set Bed temperature

@jay_s_uk thanks - deleted the file but it came back the same way

@Phaedrux Sorry I forgot to mention... 3.5.3 both

Hello, I have noticed that in the Web interface, the dropdown for Bed temperatures does not match its preset list: instead it lists the same temperatures as for the Tools. I assume there's a config file that has failed to update - can somebody point me in the right direction?

The "Machine Specific Settings":

@Phaedrux @droftarts on Channel 13 now (Europe, and much less congested than 11 or 6).

I believe it's gotten slightly better, but I still see disconnects at random (frequent) intervals. If i understand you right, this is caused by EMF? Is my last resort an external antenna?

@droftarts I didn't even think the accelerometer showed up in M122?

Here's the latest, but I can't spot an Accelerometer mention?

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3 (2024-01-24 17:56:24) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MS8-6J9FL-3SN6N-TVVR9
Used output buffers: 2 of 26 (26 max)
=== RTOS ===
Static ram: 23224
Dynamic ram: 77824 of which 0 recycled
Never used RAM 11832, free system stack 138 words
Tasks: NETWORK(1,ready,12.4%,221) ACCEL(6,nWait 5,0.0%,346) HEAT(3,nWait 5,0.1%,327) Move(4,nWait 5,0.0%,261) DUEX(5,nWait 5,0.0%,24) MAIN(1,running,85.9%,742) IDLE(0,ready,1.6%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:52 ago, cause: power up
Last software reset at 2024-02-11 15:48, reason: User, Gcodes spinning, available RAM 8392, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 18.2, current 23.4, max 23.6
Supply voltage: min 24.1, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min 148
Driver 1: ok, SG min 153
Driver 2: standstill, SG min 0
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: standstill, SG min 0
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10: 
Driver 11: 
Date/time: 2024-03-28 07:56:16
Cache data hit count 1959708808
Slowest loop: 24.28ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 11, maxWait 39308ms, bed compensation in use: none, height map offset 0.000, max steps late 0, ebfmin 0.00, ebfmax 0.00
next step interrupt due in 104 ticks, disabled
Moves shaped first try 1, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 5, completed 4, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by HTTP
HTTP is idle in state(s) 2 0 15, running macro
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 1, 1.13 reads/min
=== Network ===
Slowest loop: 24.42ms; fastest: 0.00ms
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.1beta6
MAC address ec:fa:bc:2d:df:4f
Module reset reason: Turned on by main processor, Vcc 3.39, flash size 2097152, free heap 43064
WiFi IP address 192.168.178.30
Signal strength -52dBm, channel 13, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

@Phaedrux Version 1.27 does not bring any relief unfortunately.

I understand @droftarts point - I'll change the channel to 6 or 11 on the home wifi. Crossing my fingers !

@droftarts Ian, it was connected directly to the Duex TempDB connector.

While moving it to Duet, I noticed that the INT1 pin wasn't fully aligned. Changed the plug and reset all cables, I now see values!

Thank you so much for your patience guiding me through it

@droftarts Version is now showing 2.1beta7.
No change in the behavior. It's mostly annoying when doing config work, as randomly the interfaces loses connection (and reconnects within a second), but it closes the edited config file wihtout saving obviously.

@droftarts Thanks Ian, unfortunately even with S = 1 nothing comes but "Failed to collect data from accelerometer"

@droftarts Thank you for the pointer - I have updated it but can't see a difference.

@gloomyandy Thanks for the pointer - I just did the following from the console

So nothing seems to go wrong, but the file is still empty:

Sample,X
Failed to collect data from accelerometer

is there a more descriptive way to query manually?

@gloomyandy said in Input shaper v3.5.0 -rc4 not showing motion profile:

So for some reason the data collection is not working.

Reply

Thanks - if the Accelerometer connects and shows up reliably - what could be causing this? Are we back to cable issue (despite double shielded USB3?)?

Hello,
trying to troubleshoot another problem I discovered a possible cause to a recurring annoyance of mine: the connection to the webinterface tends to reset itself every so often. Haven't bothered so far as more pressing things, but here's what I have: at random intervals I see this in the logs:

Digging in, I find that the while everything else is at RRP 3.5.0-rc3, the Wifi system is listed DuetWiFiServer 2.1beta6. I can't find what the exact last version needs to be, but I downloaded the Duetwifiserver.bin listed in RRP 3.5.0-rc3 and uploaded it (using webinterface): when restarting it stays at v2.1beta6

Can you tell me what version there should be?

Thanks!

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3 (2024-01-24 17:56:24) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MS8-6J9FL-3SN6N-TVVR9
Used output buffers: 9 of 26 (26 max)
=== RTOS ===
Static ram: 23224
Dynamic ram: 77664 of which 0 recycled
Never used RAM 12256, free system stack 182 words
Tasks: NETWORK(1,ready,13.4%,221) ACCEL(6,nWait 5,0.0%,346) HEAT(3,nWait 5,0.1%,327) Move(4,nWait 5,0.0%,360) DUEX(5,nWait 5,0.0%,24) MAIN(1,running,86.0%,742) IDLE(0,ready,0.5%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:58 ago, cause: power up
Last software reset at 2024-02-11 15:48, reason: User, Gcodes spinning, available RAM 8392, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 20.3, current 27.0, max 27.2
Supply voltage: min 24.1, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, 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: standstill, SG min n/a
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10: 
Driver 11: 
Date/time: 2024-03-27 08:02:25
Cache data hit count 4294967295
Slowest loop: 15.30ms; 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 2.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 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 0, completed 0, 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
=== 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 1, 0.34 reads/min
=== Network ===
Slowest loop: 15.13ms; fastest: 0.00ms
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.1beta6
MAC address ec:fa:bc:2d:df:4f
Module reset reason: Turned on by main processor, Vcc 3.39, flash size 2097152, free heap 43068
WiFi IP address 192.168.178.30
Signal strength -44dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Anybody has a pointer?

The Probe is getting recognized flawlessly, connected by USB3 cable and registers as:

M955 P0
Accelerometer 0 type LIS3DSH with orientation 20 samples at 1600Hz with 16-bit resolution, SPI frequency 2000000

The line in config.g is

;Accelerator
M955 P0 C"spi.cs6+spi.cs5" ; all wires connected to temp DB connector, no temperature daughterboard

And M122 is

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3 (2024-01-24 17:56:24) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MS8-6J9FL-3SN6N-TVVR9
Used output buffers: 9 of 26 (26 max)
=== RTOS ===
Static ram: 23224
Dynamic ram: 77664 of which 0 recycled
Never used RAM 12256, free system stack 182 words
Tasks: NETWORK(1,ready,13.4%,221) ACCEL(6,nWait 5,0.0%,346) HEAT(3,nWait 5,0.1%,327) Move(4,nWait 5,0.0%,360) DUEX(5,nWait 5,0.0%,24) MAIN(1,running,86.0%,742) IDLE(0,ready,0.5%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:58 ago, cause: power up
Last software reset at 2024-02-11 15:48, reason: User, Gcodes spinning, available RAM 8392, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 20.3, current 27.0, max 27.2
Supply voltage: min 24.1, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, 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: standstill, SG min n/a
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10: 
Driver 11: 
Date/time: 2024-03-27 08:02:25
Cache data hit count 4294967295
Slowest loop: 15.30ms; 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 2.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 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 0, completed 0, 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
=== 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 1, 0.34 reads/min
=== Network ===
Slowest loop: 15.13ms; fastest: 0.00ms
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.1beta6
MAC address ec:fa:bc:2d:df:4f
Module reset reason: Turned on by main processor, Vcc 3.39, flash size 2097152, free heap 43068
WiFi IP address 192.168.178.30
Signal strength -44dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

@chrishamm Here are the last two motion profiles I did:
1-X56-238-0-none.csv
1-Y24-170-0-none.csv

When I opened up to take a picture of the wiring, I noticed a piece of unconnected wire that had fallen off and was resting on the Duex. I guess I'm lucky not to have shortened anything, but the issue is definitely resolved

Thanks @gloomyandy for your indirect help

I am using a Duet 2 WiFi 3.5.0-rc.3
Duet WiFi Server n/a 2.1beta6
Duet Web Control DWC 3.5.0-rc.3

I am able to record a motion profile, but when selecting it, the plugin does not display anything (see screenshot). have been poking around for an hour but can't find what I'm missing

Recording

In my quest to get input shaper working, I finally figured out a reliable way to connect a brand new LIS3DSH, using a USB3 cable: It now connects nicely and consistently using the Duex.

My issue is that since connecting it, I noticed that my temperatures (at rest, and across bed and all 4 extruders) fluctuate immensely.

Can you point me what I am doing wrong or causing this?

Here's what the Accelerometer responds

M955 P0
Accelerometer 0 type LIS3DSH with orientation 20 samples at 1600Hz with 16-bit resolution, SPI frequency 2000000

Here's a screenshot of what I see:

Thanks for your pointers!

Hello, I am converting a small lathe to CNC and having a spare Duet3 board I thought of using it.

I see multiple reports of people having used it successfully but I cannot find any information on making moves synchronized with spindle, specifically threading (G76)? Is this something available that I have missed?

Cheers
Pierre