Advanced Search

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!

Ohh thats very good to know! Probably stick around with the "dumb" devices then. But any other experience is welcome!

  Hi Everyone, first post here on the forum.I'm very new to Linuxcnc, and am building a 4 axis machine. I have Linuxcnc 2.9.3 installed and literally just a few days ago started playing around with jogging in increments within Qtdragon_hd. (love the interface)Sadly the only increments that actually work are 0.1mm or smaller. Everything else produces random results.After some reading it was suggested that I update the qtdragon_hd handler.py which seemed logical, and after downloading from the github a new .py file (95.5kb) I eventually figured out how to replace the original.Unfortunately now I cant launch the program and just get an error - hopefully attached is the report. If I revert to the original handler.py the program launches but I still have the unreliable increments.Have I missed a link somehow with respect to the new handler looking for a reference to my HAL and ini files?Would love to get some input for a solution.Many thanks

I dont have the 556 but i have the 542j which seems similar to one of those. In the sense that it has the serial port and 5v/24v switch. I noticed that this drive has some kind of internal processing that causes a following error. At any speed the motor lags the pulses and more so as speed increases. At 2500rpm the motor lags 1/4 turn behind the pulses, which makes it a poor candidate for use with encoders, and probably causes poor interpolation. I tried tweaking the settings with the leadahine software but no luck... ended up switching out with geckodrives and now have zero following error.

I was having this conversation with an engineer friend and he also noticed that some leadshine drives have a mind of their own.

Hi everybody,
since I am planning to update a Wabeco CC-F1210 with something quite up to date hardware I saw the DM556 and thought those would fit quite good. But there are so many "versions" of that thing.
Probably the most differences are in the following 2 models:
www.omc-stepperonline.com/digital-steppe...stepper-motor-dm556t
and the leadshine version:
www.omc-stepperonline.com/leadshine-digi...-stepper-motor-dm556
Is the new functionaliy of the leadshine worth the buck? Does anyone has real experience with both?
regards Han

Thank you all!

Hello, I'm a beginner in Probe Basic UI and want to add some machine specific buttons in the USER section of the UI screen.
I understand that the layout is designed by using Qt Designer but have no glue whow to link/connect the button with the hal pin or signal of the machine.
Any advise ot link to a helpful YT video is apreciated. I could not find a YT tutorial or step-by-step guide/documentation.

I've been distracted by configuring a CAM post for this machine, and kind of blown away, that after months of learning, I can decide on a strategy, select tools speeds feed etc, and output the NC code from the CAM system and linuxcnc, parses it without comment. Not only that the machine runs the code and the the part is to drawing. Just excellent.

The orient.svg chart, while I get some of what it is telling me, i cannot understand how I need to convert it into hal statements. I thought by now I would get this stuff but I don't. which ones are loadrt, addf, setp and net ?

Sorry to be a dunce.

Could I ask for some pointers please?