Advanced Search

I'm sorry.
It seems it was my misunderstanding.

I've had a problem for a few runs where my X axis has been stalling while traveling to the right, and today it completely stopped working entirely. I've traced the problem all the way back to the mesa board.

By plugging in the X axis control lines in Y or Z's control ports on the board, it functions as expected. That means its not the wiring, the drivers, not the stepper itself, but something on the Mesa itself.

I've not changed anything in the INI besides some homing offsets for quite some time and it functioned perfectly for a around 6 months prior. There has been some temperature increases, but the mesa is in cased with 2 120mm fans facing it.

Has anyone seen or had this problem before? Is there a solution you can suggest?

You would probable need a daughtercard because
the XY100 interface needs 4 differential outputs and
1 differential input (that is you could not directly connect
to P1). Something like a 7I78 could do.

Without buying anything, you could test the galvanometer
with a 7I95T config that steals 2 step/dir channels to get the
XY100's 4 differential outputs and use a sserial input for the
differential input.
 

Hello! New to LinuxCNC and Mesa and trying to set up a 6-axis (+2 galvo axes) laser system. All 6 of the step/dir and encoder pins of the 7i95T are anticipated to be used, and trying to figure out how other pins can be repurposed.

Is there a firmware version for the 7i95T with xy2-100 support (xy2mod)? The unit currently has the default 7i95t_d.bin firmware loaded.

Which pins on the 7i95T could be used for controlling a 2-axis galvanometer? Would the Serial 0 and Serial 1 pins be suitable?

The manual mentions that the P1 expansion port can be used to expand I/O including for more step/direction channels. Can these pins be redefined for such purposes directly or is an expansion card / daughterboard needed?

Can (which?) pins on the 7i95T be used to control an IPG laser (please see attached image of pinouts from laser specifications) or is another card needed? 

hello gentelmen,

I did some stuff... if you are familiar with TC3 and you have working configuration.. You cas use the consoleTool which translate complete .xml configuration from Beckhoff ethercat master to lcnc ethercat master by drag and drop your right working config .xml + initCmds should be imported too

regards

Yes.
Yes.
Yes.
...
But first you have to stop thinking DMG or Dosan have good controllers, most industrial controllers suck badly for some work while being very good for some other work.
Point being, C1, C2, C3 are very wrong names for rotary joints/axis, LinuxCNC use A, B, C and they are tied physically to X, Y, Z, in that order so very easy to remember and use.
As for the rest, the above Yes's are for everything else you asked, LinuxCNC can do 5 Axis (can do 9 axis XYZABCUVW and each of those can have more than one joint/motor/drive controlled separately), yes you can use a parallel port or two or three if you need more inputs/outputs, parallel ports can be set to IN/OUT/X mode, etc etc etc .... the list is very, very long.
And most importantly, YES, start building the machine, no matter what i or others say, just build it!

Edit:
Just read it again, C are spindles in axis mode so forget the part of me complaining about it.

No, homing to index is common and fully supported.

I'm just saying that the actual index hal pin is not useful
for homing. The index-enable pin is what's used to communicate
index information from the hardware/driver to LinuxCNC

That is, this hal statement:

net phaseZ [HMOT](CARD0).encoder.00.input-index

Doesn't do anything useful.

But this hal statement:

net b-index-enable joint.3.index-enable <=> [HMOT](CARD0).encoder.00.index-enable

Allows LinuxCNC to enable index detection AND allows the driver to inform LinuxCNC
when the index has been detected.

To test whether the index hardware is working (assuming you can move the axis past
an index mark), you would:

With LinuxCNC running,  use halshow to watch the signal b-index-enable
and then with either halshow or halcmd, set b-index-enable true"

halcmd sets b-index-enable true

halshow should now show b-index-enable true

now, if you move the axis past an index mark, b-index-enable should go false.

This is how you test for correct index operation.

