Advanced Search

If the drives are analog +-10V, then in this order
Mesa 7i97
Mesa 7i92TM + 7i77
Mesa 7i92TM + 7i85 + 7i83 + 7i84
Mesa 7i96S + 7i85 + 7i83 + 7i84

my1987toyota wrote:

Ok Amazon you really failed me . I searched on there site with BTS7960 as the search query and
literally got NOTHING.

Yeah, this is getting really frustrating with google and youtube and duckduckgo, spend half hour looking for something you found a few days earlier with the same exact name, nothing, zero, zilch,! All those have become like PMS with mood swings!

I think it's time for you to do some (more) research.

First... there's an excellent vid on YT from Erik Salo (sp?) about configuring a tool changer.  His explanation and demonstration of the digital in/out hal pins is excellent.  Even if your configuration will be different (not using carousel.comp), it's still a very good introduction of all the things which have to be choreographed.

Second, there are many, many examples of tool-changer configuration files - including gcode subroutines - on the forum.  Yes, the forum editor is horrible, and the search tool is a bit lacking, but I'd suggest digging through posts as much as you can stand.  Once you've found a handful of configurations & subroutine examples to digest, go through them and make yourself notes in narrative form exactly what the author was trying to achieve.  Pay particular attention to what signals were passed between what 'things', and how that was accomplished.

That should give you an idea of the steps & sequence you need to really get started your own config.

As another resource, the Probe Basic GUI includes an ATC simulator - which also has various subroutines and so forth to review and digest.  No need to install the GUI if you don't want - just download the relevant files from github.  The PB tool changer scheme does not use carousel.comp, nor does it treat the platter as an axis.  All of the 'go-to-this-pocket' logic is contained within the subroutines, and the whole thing is designed to work with geneva-wheel mechanisms and 'dumb' motors.

Wen und ob es kein karte das sie brauchen gibt, sie konnen immer die Mesa 7i96S kaufen, dan abhangig an die machine noch die 7i85 oder 7i85S, mehr IO mit 7i84 and fuhr analog servo noch die 7i83.
Mit ale diese da kan jede machine zum laufen gemacht.
Wie ist mein Deutch? Bitte die korrekte worte schrieben, ich will Deutch gut lernen.
Danke schon.

Thank you for reporting back.

It is said in there that it takes 40 us to send that message and if I understand correctly it sends 15 pulses. so something around 3 us per pulse which is 300-400 kHz range?

Hi Arciera,

I don't see another way than to limit the speed to the highest curvature

When only dealing with lines and arc's this should be fine.
Once we have spline's and clothoid's the curvature varies along the path.

Say for each segment we create a scurve velocity profile using 5 waypoints.
Then using a B-spline to represent the upper bound of an S-curve profile can be a practical approach.

Then running realtime we are able to follow the upper bound (spline) with the scurve algo along the path.

Then when we for example should apply a spline roughing algo like seen in the science papers,
this then results in perfect velocity changes along the path. A sort of dynamic feed flow. I dont know how to call it.

This upper bound (spline) then also smoothes the transition's between lines and arc's with clothoid fillet in between.
In fact we could create one upper bound (spline) along the entire gcode path. I could test this with a large file.
 
// Notes:

// curvature = k;
// k = 1 / radius ( this is for arc, or circle, for spline or clothoid use library functions ).

// linear_acc = r * angular_acc
// angular_acc = linear_acc / r

// velocity = sqrt( angular_acc / k )

Then there might be a problem when one segment is very long and has high curvature value at one spot.
This then will reduce the overall segment speed. How to deal with this?

I don't see another way than to limit the speed to the highest curvature value but since this will only apply to fillets I don't think the segments are going to be very long in the first place. Not really sure about this but creating a path deviation of a couple of mm is likely already the limit of what you would want even in a roughing cycle.

In what situations would you use "Pause For Jogging" in the manual tool change message dialog?
Select this to rotate the spindle.
I'm not familiar with CNC operations, so I had some doubts.

(When using qtdragon for manual tool change.)

 

Hi Arciera,

Hmm, I will take a look when time comes.

Currently working on the look ahead function to calculate optimal trajectory speeds.

The trajectory consists of lines, arc's, helix, clothoids, & splines.
The max speeds depends on the min,max curvature value of the shape.

- For a clothoid we retrieved the clothoid curvature extrema. "kmin, kmax also know as a kappa value." from the library g2solve3arc.curvature_min_max(..)
- For a arc we can calculate the constant curvature "1/radius" as for a line the curvature=0.
- For the 3-degree spline we calculated curvature min,max using the opencascade GeomLProp_CLProps class.

Then using a optimal angular speed, we can calculate the max speeds for the shapes.

We use a forward sweep over the trajectory followed by a backward sweep over the trajectory between
the rapids. Then the vo, ve is calculated given by a max vm of that segment.

Then there might be a problem when one segment is very long and has high curvature value at one spot.
This then will reduce the overall segment speed. How to deal with this?

 

Issue has been solved by following this post: forum.linuxcnc.org/27-driver-boards/3559...ethernet-mesa-boards

danke sehr nett von dir dort habe ich vor 6 monaten angefragt mir wurde nur gesagt es gibt nur mehr die 7i76Eu und sie wissen nicht bis wann

vor 3 monaten dass selbe.
und mein händler der dir 7i76 e verkauft hat ist gerade in urlaub er weis auch nicht wann die neuen kommen da MESA nichts raus gibt aus den USA

Resets the Z value of the active coordinate system.
Before getting #<zworkoffset>, you must reset the Z value of the active coordinate system.

The drives use an analog signal from the control. I was also able to find datasheets and the software to tune these drives online.

Ok Amazon you really failed me . I searched on there site with BTS7960 as the search query and
literally got NOTHING.
Thank you tommylight. I used your URL and Amazon went straight to it. On a side note that other
SSR I ordered works great with PWMing and has a heat sink and fan port . So now the machine
is back in bussiness. Now I can get back to getting the 7i96 to do PWM on a general output.