fluidd-core / fluiddpi Goto Github PK

Something is happening causing mjpg-streamer to be compiled without the input_raspicam plugin due to unmet dependencies. If I had to guess, something changed with the location of /opt/vc/include that isn't being installed on the root image causing the plugin to have unmet dependencies. The raspi camera doesn't work out of the box because it's missing the so associated with the plugin.

Hi, I installed FluidPi on RPI Zero 2W, and I have 'unknown' error.
On first run I had error about printer.cfg file not present, when I pasted my config file (that was working on the same printer under Octoprint) it changed to 'unknown' error are there seem to be no communication with klippy service.
It looks like this error is repeating:
[websockets.py:build_error()] - JSON-RPC Request Error: -32601
I installed FluidPi once again from ground up and the behavior is the same.
I also tried to update everything - nothing changes.

I'm attaching log files:
klippy.log.txt
moonraker.log-1.txt
I thought maybe the configuration file had an error and I added one entry at a time, but when there are no more errors with the configuration file, an unknown error appears.

edit: I also tried installing with KIAUH and the error is the same.

I was looking for where the problem with the thumbnail is and why they don't appear, after a long time I discovered this.
There is no option to search for thumbnails in the "metadata.py" configuration file for the S3D slicer. I copied this part from the Prusaslicer and copied it to the Simplifi3D part and everything works as it should. Please integrate this item permanently, there are enough fans who will appreciate this support.

since November 9th 2021 the 'Build FluiddPI - RapsiOS' action fails with following error

+ apt install python-virtualenv virtualenv python-dev libffi-dev build-essential -y
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Package python-virtualenv is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'python-virtualenv' has no installation candidate
++++ echo_red 'build failed, unmounting image...'
++++ echo -e -n '\e[91m'
++++ echo build failed, unmounting image...
build failed, unmounting image...

Hello,

The latest version does not download. The connection times out. Is there a fix for this? Thank you!

Is there a way tp Change Fluiddpi to the 24h Format?

Hi!

Having only used FluiddPi for a only a few prints, I wasn't sure if this issue belongs here or in one of the other components that make up the project. If someone could point me in the right direction, I would greatly appreciate it!

I have been using FluiddPi with a CANCEL_PRINT gcode macro defined in printer.cfg for a few days. However, my printer.cfg became corrupted after the Raspberry Pi became filled with logs (this was a problem with KlipperScreen). After solving this problem and restoring my printer.cfg from a previous version, I was able to get things running again.

Today, I updated the all of the components within FluiddPi then set out to rebuild my CANCEL_PRINT macro. However, now it complains that the macro already exists. Commenting out the macro causes the system to complain about the CANCEL_PRINT macro being missing! lol wut?

I tried to comment out the [CANCEL_PRINT] macro present in fluidd.cfg without success as well.

Attached are the log files and my configs. Thanks in advanced and thanks for making such great software!

klippy.log
moonraker.log
fluidd.cfg.txt
KlipperScreen.conf.txt
moonraker.conf.txt
printer.cfg.txt

Please delete, problem did go away

The error persists on the display. I don't know where to write. The display will be streaked if I wake up. Sometimes the image flickers as you live. Resolution cannot be selected after using the raspi-config command. The resolutions do not include the Raspberry Pi 7" Touch Display TFT - DSI connect. Resolution which would be 800x480. FluiddPi is installed. There was nothing wrong with Mainsail, it worked flawlessly. Who should I write to?

Hello, I started by using a fresh install of Raspian Lite OS as my base install for my Pi4. Then I installed docker as per many "how to's" on the internet for Raspberry Pi. Once I had docker installed I followed the directions here https://hub.docker.com/r/cadriel/fluidd
and got fluidd to work. But when logging into the web browser I found in an error state: No moonraker connection. Please check moonraker status and / or refresh.

I tried to find a solid fix by googling, like all good programmers, but I found nothing. Is it perhaps something in my architecture that was causing it to foul?

I have 2 printers running each with a full fluiddpi/mainsail / klipper install on a RPi Zero 2 on each.
ip address 10.1.1.81 and 10.1.1.102.

Each IP has the other printer installed under 'Printer' on the right hand menu
Each printer also has a USB webcam installed and activated via fluiddpi settings and edited webcam.txt config.

When I connect to 1 IP (.81) I can see the camera for the .81 printer. when I switch using the right hand menu to the .102 printer, I have the correct printer menu and UI, but the camera shown is for the .81 printer (but not the inverted settings, etc)

