Advanced Search

Search by Keyword Keywords:

Search Options

Find Posts from

Sort Results by

Search at a specific date

Jump to Result Number

Search in Categories Also search in sub-categories

Search Results (Searched for: 7i76e)

bnet

17 Mar 2025 15:12

Replied by bnet on topic Fanuc Serial Pulse Coders - Red cap servos, mesa 7i76e, how to?

Fanuc Serial Pulse Coders - Red cap servos, mesa 7i76e, how to?

Category: Driver Boards

That's what I'm starting to realize! Thanks for adding to my confidence on this route.

I have found some good encoders - I'm thinking of going with 10000 PPR for X and Z and 800 PPR for the turret and the live tooling motor as the latter won't need much in terms of resolution, while the Z and especially X will need as much as I can get/afford (maximum count rates of A-B Ultra3000 2.5 mHz).

M4MazakUser
M4MazakUser

16 Mar 2025 11:26

Replied by M4MazakUser on topic Fanuc Serial Pulse Coders - Red cap servos, mesa 7i76e, how to?

Fanuc Serial Pulse Coders - Red cap servos, mesa 7i76e, how to?

Category: Driver Boards

I had red encoders on the two servos I was using but changed them for 1024 a b z encoders. They weren't compatible with the mesa card I bought- i thought they would be. Was a lot simpler with standard encoders even with the startup positioning.

11 Mar 2025 12:14

Replied by JT on topic Finally 7i76EU!

Finally 7i76EU!

Category: User Exchange

I have them in stock as well.
mesaus.com/product/7i76eu/

JT

tsaG
tsaG

09 Mar 2025 23:51

Replied by tsaG on topic Can't succesfully release Tool (according to Probe Basic GUI)

Can't succesfully release Tool (according to Probe Basic GUI)

Category: QtPyVCP

yes, that is the "spindle-released" sensor. As mentioned above I have to convert it to a binary value as the 14V is below the (60% of 24V) digital threshold of my 7i76e.

I can see the "spindle-released" going high when the drawbar is pulled (so, no error when releasing the tool) but get the error when clamping the tool.

tsaG
tsaG

09 Mar 2025 23:40 - 09 Mar 2025 23:49

Can't succesfully release Tool (according to Probe Basic GUI) was created by tsaG

Can't succesfully release Tool (according to Probe Basic GUI)

Category: QtPyVCP

Hi,

I am currently integrating my ATC. However, I get the Error "Failed to release Tool" message when I clamp the tool.

My HAL looks like the following. I get a 0-14V Signal which is converted into a HIGH LOW for the Motion controller.

#ATC Settings

net analog1 hm2_7i76e.0.7i76.0.0.analogin1

setp comp.0.in1 10.0
net analog1 comp.0.in0

net ventil-spindel hm2_7i76e.0.7i76.0.0.output-12 <= motion.digital-out-02

net spindel-released comp.0.out <= motion.digital-in-02

In the HAL Show, I can see that spindle-released goes high when I press the "Release tool" button in the GUI. I also do not get an error message. However, when I insert the tool and click "clamp tool" I get the message "Failed to release tool" although everything works fine (and the spindle-released goes back to low). 

I found that I need to connect the motion.digital-in-02 [url=https://github.com/dpslwk/probe_basic/tree/subroutine_unify_and_move_to_nc_files/linuxcnc/nc_files/probe_basic/atc_carousel]here on the PB Github (manual is hard to find). 
I was unable to find more information on the PB Website. The current PB Github also doesn't have this Readme file/instructions.

Does anyone know what needs to be done here?

Thanks![/url]

bnet

08 Mar 2025 23:30

Replied by bnet on topic Fanuc Serial Pulse Coders - Red cap servos, mesa 7i76e, how to?

Fanuc Serial Pulse Coders - Red cap servos, mesa 7i76e, how to?

Category: Driver Boards

This very quickly is going to turn into a how to destroy some Fanuc encoders thread so stay tuned for that

I've decided to replace the encoders... this is probably not the answer that future readers are going to want to read, but its the least expensive and most straight-forward approach I can come up with. Either I have a digital problem or a mechanical problem to solve, and the latter is much more manageable with my skill set.

I'm trying to get better at knowing when to take a different path to the finish line. I once spent months trying to design a DC motor driver (90v 200amps) that ran on 600v 3phase for a Hardinge CHNC lathe based on open source electric vehicle schematics. Long story short, I didn't succeed and blew up a lot of expensive components along the way

Once I finally decided to swap the motor for an AC one and add a VFD, the whole thing was turning in in 2 days!

More to come!

djdelorie
djdelorie

08 Mar 2025 00:49

Replied by djdelorie on topic Power failure/flicker best practices?

Power failure/flicker best practices?

Category: General LinuxCNC Questions

The 7i76E is in (or eventually will be) the same enclosure (and same power cord) as everything else, except the PC, which is elsewhere. Putting just it (24V) on a UPS would be a technical challenge.
As for the motors, to keep the encoders powered that means another power supply (16V) in that enclosure that needs a UPS, and I'd have to get around to testing the following-error code ;-)

The motor's big power supply has pretty beefy capacitors - so much so that I have a discharge circuit on it's contactor for when I power it down.
My machine homes pretty accurately, at least enough for my purposes (woodworking) so a following error is not much better than a reset.
The spindle vfd is already monitored for faults (modbus).

Now I get to research tiny din-rail UPSs for 24V and 16V... ;-)

