Advanced Search

Is the info in this thread still relevant to QtDragon shipped with 2.9.7? I have a 3-axis cnc router with a manual change spindle and I'm looking to automate bit offset/height setting with a tool setter input on my 7i96s.

Don’t worry, I don’t know how often I intended to attach something and then just didn’t. I asked when I was still having problems with the PnCconf setup, so it is not relevant anymore. But thanks.

Yes, probably you are right... tomorrow next try

without knowing how and what you did its nearly impossible to guess, you appear to have been using multiple different old version to test or try things, so i would almost say for someone at your level your best bet is a clean build fro the ground up to ensure you don't have any remnants remaining that could muck up future progress.

Pretty sure yes... i got it to work now. But the latency of my new system is really really slow. I switch back to the old one. 

Last question for today...
" i would remove everything and reinstall from scratch using apt only, be sure to purge all installations"
what exactly i need to deinstall and which commands in the terminal?

If you measure the voltage across C36 I expect you will find a low voltage
instead of the expected 4.2V. What this likely means is that one or both
bus switch parts (74CBT16211) have been damaged by either ESD
or by being connected live to the G540 with no common ground
existing between the G540 and 7I92T before they were connected,
exposing the bus switches to a transient high voltage.

Hi.
I've added a custom M199 code to enable my  spindle-index-enable signal, and this runs fine. (Can see the LED light up in halshow when run.)
So now I'd like to build it into my M19, so the M99 runs just before the M19 is called.

In the [RS274NGC] section of my INI, I have put
REMAP=M19  modalgroup=7  argspec=RQP ngc=custom_M19
my custom_R19.ngc file contains:-
( Custom spindle orientation ngc file)
( M199 raise spindle-index-enable signal)
o<pre_M19>sub
M5
M199
G4 P2
M19 R#<r> Q#<q> P#<p>
o<pre_M19>endsub

The G4 pause is just so I can be sure that the signal is enabled in halshow gui.

I'm pretty sure the file is being read at Linuxcnc fire up, as when I remove the file from the macros folder, the startup parser errors with missing file.

After I home the machine and run the MDI command say M19 R20, the M199 and the pause are not being executed.

I feel I have missed something really obvious..  be grateful for a steer. Thanks

Did you do a
sudo apt update
before
sudo dpkg -i linuxcnc-uspace_2.9.8_amd64.deb
?

I had a quick look at the config files in the first thread. However, I do think it would be good with the latest files, as well as the classicladder part.

In addition to what I mentioned in the last post, I would also say you should have a look at these signals when you issue an M3 command:
If the physical buttons are not connected to (only) LinuxCNC, then I guess it could very well be something on the hardware side as well. In that case some kind of schematic would also be needed for "remote" troubleshooting.

Hello and sorry for the late reply. I got a new PC yesterday and i finished to do the Debian 12 installation right now.

I followed the Probe Basic Stable docs...

I stuck on step 3 now 
cd ~

cd Downloads

sudo dpkg -i linuxcnc-uspace_2.9.8_amd64.deb

These are my errors now... Python not installed? If yes how do i install it via Terminal?

Reading database ... 129701 files and directories currently installed.)
Preparing to unpack linuxcnc-uspace_2.9.8_amd64.deb ...
Unpacking linuxcnc-uspace (1:2.9.8) over (1:2.9.8) ...
dpkg: dependency problems prevent configuration of linuxcnc-uspace:
 linuxcnc-uspace depends on libboost-python1.74.0 (>= 1.74.0+ds1); however:
  Package libboost-python1.74.0 is not installed.
 linuxcnc-uspace depends on libboost-python1.74.0-py311; however:
  Package libboost-python1.74.0-py311 is not installed.
 linuxcnc-uspace depends on libgpiod2 (>= 1.5.1); however:
  Package libgpiod2 is not installed.
 linuxcnc-uspace depends on libmodbus5 (>= 3.1.4); however:
  Package libmodbus5 is not installed.
 linuxcnc-uspace depends on libtk8.6 (>= 8.6.0); however:
  Package libtk8.6 is not installed.
 linuxcnc-uspace depends on libudev-dev; however:
  Package libudev-dev is not installed.
 linuxcnc-uspace depends on iptables; however:
  Package iptables is not installed.
 linuxcnc-uspace depends on blt; however:
  Package blt is not installed.
 linuxcnc-uspace depends on mesa-utils; however:
  Package mesa-utils is not installed.
 linuxcnc-uspace depends on python3-tk; however:
  Package python3-tk is not installed.
 linuxcnc-uspace depends on python3-numpy; however:
  Package python3-numpy is not installed.
 linuxcnc-uspace depends on python3-opengl; however:
  Package python3-opengl is not installed.
 linuxcnc-uspace depends on python3-configobj; however:
  Package python3-configobj is not installed.
 linuxcnc-uspace depends on python3-xlib; however:
  Package python3-xlib is not installed.
 linuxcnc-uspace depends on libgtksourceview-4-dev; however:
  Package libgtksourceview-4-dev is not installed.
 linuxcnc-uspace depends on tcl8.6; however:
  Package tcl8.6 is not installed.
 linuxcnc-uspace depends on tk8.6; however:
  Package tk8.6 is not installed.
 linuxcnc-uspace depends on bwidget (>= 1.7); however:
  Package bwidget is not installed.
 linuxcnc-uspace depends on tclreadline; however:
  Package tclreadline is not installed.
 linuxcnc-uspace depends on tclx; however:
  Package tclx is not installed.
 linuxcnc-uspace depends on python3-pyqt5; however:
  Package python3-pyqt5 is not installed.
 linuxcnc-uspace depends on python3-pyqt5.qsci; however:
  Package python3-pyqt5.qsci is not installed.
 linuxcnc-uspace depends on python3-pyqt5.qtsvg; however:
  Package python3-pyqt5.qtsvg is not installed.
 linuxcnc-uspace depends on python3-pyqt5.qtopengl; however:
  Package python3-pyqt5.qtopengl is not installed.
 linuxcnc-uspace depends on python3-opencv; however:
  Package python3-opencv is not installed.
 linuxcnc-uspace depends on python3-espeak; however:
  Package python3-espeak is not installed.
 linuxcnc-uspace depends on python3-dbus.mainloop.pyqt5; however:
  Package python3-dbus.mainloop.pyqt5 is not installed.
 linuxcnc-uspace depends on python3-pyqt5.qtwebengine | python3-pyqt5.qtwebkit; however:
  Package python3-pyqt5.qtwebengine is not installed.
  Package python3-pyqt5.qtwebkit is not installed.
 linuxcnc-uspace depends on espeak-ng; however:
  Package espeak-ng is not installed.
 linuxcnc-uspace depends on pyqt5-dev-tools; however:
  Package pyqt5-dev-tools is not installed.
 linuxcnc-uspace depends on gstreamer1.0-tools; however:
  Package gstreamer1.0-tools is not installed.
 linuxcnc-uspace depends on espeak; however:
  Package espeak is not installed.
 linuxcnc-uspace depends on python3-poppler-qt5; however:
  Package python3-poppler-qt5 is not installed.
 linuxcnc-uspace depends on psmisc; however:
  Package psmisc is not installed.