This is also true when i directly connect to the .102 printer. I can see the .102 camera and only that camera. If one camera is disabled, then I am unable to view the working camera from the other ip address.

Cliff Notes : Webcam only works on the directly connected IP address for the printer in fluiddpi

Hi, I got the last version of fluidd and it is managing an ender 5 plus with skr 1.4. All move perfectly except for the z-axis button (I think). In opposit to octoprint-klipper, when I push the up z button the build plate goes down and it goes up when I push the down z button. It is not a big issue but some time is confusing and when you forgot this and the tools head is very close to the build plate and I push the wrong button with 25mm of movement, then......
A way to modify the assignment of some (or all buttons) can be useful. I don't know if there is already one, at least I am not able to find this info.
Thanks

I have had fluiddpi installed on my pi for a while now, but now I'm getting alerts for my network that says that Fluiddpi is a network insecurity, and klipper_probe_speed (I just installed a BLTouch) is malware. This isn't really an issue for me, but I'm worried about my ISP, and I want to know how to get these alerts with the pi to stop.

This is what I did to get my PiCam working in fluiddPi.

1. raspi-config
2. choose "3 Interface Options"
3. choose "I1 Legacy Camera"
4. Enable
5. Finish raspi-config and reboot

Now PiCamera should work. Hopefully this work around will help anyone else having trouble.

Before I did the above I kept getting 502 bad gateway errors and no matter what I did in FluidUI camera settings or webcam.txt nothing would work.

Information about the legacy Raspicam stack can be found here: https://www.raspberrypi.com/documentation/accessories/camera.html

Hi,i meet some warnings. I fix one(PolicyKit Permissions) ,but some, i don't know how to fix them.

Would you be interested in making the FluiddPi image a readonly filesystem? Would make things less error-prone on powerloss or people pulling the plug without shutting down and also not wear down the sdcard.

Trying to follow the docs to install fluidpi suggests that the img is in the release archive.

I was able to grab the img from the actions artifact so I'm good! But thought it would be good to bring this to your attention.

If you need me to create a PR to do it let me know!

Was moonraker supposed to be installed with this file. When I try to go into my raspberry PI I get the error "No moonraker connection. Please check moonraker status and / or refresh"

Model: Raspberry PI 3B

Using Balena Etcher I copied the image of the latest FluiddPI build "fluiddpi-rpi-lite-v1.17.0". Added the WiFi connections as instructed and booted from the sd card.
During the bootup I can see that the following error "/etc/rc.local failed compatability" and then it continues until it reaches "Finished Update UTMP about System Runlevel changes". It does not progress any further.

If I try rebooting, I still get the error "/etc/rc.local failed compatability" but then it stops at prompt for Fluiddpi login

What am I missing?

Is there something else I need to do that is not in the instructions?

device: pi 3b+

Each shutdown or power failure may cause the system to fail to start and require reburning the image and configuration

Browser

Chrome

Device

Other (Please tell us below)

Operating System

Linux

What happened

From time to time (usually every few hours, sometimes it lasts longer, for maybe 12 hours) I get disconnected from the printer because of those dreaded Linux Kernel USB issues Linux and especially the Pi platform have been plagued by for years.

This happens only on a Pi4. No, it's not a wiring/shielding/grounding or power supply issue. Switched the exact same sdcard from the Pi4 over to a Pi3B+ and the problem is gone.

Linux kernel log looks like this when it happens:

[45407.479837] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[45407.480360] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[45407.580037] ch341-uart ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32
[45407.606245] ch341-uart ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32
[45407.657376] ch341-uart ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32
[45407.732291] usb 1-1.3: USB disconnect, device number 3
[45407.733660] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[45407.733766] ch341 1-1.3:1.0: device disconnected
[65765.234395] usb 1-1.3: new full-speed USB device number 4 using xhci_hcd
[65765.380539] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[65765.380562] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[65765.380580] usb 1-1.3: Product: USB Serial
[65765.385347] ch341 1-1.3:1.0: ch341-uart converter detected
[65765.392747] usb 1-1.3: ch341-uart converter now attached to ttyUSB1
[74477.881226] ch341-uart ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[74477.884539] ch341-uart ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[74478.083060] ch341-uart ttyUSB1: usb_serial_generic_write_bulk_callback - urb stopped: -32
[74478.083842] ch341-uart ttyUSB1: usb_serial_generic_write_bulk_callback - urb stopped: -32
[74478.089993] usb 1-1.3: USB disconnect, device number 4
[74478.092247] ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1
[74478.092346] ch341 1-1.3:1.0: device disconnected

What did you expect to happen

No random USB disconnects

