Advanced Search

Hi kn612,

Were you able to get motion with your analog servos as well? PCW was kind enough to send me a 7i97t for testing as well. I will make a pull request to add it to 2.10/master when we confirm it.

Yes, if the input common is a + voltage, those are sourcing inputs.

( it's easy to get confused as sourcing inputs connect to a sinking drivers and vice versa ) 
 

hi i am on the same point... could you share your solution please?

This solved it.
sudo rm /etc/{initramfs/post-update.d/,kernel/{postinst.d/,postrm.d/}}z50-raspi-firmware

Just wondering if the MODBUS plugin will handle analog input modules, for things like feed/rapid/jog override? Modules like this one :

www.aliexpress.com/item/1005007137758623...3A#nav-specification

I am happy to purchase one for testing if it helps.
Cheers.
Russell.

OK, only just at the end of last week, I was given an Ender 3 original, my very first 3D printer.

Having seen how crap the mechanical design is (why didn't they just make it out of soft rubber) I wondered about DIY builds, but after chatting with the guy who gave me the printer he said just buy one. I do a search online and seems many say you don't save much money over a ready made one.

However, I look at the price of larger printers and they seem to cost a few thousand.
My studies over just this weekend have shown me that the dedicated 3D printing mainboards are freely available, not that expensive, and quite configurable.
Firmware such as Klipper / Marlin is free. 
The slicing software is free.

So it seems it's just the price of the hardware/parts that is the main cost. And I know I would have a rigid and accurate build with good repeatability.
And if I can pick up an old used printer cheap I could use all the existing working parts on a quality built frame.

What's the experience of those who've built their own 3D printers. When it comes to a larger machine, say 450 cubic and up, do you find substantial cost savings or was it other reasons you went the DIY route.

Hi;
I've tried to setup an ethercat catio-a for pwm to control a vfd. Initially i followed this post: forum.linuxcnc.org/ethercat/52997-etherc...module-help?start=10 to get me started. In the cia402.hal i've added "net spindle-pwm => lcec.0.0.PWM-OUT-0" and "net spindle-duty =>  lcec.0.0.DUTY-OUT-0" 

within linuxcnc/ halshow/ watch pins i can set the spindle duty and spindle frequency. The biggest problem is i'm not sure where to go from here for configuration to have a set frequency and pwm tied to spindle rpm. To me, is seems all of the spindle documents don't apply to (CIA402) ethercat io modules.

I should note that i'm a complete lcnc noob so there's more than likely something i've missed along the way. I'm hoping to get some help from someone that's successfully setup something like this in the past. 

cheers

There is a folder with sim configs for extrajoints:
'configs/sim/axis/extrajoints/'

1.)Hello,Is this connection of the 7i96 inputs identical / similar for the 7i95T?

2.)What is the connection diagram for MPG ENCODER INPUTS (7i95T)?

I have a problem - in the manual for the 7i95T (page 17) it says:

" MPG ENCODER INPUTS
Standard 7I95 firmware provides 4 quadrature MPG encoder inputs on isolated
inputs 0 through 7. Since the input threshold on isolated inputs is about 3V, its best to use
sinking inputs (with the input common terminal tied to +5V) with TTL output level MPGs." 

Isn't that sourcing input?

Thanx

I'm converting over an old Koike Oxy Fuel table that has a Burny controller on it to run on Qtplasmac. Swapped out all the electronics. Can move the axes around how I want and it'll run whatever shape I program. However a few issues in running into, probably just me overlooking ini file settings.
1. The torch won't activate at all when the program is running. The torch only works when I manually hit the "Torch Pulse" button. 
2. I have a manually controlled Z Axis, no need for that auto height stuff on Oxy Fuel cause the height not being right is more forgiving. But the problem I run into is when I go to run a program without homing, it follows the path it should, but when I do home it goes to cut the shape and then the Z Axis starts moving on the screen and it throws the error "bottom limit reached while probing down". I feel like there's some simple solution that might fix both of these problems that I'm just not seeing. 
3. Also a third random question while I'm here, I know I can set various pierce times for different materials but it's there a way to force the machine into always manually piercing, like a M1. But in the parameters/in, I that itll pause and make me hit like cycle start or something to do the pierce. Cause while I can let it run auto, pierce times are more finicky with oxy fuel and it can vary day to day and plate to plate.

Did not work.

sudo apt purge --autoremove raspi-firmware
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  linux-image-6.1.0-35-rt-amd64 raspi-firmware*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 409 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 230177 files and directories currently installed.)
Removing linux-image-6.1.0-35-rt-amd64 (6.1.137-1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-35-rt-amd64
/etc/kernel/postrm.d/z50-raspi-firmware:
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/kernel/postrm.d/z50-raspi-firmware exited with return code 1
dpkg: error processing package linux-image-6.1.0-35-rt-amd64 (--remove):
 installed linux-image-6.1.0-35-rt-amd64 package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 linux-image-6.1.0-35-rt-amd64
Processing was halted because there were too many errors.
W: Can not find PkgVer for 'raspi-firmware'
E: Sub-process /usr/bin/dpkg returned an error code (1)

skunkworks wrote:

Yes - unchecking autovolts then uses the material voltage. Duh

thanks again
sam

Yes, this is preferred in my book. You want to know the torch height and the voltage quoted in cut charts may not be correct due to worn/eroded electrodes etc so its far better to sample the torch voltage once the voltage has stabilised and keep that constant. There is a very high correlation between torch voltage and torch height so  its an excellent process control variable. This is covered in the Plasma Primer in the docs.

This is a known Debian bug
try
sudo apt purge --autoremove raspi-firmware
sudo apt update

Hi, can someone help me with this error? It's a fresh install on a laptop.

sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
Need to get 0 B/69.1 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up initramfs-tools (0.142+deb12u3) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-6.1.0-37-rt-amd64 (6.1.140-1) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-37-rt-amd64........]
dkms: autoinstall for kernel: 6.1.0-37-rt-amd64.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-37-rt-amd64
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-37-rt-amd64 (--configure):
 installed linux-image-6.1.0-37-rt-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-rt-amd64:
 linux-image-rt-amd64 depends on linux-image-6.1.0-37-rt-amd64 (= 6.1.140-1); however:
  Package linux-image-6.1.0-37-rt-amd64 is not configured yet.

dpkg: error processing package linux-image-rt-amd64 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-37-rt-amd64
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 linux-image-6.1.0-37-rt-amd64
 linux-image-rt-amd64
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1) 

Thank you very much Andy.
I will give this a try too, although I first need to understand this, hehe.

After some testing, my proposal does not work reliably.
After a couple of probing commands, the error comes back.

I first thought about a race condition, so I also tried the synced
M62/M63 and isolated everything with G04 dwell commands,
up to 1s, like this one here:

After some debugging, it's clear, that the G38 command itself
triggers this error. Most likely dIrectly after the probe made contact.
The short time between the (sucessful) end of G38 and my custom
"probe off" command seems to be the zone, where this happens.

If this is true, probably not even Andy's solution would work here.

To be clear, yes, there is a _lot_ of bouncing involved here.
I am directly probing with a 0.1mm cutter and the touch probe
is connected to the galvanically isolated material.

But this all was working in the past; I almost used this daily,
with previous versions.

Is there a latching element available in HAL?
A flipflop? That might help here, if it's fast enough.

Otherwise, the last resort would be a HW latch - if the bouncing
is the cause of this. If it's just the static "probe HIGH" signal;
well - no go.