ok now hal_bridge has ok/cancel buttons that will close the notify error messages (if showing) or if a dialog is showing, enter ok / cancel or close.

Also the shutdown dialog can be set to have a countdown timer to automatically close the screen without clicking it.

Docs have been updated.

let me know how the ok/cancel pins work for you.

I’m working on a retrofit and I’m having trouble with oscillation on an analog velocity-controlled axis using existing Fanuc DC motors and drives.I have a Mesa 7i77EU for the FPGA, 7i85 for the encoders, and 7i83 for the analog outputs. I am using two outputs for each drive. one for a velocity command and one for a virtual tachometer. This is similar to how the original Fanuc controller was doing it.Current status:

• I have the analog outputs scaled correctly as far as I can tell. I measured the voltages going to the drive and they match the drive specs. 7V/2000RPM for velocity and 3V/1000RPM for the tachometer signal.
• With the velocity command wires disconnected from the drive, the system appears stable. The motor holds position well and resists manual twisting of the shaft.
• As soon as I connect the analog command wires to the drive, the axis begins oscillating even when all PID values are set to 0.(I was expecting this to act the same as when the wires were disconnected. The motor oscillates and drifts until i get a following error.
• Increasing the PID P gain to about 0.5 prevents the following error, but the oscillation is still present. 
  
  Does anyone have any suggestions on why the drive would be stable without the velocity command wires hooked up but unstable with them connected even with no movements?Any suggestions on where to start troubleshooting would be appreciated.
  

  File Attachment:

  File Name: AnalogConfig.hal
  File Size:9.3 KB

  File Attachment:

  File Name: AnalogConfig.ini
  File Size:3.47 KB

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