Advanced Search

HI PCW,
thank you for your Answer!
But for a better understanding. How is the communication between LinuxCNC and the Card done? With the LPT "communication" the LinuxCNC software gets a command to go 3mm in X direction, so "itself" sends the pulses on the LPT in the (hopefully) correct speed.
Does LinuxCNC still sends "pulses" when it has a mesa card and the card only corrects the jitters? Or is there some kind of communication so that LinuxCNC just sends go 3mm in that speed and the card does the pulses? LinuxCNC then know how long it takes for that movement and after this time it send the next command.
With the second approach it would probably be really hard to do something like probing.
Thanks !

I checked 2.9.7 and 2.9.3. I see no jogging with screen buttons issue.
I'm assuming you mean the screen buttons.
It could be a key repeat issue.

I would suggest updating your whole system to 2.9.7 before I'd suggest updating the handlerfile, but we should see if it's a system problem first.

2.9.4, Probe Basic

Probing failure either a g38.2 or g38.3 locks out the jog, 
Estop cycle , machine power cycle , probe on or off, homing, locks out jogging in all directions. Any way to reset this without restarting Linuxcnc?

Ok, Sounds Good.
I'll update and give it a try.
Thanks!

I finally got this to the finish line.  Thank you for what you provided, but from a qtplasmac standpoint all development on 2.9 has ceased.  I have pushed this update, and book ended it with some bug fixes, but to the master branch only (2.10).

github.com/LinuxCNC/linuxcnc/commit/4e26...712bc80a993377610a37

Your way seems like it would work though. 

All that said, I would encourage you to move to 2.10 and test these features if your production risks allow it.  There have been a fairy amount of bug fixes/feature updates since 2.9.

QtPlasmaC updates - Master (v2.10):

• change power button from ActionButton to QPushButton on 9x16 screen
• allow probe test to be aborted when plasmac.probe-test-error goes true
• reload material file before repopulating the GUI
• allow Probe Height and Safe Height to be zero to follow component and docs
• normalize distance decimal places for Parameters tab
• tweak gcode filter decimal places
• add Slat Height and Material Thickness probing option

LinuxCNC should report the error

If you need LinuxCNC to do a specific response to the error
you would need to set that up in the hal file

Hello,

I'm using a 7i96S with a 7i84U daughter board. Everything is working reasonably well except that when the smart serial fails Linuxcnc doesn't fault. I can manually restart the 7i84 by toggling the smart serial run pin but I was wondering if I missed something since linuxcnc continues to run with whatever the last values of the I/o pins on the 7i84.

Things like probe inputs are sampled at the servo thread rate ( typically 1 KHz )
by LinuxCNC's motion component. Typically probing ( and homing ) is done in
two steps with a higher velocity search motion followed by a lower velocity latch
motion. You would normally choose a latch velocity low enough that the 1 ms
(max) sampling uncertainty causes a minimal position error when probing.

Mesa hardware does have the capability of latching encoder or stepgen counts
at probe activation, but this is currently not supported by LinuxCNC.

Thank you so much, Mr. Hakan. I really appreciate your kind reply.

I'm using LinuxCNC 2.9.5 and 3axis machine, and I want to replace servomotors to YASKAwA servo systems.  ( I think I can upgrade LinuxCNC to the newest if needed) 

Now, I deleted SDO description, but I still get A12 Error. Xml configuration for lcec is very simple. (attached ethercat.xml)

So, EtherCAT basic communication is wrong. ( I have to solve it before SDO error. )
This is sudo dmesg output(dmsg_alarm_a12_2). 

I can see a lot of WARNINGS and Errors, but How can I fix these problems for YASKAWA Servo?
 

Hi,
some more questions from me:
Assuming using a 3D probe with one signal to use (NC or NO does not matter to me). How is this handled inside a Mesa Card? Is it just read and then put through to linuxCNC and then LinuxCNC is reacting on this saying "stop"? How does LinuxCNC knows where it is? Or is there some kind of interrupt going on and the fpa itself is stopping the movement and "sending" back some information to LinuxCNC how much steps it did to reach this position?
How fast is the Data Transfer through ethernet? And isn't it a problem for the probe process itself when the Card does all the stepping stuff? How does LinuxCNC knows how much steps have been done?
regards Han

