Advanced Search

Die neueste Version ist 238.314 und enthält zahlreiche Fehlerbehebungen.  

Ihre Sicherungsdatei zeigt an, dass Sie Version 236.301 verwenden. Wir haben ein Update mit Version 237.308 herausgebracht, das dieses Problem meines Erachtens behoben hat. Es wird durch die Verwendung von Kommas anstelle von Dezimalstellen in einigen Gebietsschemata verursacht. Sie müssen aktualisieren, dann funktioniert das deutsche Gebietsschema auch für Sie.

Wow the number of supported boards is getting really extensive.

Thanks to 'festlv' fixing the ecp5 pin generator,
the Colorlite i5 works with riocore:

 

endian wrote:

I do not know where are you from Tommy...

In Kosovo, Eastern Europe (well middle Europe is more correct, but there is no such thing, yet! )
Just for kicks, ask your post office how much would it cost to send such a thing here, but be warned: having a glass of water on hand is highly advisable, and so are sedatives!
If you ever wondered what a black hole is, now you know, i live in it!
On the brighter side, since this year we are able to travel again visa free in EU, after over 25 years!

HI,
with the update to version 2.9.2 the problem is solved.

Thank you for your time

Can anyone help. I can't find where the error is..
I am attaching the new files!

 

 

I start the spindle with Gmoccapy gui

rodw wrote:

You really should give Ethercat a try!

I would, if someone is willing to go through hell of sending me an EtherCat drive that can handle a 3.5KW Siemens (or was it Indramat?) servo motor, for free!

I do not know where are you from Tommy... But tell me the continuos current and operating voltage.. these are relevant for driver configuration ... i have some obsolete ethercat drivers free but they are little bit exotic in configuration and they are handled only by my custom component for CSP, CSV and homing mode.. everything is working same same but different.. 

​​

Hello all !

I've got an update to share now that the n100 seems to be operating properly.  YAY!!!!

In the end I never could get the pings below ~1.5ms whilst using the previous ISO install, so inspired by the recent 2.9.3 release I tried again from scratch. This is what I did...

1. Download the 2.9.3 ISO from linuxcnc
2. Burn to USB, install to the N100 miniPC
3. Follow all the steps in the excellent @rodw guide : docs.google.com/document/d/1jeV_4VKzVmOI...I_PhCm1x7oiw8VcLFdiY
4. Once networking was configured I ping'd the mesa, and it reported <0.5ms replies. Awesome!
5. However, latency was still an issue. So followed the r8168-dkim install steps, and then critically the kernel options noted by rodw at step. 56, including the r8168.eee_enable=0 setting.
6. After that, latency super ! (images attached, with web browsing and file access going on).

I didn't run _rt_setup, but did add the isolcpus=2,3 to the kernel options.

About the only thing I didn't do from the guide, was that I didn't run _rt_setup. As things seem fine without _rt_setup I didn't want to tempt fate! Perhaps the issues previously helped by the _rt_setup irq pinning have been improved by the newer linuxcnc version or some-such.

So the moral of the story... If you are struggling with N100 or Realtek drivers, don't give up!
Try again with the latest linuxcnc and hopefully you'll find yourself with a fantastic MiniPC for CNC!

Thank you again for all the advice from everyone. It all helped form the final solution.


 

Hi,

For fun i made some video's of the 5 axis tooldir blending.
I typed some gcode lines for xyz and added some abc values in radians to it.
Some of these blending really blow's my mind. It can just filter out complete rotations on a & b axis....

in your hal file:
To load the realtime component (the name 'not.myexample' is arbitrary)
For the component to be executed in the servo-thread we need to add it.
Note: The order of how components are added to the thread matter. You will want this after the ethercat read and before the ethercat write. Otherwise you may loose a cycle before the state is valid.

Then you can connect the signals:

Wie gesagt es ist auch nur mit qtplasmac

Also, if you have HOME_FINAL_VELOCITY set at 0, change it to something reasonable, otherwise it does the final move at max velocity.
I am happy that you are very happy with the machine, just watched the video.

onceloved wrote:

You can run it multiple times to find the servo drive that can OP every time. Use ethercat sii_read to read the sii data in it and compare it with the sii data in the drive that cannot OP to find the difference. The easiest way is to use ethercat sii_write to write the good sii data. It has been several months since I solved this problem and this problem has never appeared again.
 

Can you educate me more about ssi and all? how to capture? Totally banging my head in wall

rodw wrote:

Aciera wrote:

I think I already tried using "not" component, can you confirm this is right format?
I know nothing about EtherCAT, so I have no idea if you can get an inverted value back from the drive. What I suggested was using the built in HAL component called 'NOT'. For which you would need to use 'loadrt' and 'addf' commands and connect the input and output pins in hal.

You really should give Ethercat a try! Some Ethercat settings can have the direction altered by changing a SDO setting. But I doubt a status pin will. 

Can you pl share any relevant example? with "loadrt" and "addf" commands?