andypugh

08 Mar 2025 00:30

Replied by andypugh on topic Power failure/flicker best practices?

Power failure/flicker best practices?

Category: General LinuxCNC Questions

Maybe you could power the 7i76E from the UPS too? The spindle VFD can probably handle a sub-second power interruption on the bus capacitors.
The servos may stall, but there is some chance that they might recover position if the encoders remain powered. And if not, then you will get an f-error report, and still have a live system to recover with.

djdelorie
djdelorie

07 Mar 2025 22:39

Power failure/flicker best practices? was created by djdelorie

Power failure/flicker best practices?

Category: General LinuxCNC Questions

Other than sourcing a 240v/50a UPS, what should I be doing if I'm using my CNC in an environment prone to power flickers? We had a short outage this morning due to high winds, and often have sub-second "flickers", and I'm worried about running long jobs.
Note: my system was built with forum advice, where a 24v power supply feeds contactors for the motor and spindle power, with estops on the positive side and software-controlled relays on the negative side. I don't know how long each of the supplies will last without power, but I assume that no matter what the specific value is, eventually there will be outages both shorter than and longer than that ;-)

I do have a UPS on the PC running linuxcnc, but not on the power that runs the Mesa 7i76E board. I figure worst case, the PC will stop and tell me the line number it was on before all hell broke loose ;-)

So is there anything I can do or change to make dealing with such power flickers/outages less stressful?

(more info: the motors are servos but the drivers are step/dir, and the spindle has its own vfd. The setup has a single power cord with internal breakers for each power supply)

JTknives

07 Mar 2025 21:10

updating to QtPlasmac, copying setting from plasmaC? was created by JTknives

updating to QtPlasmac, copying setting from plasmaC?

Category: Plasmac

I'm starting over with a fresh install of the new QtPlasmaC on a new HD. I'm wondering if there is a way to just copy over my config data as its been so long that all these questions in the pncconf are greek now. Here is my old file

# Generated by PNCconf at Sun Jan 10 18:01:51 2021
# Using LinuxCNC version:  2.8
# If you make changes to this file, they will be
# overwritten when you run PNCconf again

[EMC]
MACHINE = IMPERIAL_PLASMAC
DEBUG = 0
VERSION = 1.1

[DISPLAY]
DISPLAY = gmoccapy
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
MAX_FEED_OVERRIDE = 2.000000
MAX_SPINDLE_OVERRIDE = 1.000000
MIN_SPINDLE_OVERRIDE = 0.500000
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = /home/jtknives/linuxcnc/nc_files
INCREMENTS = .1in .05in .01in .005in .001in .0005in .0001in
POSITION_FEEDBACK = ACTUAL
DEFAULT_LINEAR_VELOCITY = 0.250000
MAX_LINEAR_VELOCITY = 1.000000
MIN_LINEAR_VELOCITY = 0.016670
DEFAULT_ANGULAR_VELOCITY = 12.000000
MAX_ANGULAR_VELOCITY = 180.000000
MIN_ANGULAR_VELOCITY = 1.666667
EDITOR = gedit
GEOMETRY = xyz

