Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Member Videos / Re: My week this week, my workshop videos!
« Last post by hermetic on February 23, 2026, 11:31:48 AM »
Hi Folks,

I have finished my annual hibernation and ventured back to the windswept wastes of Langtoft! Two little jobs, and back on the D type replica, workshop is lovely warm and tidy, so unless it snows, and as we come to the end of February thatis less likely, I will be posting videos again, weekly if I can get enough together, Hope you enjoy this weeks bag!
Phil, in cold windy East Yorkshire!
22
Project Logs / Re: Electronic Leadscrew for the New Lathe
« Last post by vtsteam on February 23, 2026, 09:55:05 AM »
Thanks Art! :beer:

What kind of projects do you have in mind?
23
Project Logs / Re: Electronic Leadscrew for the New Lathe
« Last post by Country Bubba on February 23, 2026, 06:22:34 AM »
Thank you for this information. I have not heard that before and have some projects coming up using the nano.  Will have to keep this in mind! 
24
Project Logs / Re: Electronic Leadscrew for the New Lathe
« Last post by vtsteam on February 22, 2026, 08:13:24 PM »
Discovered a little problem today with the Arduino Nano. One of the switches that set the thread pitch wasn't actually working. The six switches I have are labeled A through F. The F switch was the problematic one. I hadn't noticed this earlier since it is mainly used for the last threads in my lookup table -- the coarsest metric threads, and I hadn't tested those yet.

The way things are supposed to work -- pushing any switch to "on" basically grounds it's connected pin in the Arduino. Specifically, my switch F grounds pin D13 on the little computer. But my program wasn't seeing that happening when I flipped the switch.

After doing some electrical testing and not finding anything wrong with the wiring, or the switch, I searched the web for "Pin D13", and sure enough, there were several user issues about a Nano's pin D13 as problematic for input!  Apparently, this a known  issue.  :bang:

The reason, it turns out, is that on the nano this pin is attached to a resistor in series with a LED that is connected to ground. The function of that LED is so people can program these boards to run simple programs that flash it as a demonstration -- in fact the most basic program almost everyone starts with when they get one of these boards is called "Blinky" and it blinks that LED.

To do this the Blinky program converts Pin D13 into an output pin. This pin can either be programmed as an input or an output type. I am using it as an input. Unfortunately, the connection to a resistor and LED and then to ground makes it unresponsive as an input, though supposedly you can add a pullup resistor to +5V and get it to work that way. Recommended is a fairly small resistor since the LED is sinking a lot of current (relatively). But no actual value is given.

I tried a 10K and when that din't work, a 4.7K pullup but nothing changed. Finally I got mad at this road blocking #&%! circuitry and applied my soldering iron to the LED's series resistor -- a tiny surface mount speck, and just flicked it off of the board!   :zap:

SUCCESS! Testing again, switch F now works, and I can select all of the metric pitches that I've programmed in.  :thumbup:
25
Software Tools / Re: Experiences, thoughts and rants about using Linux as a newbie after Windows
« Last post by vtsteam on February 22, 2026, 05:36:29 PM »
Yes I agree, all of the appimages I have used were from github, where everything is very transparent. That is where the source code is kept, and issues can be logged, and also the original authors are the ones who have posted and maintained the code there.

Also, a lot of large single application websites also now host appimages for their own applications on their own download page and those are trustworthy.

But third party websites aren't as trustworthy since who knows where the code they are hosting comes from?
26
Member Videos / OKMO Retrol B02 Miniature Gas Petrol Hit & Miss Engine First Start Up & Running
« Last post by Jim Dobson on February 22, 2026, 04:40:17 PM »
OKMO Retrol B02 Miniature Gas Petrol Hit & Miss Engine First Start Up & Running

This is the best out of the box Hit & Miss engine experience that I have had, just an absolutely awesome engine from Jin.


27
Software Tools / Re: Experiences, thoughts and rants about using Linux as a newbie after Windows
« Last post by sorveltaja on February 22, 2026, 03:07:29 PM »
Yeah, I pretty much like the idea of appimage. I went and searched Waterfox one, and thought that 'appimagehub' was a legit source.

Anyway, when launching the expected browser app downloaded from that site, it showed only a text file, which begins like that:

Code: [Select]
!!!DON'T USE APPIMAGEHUB!!!

        .--.         _
       |o_o |       | |
       |:_/ |       | |
      //   \ \      |_|
     (|     | )      _
    /'\_   _/`\     (_)
    \___)=(___/

**Many AppImages on the platform come from unknown or suspicious users.**
I have no idea of what's going on that website, or is it a scam or prank or whatever. So obviously one has to be careful where to download appimages.

On a positive note, there is a site, where the actual Waterfox appimage (among many other apps) is available. I tested it, and it worked right away.

This is about a single app, but it seems that Github-related sites might be more thrustworthy  trustworthy source:

https://appimage.github.io/
28
Member Videos / Re: Stepperhead CNC Lathe Cutting Threads
« Last post by vtsteam on February 21, 2026, 08:39:55 PM »
That makes sense and it's nice to have a consistent spindle speed for more reasons than just threading. I know what you mean about doing something when the workshop warms up. Cabin fever here, waiting for winter to break its grip. This next week shows no sign of that happening. I was hoping to have my new electronic change gear finish mounted to the lathe in the next few days if I get a break from the snow plowing and bouts of bitter cold.
29
Software Tools / Re: Experiences, thoughts and rants about using Linux as a newbie after Windows
« Last post by vtsteam on February 21, 2026, 07:08:50 PM »
Hi Sorveltaja, sounds like there are linux kernel problems. I wonder if the flatpaks might have had a hand in  that. Generally it is thought on the boards I am on that flatpaks are problematic, while appimages are much preferred. Explanation to others unfamiliar with the terms.... these are a relatively recent form of "generic" application packages. Each uses a different method but they basically have all needed dependencies built in, and are supposedly OS agnostic. They are supposed to be able to be installed and work in any Linux.

As I said though, it seems flatpaks are not viewed favorably, at least in the Puppy Linux/EasyOS world. Appimages seem to work very well.
30
Software Tools / Re: Experiences, thoughts and rants about using Linux as a newbie after Windows
« Last post by sorveltaja on February 21, 2026, 04:52:46 PM »
Vtsteam:

Thanks for the offer, good to know.

I should have been clearer about the subject. It (Linux system) isn't VM instance, but actual install on my pc. That Mint Mate installation is still accessible. It boots just fine, but some parts of it are apparently broken.

For example, when trying to uninstall Gimp, it gives following errors:

Code: [Select]
(Reading database ... 571681 files and directories currently installed.)
Removing gimp (2.10.36-3ubuntu0.24.04.1) ...
Setting up linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
Setting up linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-14-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 succeeded for nvidia
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.17.0-14-generic
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.17.0-14-generic (--configure):
 installed linux-headers-6.17.0-14-generic package post-installation script subprocess returned error exit status 11
dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.04:
 linux-headers-generic-hwe-24.04 depends on linux-headers-6.17.0-14-generic; however:
  Package linux-headers-6.17.0-14-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:
 linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.17.0-14.14~24.04.1); however:
  Package linux-headers-generic-hwe-24.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for mate-menus (1.26.1+mint1) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Errors were encountered while processing:
 linux-headers-6.17.0-14-generic
 linux-headers-generic-hwe-24.04
 linux-generic-hwe-24.04
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-14-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 succeeded for nvidia
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.17.0-14-generic
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.17.0-14-generic (--configure):
 installed linux-headers-6.17.0-14-generic package post-installation script subprocess returned error exit status 11
dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.04:
 linux-headers-generic-hwe-24.04 depends on linux-headers-6.17.0-14-generic; however:
  Package linux-headers-6.17.0-14-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:
 linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.17.0-14.14~24.04.1); however:
  Package linux-headers-generic-hwe-24.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-14-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 succeeded for nvidia
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.17.0-14-generic
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.17.0-14-generic (--configure):
 installed linux-image-6.17.0-14-generic package post-installation script subprocess returned error exit status 11
Errors were encountered while processing:
 linux-headers-6.17.0-14-generic
 linux-headers-generic-hwe-24.04
 linux-generic-hwe-24.04
 linux-image-6.17.0-14-generic
After all, it's not a critical system for me, and as mentioned earlier, I've been planning to replace it with another distro anyway.

BillTodd:

It seems you aren't the only one having things like that happen. Rob Braxman has a video where he describes how Win11 and TPM made his dual boot Linux installation inaccessible, without asking or informing about it (~21min):

 _https://www.youtube.com/watch?v=t1eX_vvAlUc
Pages: 1 2 [3] 4 5 ... 10