Advanced Search

If it does not count reliably, it suggests a problem with
the quadrature.

The count should be absolutely consistent.

Tommylights suggestion to use an oscilloscope is good.

Also if you can run the spindle at (very) low constant speed you can look
at the encoder A/B signals with halscope.

The signals to watch are:

hm2_7i92.0.encoder.00.input-a
hm2_7i92.0.encoder.00.input-b
hm2_7i92.0.encoder.00.input-index

( assuming the spindle encoder is encoder 00 )

I wrote this parametric G-code program and it seems to run fine on my simulation machine.  But when I try to run it on the real machine it stops at line 20  and gives (Does not exicute line 20) no feedback as to why.  However my simulation machine is running Linuxcnc 2.9, and the real  machine is only on 2.7. 

When I press button Touch Off, i see menu. When I enter my value, can`t press OK

linuxcnc 2.10 Axis Lathe configuration 

See:
forum.linuxcnc.org/show-your-stuff/55248...-table-rotary#320834

Hi everybody,
i found some threats (e.g. Simulate a mesa 7i96 (solved)) where a component was written for mocking a 7i96e mesacard. Nevertheless i didn't found this component code published and as i'm using myself a 7i76e card i wrote a component on my own for mocking/simulating this driver.
My idea was to use the same .ini and .hal-files (and .tcl-files with some if statements -)) as on my real milling machine to keep the adaptions between simulation and real machine as low as possible.
In case it is interesting/helpful, i put the component-code on github.com/pkl42/linuxcnc_components_sim.git 
Also not all available pins are included right now, i added a detailed list on the git repository.
I tried to write the component in a generic way, so it should be quite easy to add missing pins or even adapting a 7i95 or 7i96 card. 
 

Easy, just make as much as you need/like of configs that fit your hardware, use the wizard to create each of them.
Although, plasma will not play nice with other features due to huge amounts of fine metal dust that blackens everything.

grossman83 wrote:

What I think I've discovered is that the system undercounts in the forward spindle direction, but seems to count properly in reverse.

Do you have a scope to monitor A and B encoder lines?
-
I had something similar a few years back with a china encoder where the pulses were correct in one direction, but would get thinner with speed on the other direction.
This was a new out of box encoder, the same make/model encoder worked properly after replacing it.

I'm having threading issues where the machine cuts a slightly different thread each time. This has always been the case since I retrofitted a late 70's CNC lathe 8 years ago. Recently I've decided I've had enough and want it running "perfectly" which is why I'm finally digging into the issue.

Initially I thought the issue was due to noise on my encoder lines. I finally tracked down the source of the noise I had and it was EMI from my cheap chinesium servo drives. I've thoroughly isolated those now and have very clean encoder signals so I really doubt it's that.

• I'm running LinuxCNC 2.7.4
• The OS is: Debian 7.10 (Wheezy) and the kernel is 3.2.0-4-rt-686-pae
• The encoder is a US Digital HI-1024-IE-D with a differential sort of backpack that connects to the single ended encoder and drives differential signals to my mesa 7i76 breakout board.
• The 7i76 is connected to a mesa 7i92
• I keep doing test runs on a thread and every pass is slightly different. It's as if it's not getting correct the index pulse and I suspected that to be the case which is why I put so much effort into getting rid of any noise. However this does not appear to be the case.
• When I turn the spindle manually 10 turns I expect to see 4096*10 or 40960 counts in motion.spindle_revs, but it seems to undercount by about 5-10 counts per revolution. I've swapped in a different encoder and I have basically the same issue. What is strange is that if I rotate the spindle back and forth +- 45 degrees or so a few times and go back to the original position I'll have accumulated a couple hundred encoder counts. What I think I've discovered is that the system undercounts in the forward spindle direction, but seems to count properly in reverse.

Attached is my .hal file.

Any ideas?

Good day Forum
Just a quick question for the forum, I have a Biesse 37L router that I would like to use it as multi config machine ( plasma cutter , CNC router and 3D printer ) . I would like know if someone can point me on how to make multi config on Linuxcnc so I can make things happen 
Thank you 
 

Yes - unchecking autovolts then uses the material voltage. Duh

thanks again
sam

Hi Aciera,

Its been a long time.
I saw your work and it was great.
but I have a XYZAC-TRT machine and for some work I need to run my machine as 3+2 with TWP.
I saw this video as it was TRT machine:

So I want to know how I can use my machine as such.

Thank You in advance,

Regards,
Abhishek
 

Thanks.

Is it also possible to put the voltage-divider (2 resistors) outside the plasma-source in a separate box to avoid warranty loss of the new machine ?

And where can I get a plug to connect to the THC and Start-socket of the Stahlwerk machine to connect it to my cnc-system ? Is it included when buying the stahlwerk 70P ?

clayton2ndtry wrote:

Has anyone used this to make a GUI similar to mini (deprecated several years back) or something similarly simple.
 

It's quite simple to make the GUI you need using Flex GUI. I did look at Mini and it is a bit confusing to me...

JT

As Timo and Jon pointed out, This Old Tony's MAHO 400P was like your Knuth. The machine had an early automation with a single central axis drive motor, and a set of clutches, brakes and angle gearboxes to transmit the drive to the selected axis. Only a single axis could move at a time. No integrated motion possible. No angles, no curves, no contouring, no thread milling etc is possible.

Tony stripped out all those mechanical parts and converted the machine to three modern drives each dedicated to an axis, and independant, allowing full 3D contouring.

My Maho 400E was already a "normal modern" CNC, so I didn't touch the mechanics or electrics of the drive system. Only replaced the controller, both because it was DOA, and because it had the lowest spec processor Phillips ofered (Intel 8086) and was therefore only 2.5D capable. With LinuxCNC it is now 3D capable.

Hello, can you tell me if there is a way to connect remote control signals to the jog buttons of the qtplasmac interface?
halui.joint.N.plus is missing, and joint.0.jog-counts is difficult.
Would like to have external qtplasmac pins for joging