[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python

[TASK]
TASK = milltask
CYCLE_TIME = 0.010

[RS274NGC]
PARAMETER_FILE = linuxcnc.var

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
SERVO_PERIOD = 1000000

[HMOT]
# **** This is for info only ****
CARD0=hm2_7i76e.0

[HAL]
HALUI = halui
HALFILE = machine.hal
HALFILE = plasmac.hal
POSTGUI_HALFILE = postgui_call_list.hal
SHUTDOWN = shutdown.hal

[HALUI]

[KINS]
JOINTS = 3
KINEMATICS = trivkins coordinates=XYZ

[TRAJ]
COORDINATES =  XYZ
LINEAR_UNITS = inch
ANGULAR_UNITS = degree
DEFAULT_LINEAR_VELOCITY = 0.83
MAX_LINEAR_VELOCITY = 8.3300

[EMCIO]
EMCIO = io
CYCLE_TIME = 0.100
TOOL_TABLE = tool.tbl

#******************************************
[AXIS_X]
MAX_VELOCITY = 8.3333333
MAX_ACCELERATION = 150.0
MIN_LIMIT = -60.0
MAX_LIMIT = .001

[JOINT_0]
TYPE = LINEAR
HOME = 0.0c
FERROR = 0.5
MIN_FERROR = 0.05
MAX_VELOCITY = 8.33333333
MAX_ACCELERATION = 150.0
# The values below should be 25% larger than MAX_VELOCITY and MAX_ACCELERATION
# If using BACKLASH compensation STEPGEN_MAXACCEL should be 100% larger.
STEPGEN_MAXVEL = 10.42
STEPGEN_MAXACCEL = 187.50
P = 1000.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
MAX_OUTPUT = 0.0
# these are in nanoseconds
DIRSETUP   = 10000
DIRHOLD    = 10000
STEPLEN    = 5000
STEPSPACE  = 5000
STEP_SCALE = 1940.17
MIN_LIMIT = -60.0
MAX_LIMIT = .001
HOME_OFFSET = 0.0
#******************************************

#******************************************
[AXIS_Y]
MAX_VELOCITY = 8.33333333
MAX_ACCELERATION = 150.0
MIN_LIMIT = -26.0
MAX_LIMIT = .001

[JOINT_1]
TYPE = LINEAR
HOME = 0.0
FERROR = 0.5
MIN_FERROR = 0.05
MAX_VELOCITY = 8.33333333
MAX_ACCELERATION = 150.0
# The values below should be 25% larger than MAX_VELOCITY and MAX_ACCELERATION
# If using BACKLASH compensation STEPGEN_MAXACCEL should be 100% larger.
STEPGEN_MAXVEL = 10.42
STEPGEN_MAXACCEL = 187.50
P = 1000.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
MAX_OUTPUT = 0.0
# these are in nanoseconds
DIRSETUP   = 10000
DIRHOLD    = 10000
STEPLEN    = 5000
STEPSPACE  = 5000
STEP_SCALE = 1940.17
MIN_LIMIT = -0.26.0
MAX_LIMIT = .001
HOME_OFFSET = 0.0
#******************************************

#******************************************
[AXIS_Z]
MAX_VELOCITY = 16.666
MAX_ACCELERATION = 300.0
MIN_LIMIT = -.001
MAX_LIMIT = 4.0

[JOINT_2]
TYPE = LINEAR
HOME = 0.0
FERROR = 0.5
MIN_FERROR = 0.05
MAX_VELOCITY = 8.3333333
MAX_ACCELERATION = 150.0
# The values below should be 25% larger than MAX_VELOCITY and MAX_ACCELERATION
# If using BACKLASH compensation STEPGEN_MAXACCEL should be 100% larger.
STEPGEN_MAXVEL = 10.42
STEPGEN_MAXACCEL = 187.50
P = 1000.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
MAX_OUTPUT = 0.0
# these are in nanoseconds
DIRSETUP   = 10000
DIRHOLD    = 10000
STEPLEN    = 5000
STEPSPACE  = 5000
STEP_SCALE = 6400.0
MIN_LIMIT = -.001
MAX_LIMIT = 4.0
HOME_OFFSET = 0.0
#******************************************

[SPINDLE_9]
P = 0
I = 0
D = 0
FF0 = 1
FF1 = 0
FF2 = 0
BIAS = 0
DEADBAND = 0
MAX_OUTPUT = 2000