So, it seems I've managed to get the contour pretty well right. It's coming along slowly. It took me quite a while to get it to this point.

Hello,iI am just starting to use SolidCAM.
Attached is a picture of a part that I would like to mill. The other picture shows the part after tool simulation. Material remains on the bevel. How can I remove the remaining material for example with a 3 mm ball end mill? SolidCAM has the standard milling cutters, and I added a 3 mm ball end mill manually.

Check the last say 10-20 lines of the output of "sudo dmesg".The ethercat master
always tells why (in a not so obvious way) why slaves won't go OP.

hello guys
i really need help with configuring R3EC IO coupler + R3 1600 DI + R3 0016-P DO ,to my etherCAT system,
i wrote XML file but when i check the status of the slaves all the drivers are in OP mode except the R3EC is in SAFEOP and it does not switch to OP mode,
here is the XML section for the R3EC i used : 
<slave idx="6" type="generic" vid="0x00004321" pid="0x61400025" configPdos="true">
<!-- SM2: Outputs -->
<syncManager idx="2" dir="out">
<pdo idx="0x7000">
<pdoEntry idx="0x7000" subIdx="0x01" bitLen="16" halType="complex">
<complexEntry bitLen="1" halPin="do-01" halType="bit"/>
<complexEntry bitLen="1" halPin="do-02" halType="bit"/>
<complexEntry bitLen="1" halPin="do-03" halType="bit"/>
<complexEntry bitLen="1" halPin="do-04" halType="bit"/>
<complexEntry bitLen="1" halPin="do-05" halType="bit"/>
<complexEntry bitLen="1" halPin="do-06" halType="bit"/>
<complexEntry bitLen="1" halPin="do-07" halType="bit"/>
<complexEntry bitLen="1" halPin="do-08" halType="bit"/>
<complexEntry bitLen="1" halPin="do-09" halType="bit"/>
<complexEntry bitLen="1" halPin="do-10" halType="bit"/>
<complexEntry bitLen="1" halPin="do-11" halType="bit"/>
<complexEntry bitLen="1" halPin="do-12" halType="bit"/>
<complexEntry bitLen="1" halPin="do-13" halType="bit"/>
<complexEntry bitLen="1" halPin="do-14" halType="bit"/>
<complexEntry bitLen="1" halPin="do-15" halType="bit"/>
<complexEntry bitLen="1" halPin="do-16" halType="bit"/>
</pdoEntry>
</pdo>
</syncManager>
<!-- SM3: Inputs -->
<syncManager idx="3" dir="in">
<pdo idx="0x6000">
<pdoEntry idx="0x6000" subIdx="0x01" bitLen="16" halType="complex">
<complexEntry bitLen="1" halPin="di-01" halType="bit"/>
<complexEntry bitLen="1" halPin="di-02" halType="bit"/>
<complexEntry bitLen="1" halPin="di-03" halType="bit"/>
<complexEntry bitLen="1" halPin="di-04" halType="bit"/>
<complexEntry bitLen="1" halPin="di-05" halType="bit"/>
<complexEntry bitLen="1" halPin="di-06" halType="bit"/>
<complexEntry bitLen="1" halPin="di-07" halType="bit"/>
<complexEntry bitLen="1" halPin="di-08" halType="bit"/>
<complexEntry bitLen="1" halPin="di-09" halType="bit"/>
<complexEntry bitLen="1" halPin="di-10" halType="bit"/>
<complexEntry bitLen="1" halPin="di-11" halType="bit"/>
<complexEntry bitLen="1" halPin="di-12" halType="bit"/>
<complexEntry bitLen="1" halPin="di-13" halType="bit"/>
<complexEntry bitLen="1" halPin="di-14" halType="bit"/>
<complexEntry bitLen="1" halPin="di-15" halType="bit"/>
<complexEntry bitLen="1" halPin="di-16" halType="bit"/>
</pdoEntry>
</pdo>
</syncManager>
</slave>

i appreciate your help guys i have been stuck with this problem since two weeks!