Advanced Search

This worked half way. I added a USER_COMMAND_FILE = qtplasmac_custom_post.py with the python code to set the range:

self.w.safe_height.setRange(0.125, int(self.maxHeight))

I can start QtPlasmaC and interactively set and save a Safe Height value as low as 0.125". However, if I save any value less that 0.75", when I reload QtPlasmaC the value is reset to 2" (my maxHeight).

I think this is happening because the load_plasma_parameters method that loads the value from the prefs file into memory (github.com/LinuxCNC/linuxcnc/blob/56e137...py#L2901C16-L2901C27) happens after set_spinbox_parameters which sets the defaults but before the USER_COMMAND_FILE (I'm not yet sure how that file gets invoked with QtPlasmaC to be honest).

This leaves me at a bit of a loss as to how to customize this. I could just write a sed script to change the python code for now, but that seems like a bit of a hack. Anyone have other thoughts as to how this might be achieved?

Thanks!

Scott

Thanks for the Function check PCW.

Will I need to do anything special code wise during configuration on these, or should it mostly be the normal setup
and then just pin associations / various timing variables?
 

H4+ has 2 ethernet ports so you can use mesa+ethercat or mesa+internet

Those ping numbers look OK
(the first is typically longer because it includes an ARP response)

A red LED is expected on the 7I84D since it will have
(as you guessed) at least a watchdog fault when idle

Regarding the uboot, that didn't change, hoping that it was good enough did the trick.

It looks indeed that the chance is small that the SPI driver will be fast enough, still worth a shot, but better not to count on it.
Pinning the irq of the spi to the isolated CPU might help by the way.

I wonder if this is related? forum.linuxcnc.org/ethercat/47710-wago-7...ules?start=10#262402

"Be aware that there are many delta ec02 with a faulty SII Eeprom out there..."

It's a different Delta model, but "faulty SII EEPROM" would explain things.

With the new 5v and 24v meanwell psu's wired up and my network settings updated, I pinged the 7i92T:


--- 10.10.10.10 ping statistics ---
48 packets transmitted, 48 received, 0% packet loss, time 48106ms
rtt min/avg/max/mdev = 0.071/0.099/0.158/0.013 ms


The 0.158ms was the first packet, and watching the output, most were very near 0.100ms which verifies
the 0.099ms avg. Does this sound ok for what I have running on this system?

All three cards were connected so that may have had some effect on the numbers...



There was also a solid red LED lit on the 7i84d, but I am guessing that was probably from a watchdog fault, I've
only just connected them so far and haven't done any other configuration yet. Supply voltage was good.

The numbers I provided previously were the same with the machine powered or not, maybe slightly more zero when powered on.

AC Voltage 0.000 => 0.002 V (no idea why this is expressed in V vs mV)
DC Voltage -0.0 => -0.1 mV (not sure why negative, as even switching leads gives the same negative readings)

I would disable the xhc and see if the problem goes away.
Something else unrelated to jog controller may have
changed on the PC

I have all of that covered. This is becoming a PITA unfortunately. Been running the same kernel and params for ages.
Not sure if anything changed recently but I almost always download the latest code from GIT, compile and run.

Is this something that may have recently cropped up?

It's possible it might actually be the keyboard, on a long shot I tried yet another keyboard (third one), and it actually seems to be working... touch wood.

Time will tell.....

Thanks and hopefully this is the end of the keyboard blues.

Hello LinuxCNCr's,

I have two Bridgeport Interact II mills.  We have been running linuxcnc on the newer (1994) machine for almost two years.  I am in the process of retrofitting the second (older) of the two. The spindle motor was working fine when the TNC controller finally quit on this machine.  The CONTROL TECHNIQUES 6P4Q-7.5 spindle drive on this had issues when it got hot so I want to replace it.   

My question for this forum is this:   Can you help me decide whether I should purchase a (used) DC speed controller and keep the existing spindle motor (specs below) or should I rip it all out and put a 3ph motor and a VFD in it?   I am perfectly comfortable with the 3ph/AC motors and controls, DC motor controls, not so much. 

Parker 514C-32-00-00-00 controllers are available for $700-$900 on ebay.  Can anyone help me determine if this Parker controller will work with my spindle motor? 

Is there a better fit?  

Thanks in advance!

Here are the specs for the 514C https://www.dropbox.com/scl/fi/hj4h7877623h1s3tfxqhz/2024-04-27-18-08-55.png?rlkey=nlu0re6uxcjp6e2iqigox4y6e&dl=0 (screen grab from 514C manual) https://www.dropbox.com/scl/fi/hj4h7877623h1s3tfxqhz/2024-04-27-18-08-55.png?rlkey=nlu0re6uxcjp6e2iqigox4y6e&dl=0

The manual for my 6P4Q-7.5 drive describes my spindle motor as follows:

Motor type 2M112L
RATING IN CONJUNCTION WITH 6P4Q-7.5 DRIVE MODULE
  0KW at  Orpm
  8KW at. 1000RPM
  6KW at  4000RPM
  4KW at  6000RPM

ARMATURE
  Voltage - 400V
  Current - 0/27/18.5/14A

FIELD
  Voltage - 150V
  Current - 3.8/0.78/0.48A

MOUNTING
 Special flange
EXTRAS
Two microthermal sensors embedded in the windings

VENTILATION 
Separate three-phase motor-driven fan unit with air filter mounting on main motor frame
Voltage - 380/415V
Current - 0.7A

TACHOGENERATOR
Direct coupled to main motor armature spindle. 20V/1000 rpm

Nice! Have you considered a panel mount keyboard? MIght add  a bit to costs but save a lot in wiring!
www.aliexpress.com/item/4000575816352.ht...023.6.28709HVP9HVPeU

Hi! Just to show the thing I am working on 

Sorry, is that with the machine fully powered down?
-
Another thing to test, when the machine is powered on, use the DVM to measure first DC voltage between those pins, then AC voltage between those two pins.
Should be 0V to max 0.1V to allow for measuring errors.