Advanced Search

Hello all, this is an update for my issue.

While trying to debug the THC activation happened that the voltage readings started to get erratic i.e. -39v until it completely failed. At some point identified that the encoder differential input chip was super-hot. I assume it got damaged by some EMI spike. had that chip replaced at a laptop shop, I only tried it again with a new NON HF plasma source, the new plasma is not CNC, only some relay interface used for starting and. THC is working now. so bottom line, in my case the HF plasma was causing too much trouble. Thanks all for your ideas and hope this if useful for someone in the future.

Antonio.

2.7 is a very old version now given 2.8 was released about 10 years ago when I first started with linuxcnc. If its not mechanical and not your gcode if linuxcnc is the cause, it may have been fixed in subsequent releases.

Also be very careful when reading the docs that you are reading the ones for your version. I got caught with this a lot when I started. The docs spumco shared are for version 2.9. The warning he found is not in the 2.7 docs. Not saying it does not apply, but it could be different today.

Jake wrote:

I have a working touchscreen now. Much better when you buy one that is actually a touchscreen.

I did discover something new with the new ELO driver. Default is beep on press, which becomes highly annoying.

# cd /etc/opt/elo-usb
# ./cpl

This will open the settings and you can disable it from there. FYI
 

Care to update on how you installed the driver?

I am stuck on step one of the instructions, which tell me to: "Copy the elo driver files from the binary folder to the default elo folder."

What is the "default elo folder"??? All I've done so far is download a *.tgz, and extract it. I don't have an elo folder yet! I am certainly not afraid of the Terminal, but these instructions are just not written for normies.

Sorry to double this, but I couldn't figure out how to quote your post after I forgot to before.

Do you have any firmware for the 5i25 with 7i76 by pktUart?

Estoy en Colombia y tengo disponible una 7i73, si le interesa.

If the parallel BOB on P2 is just used for GPIO, yes, the  5i25t_7i77x2d.bin
firmware will work.

You do need to make sure that the special functions on P2 are disabled
in the hal file (with num_encoders=6 and sserial_port_0=000XXXXX
in the driver command line) Doing this will make these pin functions
revert to GPIO.

If you need step/dir, PWM, etc on P2, that would require firmware for a 7I77
on P3 and your BOB on P2
 

First thing I'd do is run a test program with just the arc moves, and add an M1 between each line.  Maybe slow the feedrate down, too.

Point of this is to see if the DRO matches your expectations at the end of each arc segment.

If the DRO matches what you expect, then possibly you have a mechanical issue - coupling, ballscrew/nut bearings, some sort of lost motion.  Possibly a tuning issue during decel for one of the drives.  Might explain why it's only on two opposite arc segments.

If the DRO does not match what you expect, then you can (probably) rule out a mechanical cause - LCNC is deviating from the path - and it's time to look for config or g-code issues.

I'd also suggest reviewing the LCNC manual on G2/G3.  I know you said you don't need help with the g-code, but the manual is pretty clear that center-point arcs are more accurate than radius arcs and that rounding errors may lead to problems.

NOTE: I just spotted a warning in the manual about G2/G3:

linuxcnc.org/docs/stable/html/gcode/g-code.html#gcode:g2-g3

Your Z-pitch is pretty small, and you may be experiencing some aspect of the bug reported above. Possibly fiddling with the P64 Q-value (see bug report) might help.

Hola Roma, como estas?
Disculpa hice la compra por fin hace poco ya que no estaban en stock los equipos que queria comprar, estan viniendo por USPS y me dice que estan en argentina actualmente
Vos cuando llegaron tuviste que completar algo, te enviaron un mail, las tuviste que ir a buscar como fue?
Podrias compartir tu experiencia al respecto.
Desde ya muchas gracias!

Cool

ok with the mach3 Bob P2 and it being a digital step and the 7i77 controlling analog servos will the 5i25t_7i77x2d.bin work that would also set both ports up for analog?

github.com/multigcs/halviewer

some updates, the gui is interactive now, you can zoom and move all node for a better view.
The original diagram is generated automatically from the INI/HAL file, and the layout is created using Graphviz.

  With some things a boycott is still possible.. The big problem I have seen is more times then not
they are either all doing the same B.S. and or buying up the logical alternatives so
you have no real choice. Plus they are usually heavily subsidized enough that they get a
bailout instead of collapsing. And to add insult to injury most people are stretched so thin
financially and or mentally that they just can't.

   I know with me I had to stop watching certain YouTube channels because I was taking too 
much of a mental hit from the never ending tsunami of doom and gloom that is honestly just
getting worse. 

Lets face it most people soon will either become a slave or a criminal with how much the
worlds judicial systems are being perverted. Legal doesn't always mean ethical, and
ethical isn't always legal.


 

As someone else said that gouge at the end is from the retract (when the endmill was coming up). Usually you'd want to add a line to move the endmill off the part before coming up. Not being the right size isn't a big issue as long as there is no taper. Can you measure the hex across the flats at the top and at the bottom of the part? How far out is it? Could it be the endmill is not the size you thought it was or that in whatever software you used you left material for a finishing pass?

Hello all, I picked up a machine from someone else with axis 2.7.15 and am trying to make a countersink by ramping down in a spiral. For clarity, I am using an end mill and going in a CCW helical spiral. Sample code is as follows:

G03 R0.168 X0.168 Y0.000 Z0.0043
G03 R0.168 X0.000 Y0.168 Z0.0035
G03 R0.168 X-0.168 Y0.000 Z0.0028
G03 R0.168 X0.000 Y-0.168 Z0.0020...

The issue is as follows. The first arc will look correct, the second arc will drive more left before driver down so the arc will be incorrect (it's almost as if the Y is lagging), the third arc will be correct, the fourth arc will drive in the x first and the y seems to drive late like it's lagging. I've used halscope to look at some outputs and these are them: ibb.co/b5WTfCH3

The secondary issue is that the machine stops or slows between arcs and I don't want that to happen.

For the life of me I can't figure out why it's happening. 
Previously I changed the .ini file to increase the lookahead and the arc blending because the segments were stopping between every arc and I wanted a more continuous motion. I get the R is slightly off if the Z is included BUT then I would expect all four arcs to have the issue not just two of them.

(I don't need any help with the gcode as that is not the problem I am having - also I am well aware that *technically* ramping down each line will produce a slight inaccuracy in the machined dim - but that is within the req tolerance of the feature I am machining) 

Thanks for your help