Advanced Search

rodw wrote:

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.

Always sound advice.

In this case the bug was found under 2.7.8:

And the 2.8 docs were updated with the warning, but not 2.7.

Hi,

I installed and tested the new driver.
The installation went smoothly, and the driver is working.
I’ll be testing it thoroughly over the next few days.
I can’t comment on the jitter or synchronization issues, as I haven’t experienced any problems in that regard.
Nevertheless, I’d like to provide some feedback.

Great work

Actually I had done this in February:

 
 

I don't think so but I can make it when I get a chance.
 

Hello,

few days ago my laptop died so i have to get a new one to run LinuxCNC with my CNC
8 years ago i bought a 6040z cnc router which had a manual how to set everything up. So after this 8 years i remember nothing and i figure out everything with google. I have set up my station, connected all. My XYZ axis are working and running correctly. But i have a problem with a spindle. While i power the machine it starts to spin immediately. I cannot figure out how to set the spindle control. Tried some result posted on internet but they seem to not work with my station

CNC 6040z
JP-845 board inside
LinuxCNC 2.9.8

If someone can guide me to something or point where to check some information i would be very grateful.

Setup of pinout:
1 - Spindle ON
2 - X Step
3 - X Dir
4 - Y Step
5 - Y Dir
6 - Z Step
7 - Z Dir
8 - A Step
9 - A Dir
10 - ESTOP?
11,12,13 - should be end switched but i dont know which option to choose
14 - ?
15 - ?
16 - ?
17 - Spindle PWM


When i power on the powerunit, spindle does not start. When i open AXIS on LinuxCNC, spindle starts and then goes forever. Closing program changes nothing

I appreciate that, thanks.

adding line-charts:

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!