@dc42 No. Frankly I suspected that may be the issue.

@dc42 Cool.. thank you very much! I will consider to do the upgrade in the next days. The printer is still in the build phase and I have a lot of other things todo anyway. So I may wait, let's see.

Cheers, Chriss

@Triet said in Using PanelDue SD card only for gcode files possible?:

M929 P"eventlog.txt" S3

You can specify the PanelDue SD card using 1:/, see https://docs.duet3d.com/User_manual/Reference/Gcodes#filenames-and-paths

Try: M929 P"1:/eventlog.txt" S3

Note that the PanelDue SD card interface is much slower than the onboard SD card.

Ian

There's also a set of guides going from initial connection to commissioning.

https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet

@droftarts I may got with your recommendation of Tooboard. I didn't realize all of the advantages of the Roto TB. My chamber temps average around a max of 62c (with a bed temp of 110c). I'll have to do some testing to see what higher bed temps bring it up to to make sure I stay lower. I was going to add a PTC heater but now I suppose I shouldn't. I just have to devise a mount for the Roto board onto a Hemera XS. I'm sure that won't be too difficult. Thank you for the heads up! Any more advice or considerations?

@droftarts

i think on the Duet3D side we need to use endstops while on the OpenPNP side you use soft limits . The issue happens when you have a Axes with soft limit, it will sometimes go past the soft limit by a very small offset but when there is an endstop triggered that motion/ movement comes to a stop and does not go past.

On all the Axes, i have endstops in Duet3D 6XD controller and i have Soft Limits on OpenPnP

@Rachelle Try CoolTerm: https://freeware.the-meiers.org/
I think it's better than SerialTools, it's just not on the Apple App store.

Ian

@Timothee-Leblond If you have the RPi IP address set by the router DHCP, rather than having a static IP address, it's your router than changed it.

You should also be able to connect via the machine name, eg 'Duet3.local'. See https://docs.duet3d.com/en/User_manual/Machine_configuration/Networking#a-note-about-mdns-local-network-discovery

Ian

@dc42
Thanks for the in depth explanation. Solution 1 would probably be ideal in my case. Because i need to poll only the 6 vacuum sensors at 5 ~ 20 ms when opening and closing vacuum of each nozzle during pick and place sequence. After the OpenPnP job is run or completed i don't need to poll at those low times

is there a way that you can adjust M308 command as you said to provide up-to-date reading for individual sensors when requested in addition to the current last reading option. In my case, up-to-date reading would solve the issue

or May be add a parameter to M308 that allows for individual sensor polling but leave the rest of the sensors at default polling of 250 ms to avoid a huge load increase on CAN bus

e.g

M308 S0 P"2.io0.in" Y"linear-analog" A"VG1 Pressure" F0 B37 C-130 Tnnn

where Tnnn is the adjusted polling frequency for that Sensor otherwise default is 250 ms as usual for Duet Boards.

Any solution that is easy to implement quickly without causing a lot of issues in the Duet3D firmware code would be ideal

@Tinchus coolstep reduces the current to the motors under some conditions. Phase stepping controls the motors by directly commanding the phase currents instead of sending step pulses to the driver, which allows us to compensate for nonlinearities in the stepper motors; but it also allows us to reduce motor current when the speed and acceleration are low.

@SpeedyDad said in Voron Trident XY configuration:

A=X and Y=B

Just go with this.

@elmoret 😂 sorry!

@sebkritikel sorry I missed your reply - thanks for your valuable suggestions!

@dc42 I see! Changing my thermistor from sensor 0 to sensor 1 in the M308 pin fixed the issue. Thanks!

@dwuk3d My current (not yet finished) macro if it is of any interest

;AlignXYZ.g ; G90 G1 U150 V290 F20000 G1 Z50 F1000 M98 P"0:/macros/FindProbeXY.g" M574 Z1 S2 K3; Set Z to Ball Probe G1 H4 Z{global.zHit} F300 if sensors.probes[3].value[0] = 0 echo "Probe not found" break ;G1 X235 Y179 F10000 G1 Z50 F1000 ; Find basic Z position var Zpos = {50,49,48,48,48} var Zrate = {300,200,100,80} var Xpos = {10,8,8,8,7} var Ypos = {10,8,8,8,7} var XYrate = {1000,800,300,100,100} var prev = false var pXM = 0 var pYM = 0 while iterations < 4 M574 Z1 S2 K3; Set Z to Ball Probe G90 G1 Z{var.Zpos[iterations]} F300 G91 G1 H4 Z-10 F{var.Zrate[iterations]} ;echo "Z", {move.axes[2].userPosition} var ZP = move.axes[2].userPosition G1 Z5 F5000 M574 Z1 S2 K0; configure Z axis endstop ; Now find X middle G91 G1 X{0-var.Xpos[iterations]} F5000 G90 G1 Z{var.ZP-0.2} F300 G91 M574 X1 S2 K3 G1 H4 X+10 F{var.XYrate[iterations]} ;echo "X1", {move.axes[0].userPosition} var X1 = move.axes[0].userPosition G1 Z5 F300 G1 X{var.Xpos[iterations]} F5000 G1 Z-5 F300 G1 H4 X-10 F{var.XYrate[iterations]} ;echo "X2", {move.axes[0].userPosition} var X2 = move.axes[0].userPosition G1 Z5 G90 var XM = (var.X1+var.X2)/2 ;echo "XM", {var.XM} G1 X{var.XM} M574 X1 S3 ; configure X axis endstop ; Now Y G91 G1 Y{0-var.Ypos[iterations]} F5000 G1 Z-5 F300 M574 Y1 S2 K3 G1 H4 Y+10 F{var.XYrate[iterations]} ;echo "Y1", {move.axes[1].userPosition} var Y1 = move.axes[1].userPosition G1 Z5 F300 G1 Y{var.Ypos[iterations]} F5000 G1 Z-5 F300 G1 H4 Y-10 F{var.XYrate[iterations]} ;echo "Y2", {move.axes[1].userPosition} var Y2 = move.axes[1].userPosition var YM = (var.Y1 + var.Y2) / 2 echo "G92 X"^{var.XM}, "Y"^{var.YM}, "Z"^{var.ZP}," ;---X1,2",{var.X1},{var.X2},"--Y1,2",{var.Y1},{var.Y2} echo "G92 U"^{var.XM}, "V"^{var.YM}, "Z"^{var.ZP+5} if (var.prev == true) echo "variation X:",{var.pXM-var.XM}, "V:", {var.pYM-var.YM} set var.pXM = var.XM set var.pYM = var.YM set var.prev = true if exists(global.ballProbeX) == false global ballProbeX = var.XM global ballProbeY = var.YM global ballProbeZ = var.ZP else set global.ballProbeX = var.XM set global.ballProbeY = var.YM set global.ballProbeZ = var.ZP G1 Z5 F300 G90 G1 X{var.XM} Y{var.YM} F2000 M574 Y1 S3 ; configure Y axis endstop G90

