I am running a Maestro with 12864 LCD. I can confirm there is no real configuration required to enable the LCD appart from plugging in the display and creating menus.

The menus I am using are from the M3D Crane that dc42 linked in another post. I will see if I can track it down.

edit: https://forum.duet3d.com/post/68888

I have it connected to Endstop for E0.
DWC does not report the sensor, but it does appear in M112:

=== Filament sensors ===
Extruder 0: pos -1.74, ok, measured min 61% avg 76% max 96% over 3368.6mm, errs: frame 6 parity 0 ovrun 0 pol 0 ovdue 0

Im assuming since its not a switch and a laser filament sensor its not reporting as expected in the json.

All good will try and work around it.

@gtj0 awesome thanks for all the info thats really helped. makes sense of the number.

After doing some prints and triggering filament out unfortunately it appears the laser filament sensor does not trigger an endstop. So no way of capturing a filament out scenario from the json output. For now I will use the stopped state as a trigger however would be ideal if the json was able to report the state or laser/magnetic sensors.

I did consider that however if I abort a print then it will be a false positive. May be something that I just deal with.
Also may have a look at the DWC source to see if its something in my limited knowledge I can figure out

I was able to see end stops in type 2 however it has a value of 20, I'm not sure how to read this.
Do you know if this also reports laser / magnetic type filament sensors?

Thanks again

Hi all
Im working on home automation and including 3d printer and looking for some help.
My goal is to change the print area lighting to different colours depending on print status (heating, printing, paused completion).
At the moment I am polling the json generated from rr_status?type=3 to get details of print status, temperatures etc.

This is working great however I can't determine a successful print from the output . The fractionPrinted object resets to 0.0 on print completion.
I have looked however cant seem to find (in any of the status types) a print status that shows the file is complete.

Also on a somewhat related note would it be possible to have a status object for filament sensor status?

Thanks Nigel

Hi all
I have recently set up a laser filament monitor (1.7) on my Maestro ( firmware 2.03 ) possitioned between the extruder and spool on my Bowden setup. ( Min 40 max 140 ).

All is working well and seeing good measurement %s on consistent print moves usually between 80-100%. However on very small infill moves ( line distance ~1mm ) I was seeing constant pauses per layer and measurements of min 10% and max 37% when pressure advance was active ( set to 0.15 ). As soon as I disabled pressure advance the measurements jumped up to min 43% max 81%.

I'm just wondering if its possible for the laser filament monitor measurements to be negatively impacted by pressure advance.

Thanks Nigel

Whilst I totally agree simplicity is better, there are situations where it makes sense.
When you are already using the Pi for other things eg motioneye for remote monitoring / recording or octoprint etc.
I would prefer to minimize additional components.

@nikker Ahhhh sounds like the default rules were set to DENY, possibly during your first run through you set the default FORWARD rule to accept,
You possibly ran something like iptables -P FORWARD ACCEPT or the ACCEPT rule you provided above.

Anyway really good news hearing its all setup and running reliably.

When you ping the Duet from the PI do you get a ping reply?

If this is working then there is a problem with the ip forwarding, in this case please send the output from the following commands

sudo iptables -L
sudo iptables -L -t nat
grep ip_forward /etc/sysctl.conf
ifconfig

If the ping reply is not working then it is likely a network configuration issue on the ethernet side, either on the duet of the PI. If you dont get a ping reply can you send your duet config and the output from ifconfig on the pi?

@nikker Looking at the steps you did previously dnsmasq and the dhcp setup is not required if you hard set the ip address on your Duet, remember to set the netmask and gateway however:

From the config details you posted in your previous post

M552 S1 P192.168.1.50 #set Duet IP address
M553 P255.255.255.0 #set subnet mask
M554 P192.168.1.1 #set gateway

Key is making sure the gateway on the Duet is set to the ip the Pi has on eth0.
What is the network address you use on your wireless network? Without getting too much into routing / subnetting, if your wireless network IP is 192.168.1.x you will have problems.

Removing DHCP/dnsmasq from your setup means you can remove the following steps:

update packages and install dnsmasq:
sudo apt-get update"
sudo apt-get install dnsmasq -y

Copy and save the original dnsmasq.conf
sudo mv /etc/dnsmasq.conf /etc/dnsmasq.conf.orig

Configure the new dnsmasq.conf
sudo nano /etc/dnsmasq.conf and paste the following:

interface=eth0 # Use interface eth0
listen-address=192.168.1.1 # Explicitly specify the address to listen on
bind-interfaces # Bind the interface to make sure we aren't sending thingselsewhere
server=8.8.8.8 # Forward DNS requests to Google DNS
domain-needed # Don't forward short names
bogus-priv # Never forward addresses in the non-routed address spaces.
dhcp-range=192.168.1.50,192.168.1.150,12h # Assign IP addresses between 172.24.1.50 and 172.24.1.150 with a 12 hour lease time

@nikker yes you were right both commands are needed. awesome work glad to hear

Also just looking over your previous post, it would be best to set a static IP on your Duet, otherwise there is a possibility DHCP will eventually provide your duet a different IP address. If this happens your port forwarding will break.