How to reproduce

• Connect an Ender7 (probably other printers with ch341 USB2Serial will also show the issue) to fluiddpi
• Print something that takes a few hours
• Wait until the print stops and Klipper giving an error message
• Check Linux Kernel log with "dmesg" to see if you got those "urb stopped" messages

Additional information

No response

Im trying out fluiddpi for the first time so this might just be a beginner issue.
When connecting for the first time it asks for username and password, which I haven't setup yet. Using SSH I changed the moonraker.conf force_logins to false and even after rebooting still asks for login. Using an older version like 1.16.2 solves the issue even after updating everything.

Used the raspberrypi imager and set the SSID and PW correctly.

I checked the wpa_supplicant files in /etc/wpasupplicant/ and in /boot/fluiddpi-wpa-supplicant.txt and both are showing the correct ssid and a hexadecimal pw

On boot, literally nothing happens. I'm waiting on my unifi to pickup even an attempt but nein. Nothing.

Trying to add a preset to heat the chamber but I can't make one without entering a value for extruder greater than 0 even if it is unselected. Add button does nothing unless I enter a value for the extruder. Unselecting a device should remove the requirment.

Hi I am getting an error update the OS packages

Transaction Refresh Cache: Error Failed Run time 0.00 seconds
error updating system

Adding the default PAUSE macro to my gcode causes the printer to pause where expected, and if left alone for a couple of minutes, to cool the hotend and bed (this is fine). However it also loses it's homing location, and it won't let me resume the print without rehoming all axis.

How do I prevent this behavior?

Fmp4streamer streams your V4L2 camera directly to any browser and media player as H264 inside fragmented mp4. It is compatible with desktops and mobiles. You can add it your phone's home screen too!

https://github.com/soyersoyer/fmp4streamer

How does it work?

Fmp4streamer setups the V4L2 device, reads the H264 or MJPGH264 stream from it (or the YUYV, MJPG stream and converts to H264 with a M2M V4L2 device), adds MP4 header (fragmented mp4 - fmp4) and serves it via HTTP. On the browser side it works with only one html5 video tag, no js needed. It's pretty lightweight.

Did some testing with this and you can't use it directly loaded on FluidPi. All you get instead of video on the camera view is another instance of Fluidd no matter the port you use. I am able to view the stream loaded on FluidPi in a separate browser tab however. It has to be from a separate IP address and that way it works extremely well. No more bandwidth constraints trying to push a huge MJPG stream.

It also uses barely any CPU or Memory as all the heavy lifting is done on the GPU which we don't use anyways except maybe KlipperScreen. It is so light weight it works on the original Pi Zero.

You can view the specific capabilities of the attached cameras with v4l2-ctl --list-formats-ext

• No additional dependencies were needed during testing.
• Would need to work around issue of adding the camera to Fluidd from the same IP it is hosted from.
• Provide documentation on Fluidd Wiki
• Modify code to incorporate fmp4streamer.conf config file into the Fluidd config directory so that it can be edited from within the WebUI.

I'm trying to build a client application to work with Fluidd.
I'm mostly done with the project, however I cannot figure out where FluiddPi stores the different hosts information?

MainsailOS is doing this in the database, however this seems not to be the case for FluiddPi.
Can you give me a hint? I need to get the information via WebSocket or REST-API.

Thank you!

It just dawned at the that there is no confirmation dialog that we could use for the [power] items, like the one that shows on the host shutdown/reboot!

Ideally, I would ask for this to be a configurable thing, so one could decide if we want to have a confirmation popup or not, but I do think this would be a great feature to have (and hopefully an easy one to implement)!

Hi!

I'm using FLuiddPi and trying to set up a camera. I came across this article:
https://docs.fluidd.xyz/features/cameras

But I can't find /boot/webcam.txt, or even /boot/fluiddpi.txt. Maybe I'm missing something?

Camera type: Logitech C270
Enabled under Settings with Stream typ: MJPEG Adaptive
Camera URL: /webcam/?action=stream

Thanks a lot for this image!

I downloaded and installed 1.18.2 to see what was wrong with the ssh login.

Mounted the rootfs filesystem to look around and found the issue with the pi user that does not have a password set in /etc/shadow which is failling all logins.

HTH to find a fix.

v.1.18.2

# cat fluiddpi_version
0.4.0

# grep ^pi *shadow? passwd?
gshadow-:pi:!::
shadow-:pi:*:19086:0:99999:7:::
passwd-:pi:x:1000:1000:,,,:/home/pi:/bin/bash

😢 - fluiddpi_version is not updated with the tagged version number

