Advanced Search

Since 2008 I have been using linuxcnc, I remember running into a problem in the G85 code (it was malfunctioning). I am an expert in cnc technology and I am very used to the G-code in all the controllers that exist. I remember entering the forum and raising the problem and it was immediately solved. This experience was never repeated. I'm not complaining, I'm posing a problem! It seems that for some members (luckily not all) the linuxcnc Forum has become a place where users must have knowledge of github, programming, compilation, editing, etc. every time the solution to a problem is blocked. In order for linuxcnc to continue improving, they must accept the Forum as a place where they can find the problems to be solved, because this is where the users who are using the application are located. I'm really tired of members who impose their hierarchy of knowledge on those who don't have it.
For my part, nothing more to talk about in this thread. Thank you!!!

i'm doing the same in github.com/yur7aev/linuxcnc/tree/nyx2.9/configs/nyx/argo like that:

o<m6> sub
(AXIS,hide)
... tool change with out of limit z move ...
(AXIS,show)
o<m6> endsub [1] ; signal success
m2

You can test   if [#<_task> EQ 1]    to skip this sequence in preview

Hi All,

Good day. Managed to wire the ENA to the servo drive enable.

My current problem is overshoot. lets say I command it y5, it will go until y6 then go back to y5. Overshoot increases as feed speed increases. I estimate it to be 1mm per 100mmpm. so 100mmpm has an overshoot of 1mm, 300mmpm has an overshoot of 3mm.

PID settings are
P = 1.5 (If i add more, it shakes at higher speed)
I = 0
D = 0 (any increase and the system shakes)
FF0 = 0
FF1 = 1
FF2 = 0
Scale : 1225 (0.01 accuracy even with overshoots)

Regards,
Kibin

Hi All,

Good day. Managed to wire the ENA to the servo drive enable.

My current problem is overshoot. It is overshooting. lets say I command it y5, it will go until y6 then go back to y5. Overshoot increases as feed speed increases. I estimate it to be 1mm per 100mmpm. so 100mmpm has an overshoot of 1mm, 300mmpm has an overshoot of 3mm.

PID settings are
P = 1.5 (If i add more, it shakes at higher speed)
I = 0
D = 0 (any increase and the system shakes)

Scale : 1225 (0.01 accuracy even with overshoots)

Weird that it works with a small modification in a minimal running example but not in gmoccapy:



Maybe you have some time to play around and figure it out if it is important for you.

Hello,

I'm working on a mill which make Z+ move to free the tool in spindle.

I need to go to Z++ to disengage locking, but i have to keep under Z25 when machining.

I set up a mux2 component with 2 Z limit values
I normal operation Z limit is 25 and while toolchange Z limit is 180

If i run m6 txx, it works fine, but if I load a program, the plot complain about Z limit, because M6 subroutine mention off limit Z move
If I launch program, linuxcnc complains about Z limit too, but program runs nicely as my limit is moved when it have to

Anyone have an idea to fix this ?

I've tried to add a conditional state before the Z move, but linuxcnc still see the move while plotting

Thanks

PostavCNC wrote:

Hi, there,

i am trying to make a keyboard shortcut to toggle between TURTLE and RABBIT jog mode. I think that the code should have look something like this: 

        if keyname == "r":
            "some toggle event goes here"
            return True

It is shown on in the def on_key_event section in the code attached from line 3052. Can you help me which event should I use to toggle jog modes? 

 

Toggling does not really work without further changes, because it toggles the button twice then.
Adding two buttons is the simplest solution if that works for you.

To Aciera

It's not very well documented, but you have to set the counts value when you use direct value
It takes me some time to figure it out as I made my tests with spindle speed override and it's not working

From this hereIt looks like you are including basic_sim.tcl. You got to remove that inclusion.
It's in the .ini file, comment out that line, the line looks something like HALFILE=LIB:basic_sim.tcl

I created confusion there. The 784 is not powered by the 200 rail (which is switched on and off with Machine start / Estop), it is wired to the 204 rail, which is on constantly when the machine main switch is on.

Hi everyone,
I'm hoping that someone can help me get my head wrapped around this, and point me in the right direction.  I've spent over a dozen hours reading through threads on this forum and elsewhere - yet, I can't figure out how to proceed.

My machine is a Bridgeport Series I CNC (Boss 6) mill - and it's sitting in my shop in original condition.  I'm new to CNC (having only dabbled with my Ender 3 3D printer).  However, a close friend of mine who's helping me has a couple of HAAS mills and is a guru with Autodesk Fusion.

I've investigated numerous options for updating this machine.  The more I study this, the more confused I've become!  The simplest answer for a person like me seems to be to install an Acorn board.  I'd rather not.  I don't want to get vendor-locked (more than I have to).  The thought of a company going under and leaving me in the position of having to gut the machine and start over is not appealing.  I don't want to pay a subscription.  I like the openness and configurability of LinuxCNC, and I'm a big fan and daily user of Linux (Red Hat Academy instructor).

My goals:
* Get the old Bridgeport back to making chips again.
* Have the ability to both use this machine as a CNC, and as a glorified manual machine (using LinuxCNC as a DRO).
* Not spend thousands of Dollars on this project (if possible!).

My thoughts:
* Mount a 12" touchsceen monitor in the original control panel housing for interacting with LinuxCNC.
* Hang a pendant on the side of the original control panel housing.
* Pick up a Huanyang VFD for the spindle drive (these seem to be well-supported and well regarded?).
* Replace the ancient original Bridgeport steppers with modern closed-loop NEMA 34's (1100-1200 oz in).

My questions:
* What should I run LinuxCNC on?  I've got a spare RPi 4 sitting in my drawer.  I've got a couple of Supermicro Intel Atom-based ITX server motherboards lying around.  What's the most intelligent way to go?
* It seems that a parallel port interface is the "old-school" way of doing things.  Now, it seems that most prefer an Ethernet interface.  Is there a disadvantage of going one way or another?
* Since I have to replace the steppers anyway, is it foolish to go with a "traditional" setup rather than Ethercat?  It seems like Ethercat will be considerably more expensive (like twice the price or more) - but is it worth the price?
* Everyone seems to agree that Mesa boards are the "gold standard."  How do Pico Systems' boards compare?  Jon Elson lives like 20 miles from my house.  Does anyone have experience with his customer service?  Is it foolish to consider anything other than a Mesa?
* If I go with a Mesa setup, which direction should I go?  If I use the RPi, I could go with the 7C80 or 7C81 - I could also run an Ethernet setup.  If I use the server motherboard, I could go with a parallel port setup or an Ethernet setup.  Is there an advantage of going one way or another, here?
* If I go with a given Mesa board, what else will I need to buy?  It seems that some of the Mesa cards (like the 7C80 and the 7I95T) will hook directly to the stepper drives, while others require a separate daughter card (BoB)?
* What hardware (if any) would I need in order to use the encoders on the steppers as a DRO?  Will any of my hardware selection above affect my ability to have this feature?
* Will a cheap Amazon/Aliexpress stepper motor/drive/power supply set work, or will I need to buy the stepper drives separately?  If I need a particular stepper drive, should I go with a Gecko or something else?
* If I run a touchscreen and a pendant, is there any reason why I will need a keyboard hooked up to this machine (once it is configured)?

Sorry for all of the (possibly stupid) questions.  The DIY CNC and especially the LinuxCNC ecosystem is far more vast than I imagined.  I really did attempt to "do my homework" before asking.  There just seems to be a lot of somewhat conflicting information (possibly, due to changing technologies and best practices over the years?).

Thanks for any advice that you can provide to me!

I've solved it
1. Synchronization problem of gantry and conveyor belt, use an external encoder to record the position of the conveyor belt

I want to use vision to determine the location of the item, and I can achieve this too.
When items are placed on the conveyor belt, they will continuously place items on the conveyor belt. My camera and program will also constantly collect images to calculate the location of each item.
I can generate G code to control its running.
But I can't solve multiple G-codes at the moment (the continuous stream of items are placed on the conveyor belt) when will they start running
Ideally, the running signal of each G code is triggered by the encoder position.
But I don't have a good idea to achieve this. Does anyone have a better solution or idea?
 

Right now, the 7k1-131 relay contact is disconnecting the 24VDC supply to mesa 7i84 board which is no, no as indicated by Tommylight. I can suggest you jumper 7k1=131 contact and replace the single pole relay 7k1-131 with a 3-pole relay to disconnect the 3 phase AC side of 6V1 power rectifier. let me know, if this info does not make sense, I can draw a diagiagram.

Self.execute was it! Finally getting back to the python testing. I pretty much got the rest of the machine up and going and it makes more sense to use the python M6 remap for a more automated experience with all the different tools on the Biesse. By the way thanks so much for posting your Biesse upgrade bevins! Mine is up on github also and plan to do a post covering my project. Been a learning experience!