Advanced Search

Unless you have an added parallel daughtercard, it's unlikely you need
to change the installed firmware.

Since you are using pncconf that does not directly support the 7I95/7I95T
the list of pin names is useful since in has the names of the isolated inputs
like:

hm2_7i95.0.inmux.00.input-00

and isolated outputs like:

hm2_7i95.0.ssr.00.out-00

are there.

If you do not want to add these by hand to a pncconf created configuration
you could use mesact instead of pncconf, since mesact supports the 7I95/7i95T
directly

This is very helpful but I don't understand. It appears you are using two pins. I have my Emergency Stop switch attached to GPIO25. It is designated as INPUT. I get errors when I try to add the second line [net estop-ext => [HMOT](CARD0).7i84.1.1.output-08} with references to -output.  I don't see a need for output in an eStop unless it is to communicate with software. With what I understand, I did this:

I created an input on GPIO25 -
loadrt hal_gpio inputs=GPIO7,GPIO8,GPIO25,GPIO12,GPIO13
I created an input:
net estop-ext <= hal_gpio.GPIO25-in
Then I used one of your suggestions:
net estop-ext => iocontrol.0.emc-enable-in
And so now, when I press my eStop (which at present is non-latching) the program momentarily stops. If I release it, it restarts (bad).
I think I am missing the second part- not allowing the machine to come on after the button was pressed.

I don't know of anyone working on that, but loobric.com/blog/introducing-smooth-tool-data-sync might be of interest / related

Cooped-Up wrote:

the only way I was able to get any of the axis to move outside of homing is to use the halshow to select the axis for jogging. 

That sounds like you are jogging with axis-selected in halui. 

Try connecting the jogs to the motion pins:
linuxcnc.org/docs/stable/html/man/man9/m....9.html#JOINT%20PINS 
linuxcnc.org/docs/stable/html/man/man9/m...n.9.html#AXIS%20PINS
You will need to connect up the joint.N.jog.... pins to jog before homing and the axis.L.jog... pins to jog after homing. 
(An advantage of doing it this way is that you are jogging entirely in the realtime layer) 
 

Part of failing is what you learn along the way. I know of "a rule" that eStops should be Normally Closed. Yesterday, that is all I knew. Today however, I am well-versed in ISO 13850:2015 Safety of Machinery - Emergency stop functions - Principles for design. Today I have a strong opinion that you are right! The reality is my schematic I'm using from Byte2Bot does it otherwise, so shall I.
But we divert! I don't see any GPIO25's in this banter.

OK got the file but it tells me a whole lot of nothing i understand.

From what i understand so far is that there are bin files that are pre configured for the board.
Like in the second Picture attached.
In the first picture are what seems to me are such files which are provided by mesa.
Which basicly does nothing for me because i cant look into them or research which does what.

Trying my best to understand and get a hang of things.
 

Also are those things correct for your steppers, they look big to me.

Are you dropping packets? that is, what is:

hm2_7i76e.0.packet-error-total

A dropped packet will result in a (bogus) following error spike,
as stale stepgen position (from the previous cycle) will be compared
with the commanded position. At a 2 ms servo thread period and 125 mm/sec
velocity, a .25 mm reported following error value is possible from a dropped
packet. Note the this does not mean that there is an actual path deviation
of this magnitude, this is bounded by the max_error PID pin to ~.0127 mm
per dropped packet.

I still think the physical error is most likely mechanical as it only shows up on Y.

To diagnose stepgen errors, the best thing is to plot the following error
with halscope like this:

 


Note that this is in inches, but the velocity and acceleration are about 4x and 6X your machines values
and the inherent stepgen error is less than  0.25 micron.

Another possibility if the system latency is really bad, is loss of DPLL sync, so you might try increasing
the DPLL time from -250 to -500 usec

 

Hola! Tambien soy Argentino. He comprado directamente a Mesanet sin problemas en varias opurtunidades y te lo envian ellos mismos por correo. Tambien puedes probar en esta pagina:
eusurplus.com/index.php?route=common/home

Si no me equivoco son de Portugal y en ocaciones puedes encontrar lo que no consites en mesanet.

Saludos!!

Ok, no worries!

Happens to everyone.

are getting reported when from driver's or linuxcnc? What is the axis drive type? Bal screws or rack or belt? Edit: Nevermind saw c5 screws 

Your fixed bearing arrangement isn't ideal. Ac bearings should be matched sets requiring no intermediary spacers for preload.  Adjusting correct preload with spacers between the bearing set is incredibly variable and difficult.  It is for certain an easy way to destroy bearings as I've done it in the past and turned the balls to crumbled bits.  That said I don't think that's enough for your deviation, just a suggestion for future improvement. 

Feed forward is used with PID tuning for servos and a feed back loop, if your using simple steppers this shouldn't need an adjustment over the ff = 1

 

I made a spelling mistake when i entered it into the INI file. It's working now.
Thank you

Mesaflash shows physical pins, and which firmware modules are included
in the current installed firmware. What you need for hal file creation/editing
are hal pins and parameters.

To show all 7I95T hal pins and parameters:

1. Start LinuxCNC

2. In a terminal window type:

halcmd show all hm2

if you want a file containing these pins and parameters (for use as a copy/paste donor file):

halcmd show all hm2 > 7i95pins.txt

For documentation on the modules and their pins and parameters:

man hostmot2

This is a mod that allows using a single key ("c") to cycle through all jog modes and increments.

From continuous to every increment in order, back to continuous.

The beginning of the error log is cut off.

Perhaps posting the output of the "Create Report File" button is the best solution.

Posting your HAL and INI files is also probably a good idea.