Advanced Search

same problem.. It didn't change anything
If I go F1000 or F10000 the error are the same...

The problem isn't so much with Linuxcnc, it is more an inherent limitation of G-code itself.

To do what I think your asking for, you would almost have to have two separate G-code interpreters executing two separate, yet some how synchronized g-code files. I think there are some high end control systems that can do such things, but it is currently beyond the scope of Linuxcnc.

That said, I think I can imagine two separate Linuxcnc control computers on one machine linked with some of digital io bits to synchronize a set of parallel processed files. It could work, but would require some experimentation, and there may be unforeseen pitfalls.

I would like to change the email address.  I changed it in the profile settings.  However I don't think notifications from topics I've subscribed to are being sent to my new address.  Is there something else that I must do?

Does LinuxCNC run without error? maybe installing the driver is sufficient.

Yes, set those both to 20000 (for all joints)

Realtek driver R8168 installed. It certainly improved tmax parameter (hm2 read tmax was 3330000, now 1300000).

But IRQ could not be set to CPU1 automatically. PCW script sets it manually, but mozmck script did not work, at least till now.

Yeah, I'd like to share and potentially contribute. I'll admit I kinda hacked together the conversational portion. What do you need from me to check it out?

DIRSETUP = 6000
DIRHOLD = 4000
 This?

spumco wrote:

That would be a great addition to Probe Basic.

I'm not sure it can be done - but I'm no expert.

My initial thought is that the on_abort subroutine is run while LCNC is in auto mode... so there's no way for a program to switch to manual (or MDI) mode.

I'll dig around a little and open a new thread - the issue (or solution) may not be specific to PB.

Thanks Spumco,  I briefly looked and saw there is a python module to for the status but i don't see a method of issueing a mode change from within a subroutine, at least not at first glance, if there is a method im not sure how it would handle changing the state from within an auto mnode program to manual mode and close the running subroutine which would need to be done in auto mode.. chicken/egg scenario maybe?

task_mode
(returns integer) - current task mode. one of MODE_MDI, MODE_AUTO, MODE_MANUAL.

i used this for some of the display button states in probe basdic but not sure how much help they would be.  may need a module added or perhaps there is a feature function somewhere else im not aware of.  I also have previously considered having some way to abort to manual mode, but then i think well thats a safety thing too so you don't inadvertently move the machine when it is in a precarious spot, such as the probe down in a hole where it errors from max distance non probe trigger,   so.. while a minor inconvenience, maybe saves a major cost or crash?

 

I downloaded lcnc_irqpolicy.sh.txt.
My NIC is "enp4s0" and Mesa ip=10.10.10.10.
I made the modification in the above file and modified file attached. Please check whether any further correction required or it is ok.
============================================================================================================
NIC=`awk 'BEGIN{nic="enp4s0 "} {if ($1=="iface") {tmpnic = $2} if ($1=="address") {if ($2 == 10.10.10.10 ) {nic = tmpnic}}} END{print(nic)}' /etc/network/interfaces`
============================================================================================================

you are not in full screen mode, hit F11 to allow the display to correctly fit the screen.

Yes, it's ok now, thanks..

below text copied from

www.plctalk.net/threads/surge-protection...ng%20are%20at%20risk.

First, eliminate the idea that any protector does protection. Did you really think a protector would somehow block or absorb a destructive surges? Anything that might do that must already be inside electronics.

Second, a destructive surge does damage if that PLC is the best connection to earth. If a surge can blow through a PLC, then it easily blows through 'blocking' or 'energy absorbing' protectors. But if connected low impedance to single point ground, then nobody even knows a surge existed. That energy dissipates harmlessly in earth.

In most facilities, single point ground means wires inside every incoming cable connect low impedance (ie 'less than 10 foot') to the single point ground. All wires enter at the common (service entrance) location. All connect low impedance to one ground. Make that connection either directly or via a protector.

Thanks for the info.
Mine is an Intel MacBook 2012

Could you point me to some info on how to disable IRQ?

Ok. try again should work now.