Hi everybody.
I would like to build a CNC machine with 5 axis MillTurning.
Its basically like the DMG Mori CTX BETA 800 TC.
I work everyday as a cnc programmer with DMG(Siemens/Celo) and Doosan(Fanuc).
It would be a small form factor and only for light materials, like aluminiu or brass.
My ideea is :
X, Y, Z as linear axis.
C1, C2, C3 as rotary axis.
C1 is the rotary axis of the spindle head
C2 is rotary axis of main spindle (G54)
C3 is the subspindle (G55 for ex.)
BTW i know that in DMG the C1, C2, C3 are in angular mode, in turn mode is S1, S2, S3.
The Spindle head will be with a BT30. (i will machine all turn base tool holders for BT30)
The driver part i would like to use 400W to 750 W servomotors.
I would like to use Parallel port for this setup but i get the feeling i'm limiting the performance of the build.
For the moment i have some stepper motors (JSS57P2N) would like to experiment.
The build size will be maximum of 500mm between arbors (S2, S3), the Y axis max 150 mm travel, X axis 200 mm travel.
The problem i face right now is it posibil to make this cnc with linxcnc or i have to buy a different controller and software?
For now i have DELL Optiplex 745 with Intel Core2Duo CPU and 4GB Ram, AMD video card and i get about 12000ns
 latency test.
I'm trying different configurations but do not see something compatible for my purpose.
If someone build something similar from DMG style could you guide me.
Thanks
 

What value do you have for P in the ini file, if any?
And what value does the servo period have?
Or is this a parallel port setup?

I don't quite understand, but that means I could never use it as a homing device? my encoders are 2500 pulses/ 10000 pulses quadrature hole.

I have been trying to run a fairly simple profile on my lathe- a radius and then a straight z axis move. during the the final g71 pass and also the g70 pass, the x axis twitches after going some distance, gouging a bit into the profile, around 0.3 mm into it whereas it should go straight without the x axis moving. I am unable to troubleshoot this problem at all. 

i am posting a link to the video of the problem I am facing, you will be able to see the x axis unwantedly twitch a bit in the last 3-4 seconds if you look closely. any help is much appreciated.

youtube.com/shorts/7KZHbUTbIng

Very odd, the only thing I can think of is that
there's something wrong with the supplied
field voltage (not filtered?) or the field voltage
sensing on the card is faulty.

What is your field voltage and what does
the 7I76 field voltage hal pin read?

You would need to have the sserial mode set to 2 to
be able to read the field voltage hal pin, so in the
hal file, change:

sserial_port_0=00xxxxxx

to:

sserial_port_0=20xxxxxx
 

are you on the soft limit or the hard limit? if the hard limit, then set a home offset so you have a bit of cushion for drift on power cycling. if its a hard limit switch, in probe basic in the side bar tab for "WCS" there is a button for LIIMITS OVERRIDE. this should ignore the limit switch and allow you to jog away. but this isn't really going to fix the issue over all. you should set the home offset with enough distance away from the limit towards the useable axis travel side so it doesn't ever encounter this situation.

hello,

I see the TC3 on your screen .. I did TC3 master to lcnc master configurator but it is not tested with the SoE drives ... maybe it will help you

let me know if it helped

regards
 

kubes wrote:

Additionally, I have found incorrect and inaccurate details regarding the setup of absolute encoders and how LCNC handles them in both document and forum searches.

Yeah search is fuzzy on the forum and utterly useless on google lately.
And this is a rare topic, so not much to go on, but more and more users have similar setups with absolute encoders and homing to index and EtherCAT, mainly due to inrush of cheap china drives with haphazard user manuals leaving users to pretty much figure stuff by trial and error.
-
I did a retrofit with absolute encoders, used the "immediate homing" feature in LinuxCNC as it was simpler for them and more in line with their type of "one off" work.
-
Did you test adding a bit of HOME_OFFSET? Usually negative values, not always.