search for: linuxcnc

Hi Jean-Roch, No. There is no user-facing firmware update process available. If there are any particular commands you're interested in on a newer unit, I can look them up. ________________________________ From: jean-roch blais <blaisjeanroch at gmail.com> Sent: Friday, January 3, 2020 6:13 PM To: David Zomaya Cc: nut-upsuser at alioth-lists.debian.net Subject: Re: [POSSIBLE FRAUD] Re:

On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > On May 7, 2019, at 5:06 AM, Gene Heskett wrote: > > New testing install(stretch) > > pulled in nut stuff from repo. > > copied old wheezy configs to /etc/nut, overwriting the resident > > files can't talk to ups, missing usbhid-ups file > > Gene, > > What do you have in /etc/nut/ups.conf? (There

...ode when you plug in the UPS, it's probably a USB-to-serial adapter wearing a funny hat. From the NUT driver perspective, if the UPS is on /dev/ttyUSB0, it is considered a serial UPS (despite the physical USB cable). That said, other serial devices may show up as /dev/ttyUSB0. If this is, say, LinuxCNC, be sure that you aren't configuring NUT to send UPS commands to a motor controller or something. > Should I put the full path to it in that driver= statement, Charles? No, not necessary. > But this kernel might not like it, its for 32 bit i386's according > to "file"...

On Feb 19, 2015, at 8:55 AM, Gene Heskett <gheskett at wdtv.com> wrote: > On Wednesday, February 18, 2015 08:11:13 PM Charles Lepple wrote: > [...] >> On recent Debian and Ubuntu with 2.7.2 and >> earlier, there was an issue where the udev rules file needed to be >> renamed from 62-nut* to 52-nut* in order to not be overridden by >> another set of rules. It

On Wednesday, February 18, 2015 08:11:13 PM Charles Lepple wrote: [...] > On recent Debian and Ubuntu with 2.7.2 and > earlier, there was an issue where the udev rules file needed to be > renamed from 62-nut* to 52-nut* in order to not be overridden by > another set of rules. It lives somewhere like /lib/udev/rules.d Charles; I assume this is the message you refered to, so I just

...n the box to cool its surface. So the motor supplies and motor drivers are in the box, and supply their own fans, leaving room on the inside of the door for the controlling interfaces and two SBC's: A Raspberry pi 3b (4 core arm64 @ 1.2GHz, and a gig of ddr3 ram) to run the program, called LinuxCNC. And an odroid64-c2, faster 4 core arm64, 2GB of ram, which should handle the graphical duties of controlling the program as it claims to be able to drive a 4k display at 30 FPS. I have tried running X on the raspi, but it hasn't enough memory or iron to do it well. With only a gigabyte of...

...e: x86 (IA32) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: joachim at falaba.de QA Contact: xorg-team at lists.x.org LinuxCNC Live CD (Debian Wheezy is the base distribution) hangs with some Nouveau messages. Since I'm not allowed to install it on a PC with K2200 in our facility, I can just use the LiveCD or USB-Stick with persistence mode. Is it somehow possible to get a kernel log in this situation? -- You are re...

On Mon, 2023-05-22 at 15:54:51 +0200, Matus UHLAR - fantomas wrote: > > > gene heskett <gheskett at shentel.net> writes: > > > > Which file in the nut I pulled a month ago, should I start with to get > > > > the new version actually running? I still get - -V=2.7.4 > > > On 5/22/23 07:13, Greg Troxel wrote: > > > It is likely that you have

Gene's posting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011654.html contains a NUT 2.7.4 update for the APC Smart-UPS_1500 device dump at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html Please note the changes since the 2.7.2 report, e.g. ups.delay.start is no longer supported. Roger

...> it's probably a USB-to-serial adapter wearing a funny hat. From the > NUT driver perspective, if the UPS is on /dev/ttyUSB0, it is > considered a serial UPS (despite the physical USB cable). > > That said, other serial devices may show up as /dev/ttyUSB0. If this > is, say, LinuxCNC, be sure that you aren't configuring NUT to send UPS > commands to a motor controller or something. > > > Should I put the full path to it in that driver= statement, Charles? > > No, not necessary. > > > But this kernel might not like it, its for 32 bit i386's acc...

...rked perfectly on ubuntu-10.04.4 LTS. Wheezy is dead stable, but actually getting something done with it is almost always a maddening battle of wits. I have a single sided printout, 88 pages of 24 lb, but IIRC my 3 hole punch, a good one, is out in the machine shed where I was last updating my LinuxCNC doc's. And its currently +2F & nearly a foot of snow to plow to go get it. And of coarse I'll need to find a 3 ring binder that I can recycle to be a nut doc holder. 1 step forward seems to be a 2 step backwards in real life. I don't even know if I am using the correct driver,...