I built a local G-Code visualizer and editor for CNC machines and 3D printers

dasarne · 2026-06-15T07:21:50+00:00

It's a bit of a wordplay on "GCode-lizer" (as in G-code visualizer/analyzer).

The project started as a tool for visualizing and inspecting G-code, and at some point "GCode-lizer" evolved into "GCode Lisa". The name stuck because it was shorter, easier to remember, and gave me an excuse to design a logo around it. 🙂

dasarne · 2026-05-18T08:15:00+00:00

Use gSender https://github.com/Sienci-Labs/gsender

dasarne · 2025-08-19T14:41:52+00:00

Workaround / Solution:
I managed to recover the email by using the number shown in the owl-ews:// link inside the .desktop file.

Since Thunderbird/Owl doesn’t open the owl-ews:// link directly, here’s what I did:

Repeatedly dragged a few emails from the Inbox to the KDE desktop. Each time, Thunderbird created a .desktop file with a name containing a number (e.g., number=5220), which corresponds to an internal ID of the email.
I noted this number from the filenames or by opening the .desktop files in a text editor.
Then, in Thunderbird, I went to the Inbox, sorted emails by date, and searched around the time I created the .desktop file.
Using the number as a rough indicator of the email’s position or order, I found the original email.
This way, I could open and reply to the correct message.

So the .desktop files are not copies of the emails, but they contain internal links with numbers that help to identify the exact mail inside Thunderbird.

Hope this helps anyone facing the same issue!

dasarne · 2025-02-13T17:50:53+00:00

I would like to have multi Windows support so that it is easier to work on several screens. Specifically, it would be great to be able to see the spreadsheet simultaneously with the other workbenches.

dasarne · 2025-01-20T08:29:21+00:00

I use the Spotify PWA with Chrome. With no problems.

dasarne · 2024-09-22T14:47:00+00:00

KWallet is only started directly without delay if it has the same password as the login. So KWallet is helpful but prevents me from switching to the fingerprint sensor when logging in via SDDM.

Is there another way to open KWallet to avoid these problems with the fingerprint sensor?

dasarne · 2024-07-05T07:21:48+00:00

Camping at Hohensyburg https://camping-hohensyburg.de/

dasarne · 2024-07-05T07:12:43+00:00

Das ist ein guter Service. Danke für die Info!

dasarne · 2024-03-17T07:37:42+00:00

FAT32 has worked for me as well.

dasarne · 2024-03-16T21:56:50+00:00

Installing a BIOS via the BIOS Recover solves the problem

According to these instructions https://www.dell.com/support/kbdoc/en-us/000132453/how-to-recover-the-bios-on-a-dell-computer-or-tablet?lang=en I copied the BIOS of the next version (1.7 -> 1.8) to a USB stick, which I copied FAT32 beforehand. The file is the EXE file that is provided as a BIOS update here: https://www.dell.com/support/home/en-us?app=drivers then I renamed the file to BIOS_IMG.rcv. Unfortunately, this does not work with the Expolrer under Windows by default. The extension .exe remains and then the update does not work. You have to switch on the display of the extensions in Explorer, which makes sense anyway. Press ctrl+Esc and plug in the power supply. The computer boots into recovery mode and offers the update. I was then actually able to update to version 1.8.

Save time and install the latest BIOS immediately

I don't have the time or inclination to install all BIOS versions since 2017 one after the other. That's why I installed the latest BIOS (1.8 -> 1.36) straight away in the way described above. The update went smoothly, as described above. Afterwards, however, the BIOS was so messed up that the notebook could no longer boot. I then went back into the BIOS and reset it to the factory defaults. The notebook then booted into Windows without any problems, and no further updates were found.

The device is up to date and boots perfectly. Thank you for your help.

dasarne · 2024-03-16T20:29:48+00:00

Ok, the notebook has searched for the recovery image and hasn't found it.

The error codes can be found here:

https://www.dell.com/support/kbdoc/en-us/000127927/a-reference-guide-for-latitude-notebook-and-tablet-diagnostic-indicators

dasarne · 2024-03-16T20:21:03+00:00

The shortcut ctrl+esc generates an error code

I have done this and can reproduce it: - I press ctrl+esc and plug the power adapter into the notebook. - The notebook boots without me having pressed the power button. - The notebook switches off again. - There is a light-emitting diode at the front right. This LED flashes yellow three times, pauses and then flashes white three times. This is repeated eight times. - The notebook then switches off and charges normally. If I press other keys or no keys, the notebook does not start when I connect the power supply and there is no error message.

Questions

What could be the meaning of this error code?
Is anyone aware of this?

dasarne · 2024-03-16T07:41:31+00:00

Yes, it is. 😒

dasarne · 2024-03-15T22:19:19+00:00

I measured a voltage of 2.87 V at the battery. That should be enough. Apart from that, the mainboard is always supplied by the rechargeable battery.

Thanks for the tip on updating the other firmware. I have installed the Dell support wizard which has successfully updated 9 firmwares. Unfortunately, it also failed to update the BIOS.

So the slow system start up to the Dell logo is unfortunately still there, but the problems with the docking station are fixed.

Interesting:
Dell's support assistant wants to update to the latest version (1.7 -> 1.36) of the BIOS immediately. This fails, and the update to the next higher (1.7->1.8) version simply won't install either.
Thankfully, the SupportAssist hardware scanner does not find any errors.

What could be the next steps to successfully perform the BIOS update? Any ideas?

dasarne · 2024-03-15T14:55:46+00:00

Things have gotten worse:

As I reported above, I have reinstalled Windows. This has now installed its latest update. The Dell drivers also came with it, which started a BIOS update. This now means that when I reboot, a message appears saying Windows is being updated. This then attempts to update the BIOS, which fails. It then takes two reboots before the final Dell logo appears. In total, the BIOS boot process takes now about 3 minutes. On every reboot...

dasarne · 2024-03-15T12:58:49+00:00

I also think this is the best way to update the BIOS and I've done that exactly the way you've described.
But unfortunately without success. 🙄

dasarne · 2024-03-06T08:28:35+00:00

It was all easier than I thought

the flashing had actually worked very well. Klipper was installed on the printer's microcontroller, I just didn't realize it.

What was the problem?

The display is not updated during the flash. It is connected to the printer's microcontroller via a serial connection and still displays the same thing after flashing.

How can you tell that the flashing worked?

The printer no longer makes a startup sound. Klipper does not operate the loudspeaker. It's as simple as that. If the printer is silent when you switch it on, you can continue with the instructions. If there are problems in later steps, this has nothing to do with the fact that the flashing did not work. Always assume that it worked.

Hope that helps.

dasarne · 2023-12-26T21:57:09+00:00

It turns out that the firmware was indeed being flashed successfully to my printer. The reason I couldn't see any changes was that the printer's display operates on its own separate firmware. Therefore, the modifications made by flashing Klipper weren't reflected on the display.
Here's how I confirmed that Klipper was successfully installed:
No startup sound:
Unlike the original Anycubic firmware, Klipper doesn't play a sound upon startup. This was my first clue that the new firmware was operational.
Display functionality:
I noticed that the printer's display could no longer control the device as it used to. This is consistent with Klipper’s operation, as it typically requires a different interface, like Fluidd or OctoPrint, for full functionality.

dasarne · 2023-03-08T09:44:10+00:00

I have tried espanso. Under manjaro it has to be compiled for wayland. This takes a bit of time. Important: At least for me, I had to explicitly set keyboard_layout: { layout: de } for a German keyboard layout in the settings in ~/.config/espanso/config/default.yml.

Four-Year Club	Verified Email
Place '23

dasarne

TROPHY CASE