With find probe here

;FindProbeXY.g ; G90 G1 U150 V320 F20000 G1 Z50 F1000 G1 X235 Y170 F10000 if exists(global.zHit) == false global zHit = 44.5 ; See if already in correct position M574 Z1 S2 K3; Set Z to Ball Probe G1 H4 Z{global.zHit} F300 if sensors.probes[3].value[0] = 0 G1 Z50 F1000 G1 Y170 X230 F10000 G1 H4 Z{global.zHit} F300 if sensors.probes[3].value[0] = 1000 break M574 Z1 S2 K0; configure Z axis endstop var y = 150 M574 X1 S2 K3; Set Z ball to X while var.y<200 G1 H4 X270 F1000 if sensors.probes[3].value[0] = 1000 break G1 H4 Y{var.y+5} F1000 if sensors.probes[3].value[0] = 1000 break G1 H4 X230 F1000 if sensors.probes[3].value[0] = 1000 break set var.y = var.y + 10 G1 H4 Y{var.y} F1000 if sensors.probes[3].value[0] = 1000 break M574 X1 S3 ; configure X axis endstop back G1 Z50 F1000

@fcwilt Thanks for your feedback @fcwilt . To answer both: I dindt knew that probe but... I have exactly the same design for a very hight temperature enclosed actively heatd chamber (it reaches 220 degrees celsius). As far as I can see it is the same (but body in my case is all cnc metal). Works very good but ccuracy is lower than bltouch because of temeprature effects on metal and other details but sill way better than anything else (we have an average error of 0.01mm, wich is way of what it can affect a first layer print ). A good example of a problem being solved in 2 places reaching to the same solution. In this case for the moment I would prefer not having to send a new "touchy" body cnc part (this is how we called this sensor internally) adn try to keep for some more time the blotuch, we have 10 of them deployed)

Regarding the other answer: we can debate if you want in the other topic, because doing it here is like repeaton all again, but trust me: thisis not a mecanical issue. The permanent magnet in no way can be affected by a 50 degrees temp in such way. I would agree if we would be talking of 70/80 degrees. Also they way it manifest is clearlo not a mecanical issue. And as I said in the original post where you can see numerical data, this is happenining on the electronics (blt side, not the duet)

@Tinchus said in raspberry camera on new firmware version:

@the_K Im not able to replicate the installation on another printer. The same as you it is happening to me: plugin just runs for 1 second. Looking at the logs I can see an error about a camera module, so I installed:

sudo apt -y install python3-picamera2

With this I can start the plugin and stays active. Still, I cant see the camera on DWC

I’ve always found it useful to prove a streamers settings with a browser before proceeding further. There are just sooo many variables …. Having said that, given a pi camera and the pi libraries - it should more-or-less just work (or at least log sensible errors)

I’ve stopped using pi cameras, so I stopped supporting my old pi streamer. However - you may ( or not ) find something useful in my old notes

https://github.com/stuartofmt/Pi-Notes/tree/master

@chrishamm
Sorry @chrishamm , unfortunately i deleted it before seeing this message. My mistake, i should have kept it. Sorry for that

@agz90 also make sure that you remove the Erase jumper before you command Bossa to flash the firmware.

Thanks for the help.

lets close the topic, It is not related really to the duet. I found the problem: if router goes down and then recovers power, at least on this particular router and internet provider, the router and the printer reconnect again, but the dhcp server on router just give the printer internal network config but ont the required config to get out to internet, and also something happens with the internal dns name ".local" wich is not founded again by other devices reconnecting.
Reconnection should happened only after the router reconnect to the ISP.
I added a crontab job every 10 minutes on the raspberry to handle these event, I post the info here just in case somebody else have this "problem":

sudo nano /home/pi/reconnect_wifi.sh :
#!/bin/bash
if ! ping -c 1 -W 1 8.8.8.8; then
sudo ip link set wlan0 down
sudo ip link set wlan0 up
fi

sudo chmod +x /home/pi/reconnect_wifi.sh
sudo crontab -e:

*/10 * * * * /home/pi/reconnect_wifi.sh