Working version

cat fluiddpi_version
0.4.0
grep ^pi *shadow? passwd?
gshadow-:pi:!::
shadow-:pi:<REDACTED>:18754:0:99999:7:::
passwd-:pi:x:1000:1000:,,,:/home/pi:/bin/bash

where are the image files? Searched in all versions and didn't find it?

Hi,

I am trying to run FluidPi on my Raspberry Pi 2 B1.1.
It does not have WLAN, I connected it to my Router via LanCable in the hopes it would get an IP Adress automatically.
I tried to find Hardware requirements or a LAN setup Guide but failed to do so.

Is my Pi suppported?
Is it possible to run it in LAN instead of WLAN?

Best Regards
Tony

PS: Sorry for the Issue.

Hello, how i can change the local port for the connection? i don't want to use the 80 because i use it for another service

Whilst testing the new version I installed numpy and pandas for resonance and probe accuracy testing. This resulted in an error.

Traceback (most recent call last):
  File "/home/pi/.local/lib/python3.9/site-packages/numpy/core/__init__.py", line 23, in <module>
    from . import multiarray
  File "/home/pi/.local/lib/python3.9/site-packages/numpy/core/multiarray.py", line 10, in <module>
    from . import overrides
  File "/home/pi/.local/lib/python3.9/site-packages/numpy/core/overrides.py", line 6, in <module>
    from numpy.core._multiarray_umath import (
ImportError: libcblas.so.3: cannot open shared object file: No such file or directory
...
We have compiled some common reasons and troubleshooting tips at:

    https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

  * The Python version is: Python3.9 from "/usr/bin/python3"
  * The NumPy version is: "1.22.4"

Installing the following package, referenced in the above output, fixed the issue.

sudo apt-get install -y libatlas-base-dev

I just installer the latest updates including moonraker v0.7.1-343-g305e002 and Fluid v1.16.2 and the host shutdown, reboot or services reboots stopped working.

It worked flawlessly before, no other updates are performed, running an RPI4 4GB.

I've recently updated klipper, moonraker, and fluidd via the UI and received a subsequent warning regarding PolicyKit. I followed option 2 at https://moonraker.readthedocs.io/en/latest/installation/#policykit-permissions and added

[machine]
provider: systemd_cli

# Edit your existing [update_manager] section to disable
# PackageKit.  This will fallback to the APT CLI Package Update
# implementation.
[update_manager]
#..other update manager options
enable_packagekit: False

to my moonraker config. I am now receiving a 502 when trying to connect.

Unfortunately, I must have had bad timing and upgraded to the 1.18 release which is no longer allowing me to ssh. As I can't login to fix the moonraker config, do I have any other path forward than to rebuild?

Also, why did the addition of those 2 entries cause the 502?

Linking to the deprecation message in the readme generates a really awkward, almost suspicious, link due to the unicode chars used in the header: https://github.com/fluidd-core/FluiddPi#%EF%B8%8F-warning-%EF%B8%8F

would be nice to have a clean url , e.g. https://github.com/fluidd-core/FluiddPi/#deprecated, and move the emoticons elsewhere.

Browser

Chrome

Device

Desktop PC

Operating System

Windows

What happened

Hello!

I have a NOIR raspberry camera, so normally it streams in shades of pink.
To fix that (when you don't need it to stream at night) on a regular Pi OS I use that command with -awb greyworld key:
raspivid -p 0,0,640,480 -fps 30 -t 0 -awb greyworld --fullscreen

So in the webcam.txt file I made that line:
camera_usb_options="-r 640x480 -f 30 -awb greyworld"
And this is the result:

At the beginning I thought that the video streams but the window is collapsed, but actually, there is no stream.
Openning in a full screen mode gives a 502 Bad Gateway.

After removing -awb greyworld key, it works fine:

I have also tried to use other -awb key options (https://community.octoprint.org/t/available-mjpg-streamer-configuration-options/1106), still the same issue.
So is there any idea how to fix that.

Thank you very much.

What did you expect to happen

I expect to see a regular stream with -awb greyworld key (IR filter).

How to reproduce

Just try to insert -awb key, for example:
camera_usb_options="-r 640x480 -f 30 -awb greyworld"

Additional information

No response

PI won't automatically reconnect to wifi until you do these steps:
https://raspberrypi.stackexchange.com/a/5341
This should be default in firmware (in my opinion) since losing the connection removes the ability to force stop the printer.

I disable the raspberry PI on the website, and then I disable the printer. Raspberry PI's system won't boot when the printer starts up again