dpkg: error processing package linuxcnc-uspace (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u13) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for shared-mime-info (2.2-1) ...
Errors were encountered while processing:
 linuxcnc-uspace

Thanks for looking at it.

I was also thinking that the last major change I did was to wire in the spindle VFD brake command. The system worked fine for some time after that, and then didn't.
I did add some Classic ladder Fu in there as well, but that was to the brake command, and spindle brakes normally when I stop it with the external button. I suspect there is something there though, like maybe the physical buttons change switches off the brake command, but the M3/M5 doesn't.

I have the HAL uploaded to the first thread, but haven't uploaded the most recent change, so I will update it this evening.

Don't try swapping drives. At least on mine, the Z axis motor is larger for the extra force to fight gravity, so the drives, PID values etc are all different. I would doubt that there is a problem there. Sounds like a LinuxCNC configuration issue.

Reasonable suggestion. I will dedicate some time tomorrow to extensively analyze and measure what 7K2 does and how it behaves when machine is on, off or with e-stop pressed. I should probably try to see if swapping the X and Z drives won't achieve something. Thank you again, I will post my findings.

I took another look at my Maho's schematics. Seems similar except my 7K2 relay control is hardwired into the "machine on" latching circuit rather than being directly controlled by the CNC.

 

 

Because this is a hardwired signal chain, E-stop drops K1, breaking the chain and therefore dropping 7K2.


So on your set up, LinuxCNC connects to X41 and controls the 7K2 relay, which similtanously enables the drives and releases their brakes. If that is the case, then I have no idea why your axis is dropping, as the Zaxis is getting enabled at the same time as brake release.
Since you suspect a correlation with E-Stop, could it be that E-Stop is not dropping 7K2, leaving the brake off, but some other signal deactivates the drive, so you end up with brake off and no torque? Basically your more modern controller was replacing the hard wired E-Stop chain with some software PLC functionality which you haven't duplicated in LinuxCNC yet?

 

RotarySMP wrote:

Regler (DE) = servo driver module (EN). On my machine it is the Indramat, on yours it is the Simodrive 611.

7k2 is not the servo driver is it? DMG terminology would be that 7k2 is a 24V control relay. On my machine the servo drivers (the indramats) are called 7A1 and 7A2. On yours the Z axis drive is 7A5 (you probably have three separate servo drives on the axis, another on the spindle, and maybe a fifth on a C axis? I only have two.

The brake releases as soon as the 7K2 relay closes. What is the signal chain which energises the 7K2 coil? That needs to happen at the same time as the Reglerfreigabe is commanded through the X331 terminal block on your Simmodrive.   What are the three signals in the X331 terminal block? I would guess the Reglerfreigabe signal , a gnd and maybe the third wire in that cable is a "driver enabled" feedback to the CNC controller. Alternatively, it could be a "Servo Drive Fault" signal.

How did you tie them into LinuxCNC? You need to be setting whatever pin in X331 is the drive enable to active, at that same time as you are energising the 7K2 relay.
 

Thanks for sticking with me through this. B and C are nothing but encoders, their movement is done manually by the operator.

I have a separate main drive for the spindle, a separate drive for Z and XY are on one drive. This, in addition to the control module with the 7 segment display.

I believe X331 contains the Sollwerte and the Reglerfreigabe. The Sollwert has 0V and ±10V connection, so that should be three. The Reglerfreigabe signal links to a different page where it shows it on an Interface Regler and the signal is listed as Kl.65 or 65.1. That in turn is dependent on 7K2. (page attached)

Yes, 7A5 is the Z Regler and 7K2 is its Freigabe relay, right? I believe 7K2 is energized only by the single output signal on X41 (attached page). The other 4 references to it show where its output goes. Regarding how I link that to LinuxCNC, I certainly am not linking the X331 signal to the Mesa directly. I don't see an obvious way to, nor do I think it initially went into the Heidenhain controller. From the looks of it, the signal on X41 that energizes 7K2 relay should be what handles the X331 Reglerfreigabe. It looks to be sequential, meaning X331 will be set after 7K2 closes. Am I understanding this backwards?