Advanced Search

Yes, the enable signal is needed. But you need to set up the driver and motor first.

Hello folks. 
I am processing pieces in my machine. My CAM program is Fusion 360. Sometimes the pieces are being so detailed, so the generated tool paths being so complicated. I've noticed that complicated tool paths are giving the .ngc file with very big sizes. The generated .ngc file is being so big, and i want to interfere the generation of G-code. I think it can be less complicated with optimization. For example, think about the machine is gonna do face operation. There are many repeated lines in g-code(not in appearance, but in logic). As a result, they are doing the same thing. Go to end of peace, come from there, repeat...

I am wondering about is there any way to simplify or optimize generated Gcode? The method is gonna be like identifying repeated operations and putting them to appropriate loops(for, while, do-while...). I've thought it can be possible in Post Processor, because it has access to tool paths directly, and this component is the last component which touches to the machine specific code. To be honest, it can be weird because adding operations like i said may not be time efficient. If you're already gonna generate long lines, it can be longer with this operations. But if it can be done, it would be very nice about storage size. Some files are about 10'000'000 lines, or more. 

As a second choice, i considered an external program as an optimizer. This program gonna get the posted .ngc file as input and examine it's contents. With appropriate operations, it's gonna determine which moves can be done in loop and it is gonna put them in appropriate loops. The main problem in here is that the commands may not look the same but they may be doing the same job. Because of this, this program needs a strong logic to determine repeated moves in the context of CNC machinig.

These are my questions:
1. Have you guys ever thought about this kind of situation? Is there any ready to use tool, or does my idea makes sense?
2. What about doing this process in post processor? Does it make sense?

Thank you for your time.

Maybe you could use your gamepad instead. Lot of buttons on those things.

Hi All
Have just brought a chinese 2.6 kw braked servo to run the z axis of my Deckel FP4.
The smaller 1kw servos i brought a few months ago came with pre wired tails to connect up to my mesa 7i96S and i have had them up and running fine.
This new driver however came with a bare plug and some chinese instructions 

I have wired up the new plug according to the wiring with my step and dir signals going to pins 37 39 41 and 43
  

Fired up linux cnc to no result.
Brake was released manually before hand.

Tested using one of my x and y outputs also to see if it was a configuration error which it doesnt seem to be.

once the brake is released the motor can still be spun by hand almost like the drive is not sending power to the motor.

Ive had the motor turning under a test cycle after which the motor shaft will lock up like it should.

I also had a thought that this driver might need an enable signal which i tried to replicate by bridging pins 11 and 9

any other ideas as i am running out.
 

Just to demonstrate a way to start a component through a custom Mcode which could then be called as a [HALUI] MDI_COMMAND with a hal signal, (Note this uses 'hal_input' component to connect the volume_up function key to the 'axisui.notifications-clear' pin so this may not run on your hardware as is but you get the idea):

1. I save this as 'M123' in the USER_M_PATH and mark as executable:
2. I save this as 'myhal.hal' in your config folder:

3. I start the config, home and after I run 'M123' in the MDI command line I can delete notifications by pressing <Fn>+'F3'

Might also work with your 'gs2_vfd' component

This may be of interest:
linuxcnc.org/docs/devel/html/code/code-notes.html

Here store.mesanet.com/index.php?route=produc...oduct&product_id=116 is:

"Up to eight 0.0V to 3.3V analog inputs are also provided. "

But small notes in manual explain:

"Inputs 0 through 7 can read analog signal values however only inputs 0 through 3
are supported for analog input by available interface modes."

So hardware can works with 8 analog inputs, but software can send to LCNC only 4 analog signal.

The only stuff for save this project is if PCW would make "mode 4" for 8 analog inputs.

Another way is to ditch the 7i73 and use an Arduino with a SmartSerial slave.

Hi guys as the title says I am planning on retro-fit to my 1997 Deckel-Maho DMU 50T. It is a 3 axis machine with 2 manual axis’s on the table. 16pos ATC.

I was about to pull the trigger on a Centroid Oak system, but it appears they don't support my drives, so I got to more searching and found / re-found linuxcnc. So here I am, after searching this forum and watching some (many) youtube vids I think I am better off here.  Below is copy pasted from my post over there.

My machine currently has the following controls and drives.
* Heidenhain TNC 426 cnc controller
* Siemens 611 drives fitted with a Heidenhain interface control card / board.
* Siemens Servo motors – 1FK6 series with 1Vpp encoders feed back direct to the TNC
* Siemens spindle motor - 1PH6 series with 1Vpp encoder fed back direct to the TNC
* Heidenhain LS486 linear scales on the X, Y, Z. +-5um accuracy ( I think, still looking for exact specs on these)
*Manual axis’s have Heidenhain ROD280 encoders on them both.

I have only just unloaded it from the truck, I have not yet had it powered up but it had been inspected and running before I bought it. I would like to change to a more modern system, hopefully the sale of all the TNC hardware will help too. It is in very good condition.

I have come up with the following solutions to the conversion requirements if you could please have a look and see if I am in the right direction.

1. I will need to remove the Heidenhain interface controls from the 611 and replace with a SIMODRIVE 611 HR universal controller 6SN1118-0NH01-0AA1, I am going to need 3 of these. From reading the Siemens functional manual on the 611 it appears I can wire the 1Vpp encoders to this control board and program a pass through for these signal which converts to TTL format which i can use with a Mesa board.

2. I “think” I can then control the 611 in velocity mode via analog signals +-10v

3. I have found an Aikron signal converter which can convert the scales and manual axis encoders to TTL to connect to the OAK via and expansion board www.aikrondro.com/product/signa ... a-and-ttl/   it would be good to see if these work as I have a total of 5 1Vpp encoders to read not including the ones on the servos. I have looked a the exe601? heidenhain ones and they appear to be pricey second hand.

A few things I am unsure of, it appears this machine uses the scale feed back as the hard limits not proximity switches, I cant see any other way it would do it with the hardware fitted. Can I do this with linuxcnc?

The 611 controls I am looking at have Nset ( which I have deciphered to mean analog control) and Positioning mode. It appears it can do position via digital inputs, but I would lose the encoder pass through option as they use those pins. It also has Positioning via Profibus DP.... can of worms Im sure.

Further to this, how does the controller control the spindle? Is it the same analog format? As it is the same control board in the 611.
How would the manual axis's integrate? Can this be utilised in conjunction with the servo encoder feed back / closed loop or is it just a DRO style output.

I have only begun looking at the mesa options, I am pretty sure I would go for the ethernet version 7197T as a start but I am still working through these options. I am going to sit down and fully map the IO on the mill so I can get a good picture of what I require. I have full schematics and manuals so I am very lucky in that regard. I have scanned both if any one has need of them.



There is probably more but this will get me started. More photos to come. Thanks Str8

Hi everyone, I’m relatively new to LinuxCNC—just a couple of months in—and I’m looking to customize it for my project. However, I’m struggling to understand how the source files are organized, which file serves what purpose, and how to work with them effectively.Specifically, I’m interested in:

• Motion Control: Which files are responsible for motion control, and how can I modify them?
• G-code Interpreter: Where can I find the G-code interpreter in the source, and how is it structured?

Is there any documentation that explains the structure and purpose of different source files? Also, any tips on how to debug or troubleshoot custom modifications would be really helpful.Looking forward to any guidance or resources you can share!Thanks in advance for your help. 

It does actually have an enable pin but it isn't listed in the documentation:

The 'gs2_vfd' component does not seem to have an 'enable' pin:
linuxcnc.org/docs/stable/html/man/man1/gs2_vfd.1.html

   

I

   

Attached are some photos.

what about the gs2_vfd enable pin?