Advanced Search

try isolcpus=2,3

There are several options:
1) do nothing (worst option for me)
2) test some basic GUIs and accept that it might break other GUIs
3) make your own offsetpage widget for Gmoccapy

I prefer 2) Over time, the GUI will have to be tidied up

I agree with you. Reducing at least the non-functional GUIs would be nice.

github.com/LinuxCNC/linuxcnc/issues/1762#sim

Interesting. I have just built a W, z attached dust shoe myself and started to look into getting it into HAL. Think I have almost the same requirements as you with manual override, auto-follow, park when tool changing etc. Would you mind sharing your ini file as well? And the rest of your HAL files, I'm missing the components used in your HAL above.

i would but I have no idea which other guis use this widget so I cannot test.

I started with the latency tests, but then I found the script to run latency tests.

The best result I got with with latency-histogram --nobase was about 230000

 

I logged every change I made and the results after the change, which gives me some nice insights what happens, but I cannot get the latency any lower. 

I mentioned the "Atom platform", but I don't have enough experience with hardware to know exactly what you mean by that. I can make an educated guess, but that's basically it. 
So instead of looking for PC's of a specific brand and type, would it be better to look at platforms that work well?
 

Soccer wrote:

When I was testing this signal input, I found that when I turned on LED0, the corresponding IO PIN was lit up at pin number 16. Similarly, the output position was also the same. In summary, the data I currently receive has been shifted by 16 bits. Additionally, I have attached my XML and the test results from Beckhoff (they are all OK). Could someone kind-hearted please tell me why?
 

Can you share whole config to better understanding please? I am interested in the two masters from your configuration ... how and if it is working? thank you

but defenetely you can not let 32bit lenght for halType="bit" I think ... 

<pdoEntry idx="6000" subIdx="01" bitLen="32" halPin="bit-in" halType="bit"/>

Check actual config over, then you will can read active configuration from online slaves... then just copy paste

Might also need $0 for the first spindle, so
M3 $0 S12000

Why don't you make this a Pull Request?

I've decided to include G28 and G30 position:

 

Files are here for anybody interested (based on current master)
 
 

Note
rows 1-3 (Tool, G28, G30) are not editable. (The comments of those CAN be changed in the .pref file though)
'offsetpage_widget.py' seems to have been written to be used by other Gui(s) as well. I have only tested this on Gmoccapy (there are substantial sections of the code that are not used in Gmoccapy)

Good to know samlevy0515 , do you know a good place were to buy them ? I found them on the sites that i named .

Hi, yes im the same guy , the machine its giving me some problems , btw if i can ask how much did you paid them ? I saw them for ~400 the motor and ~400 the drive. Leadshine seem a good product but idk i'ld like if someone can guarantee them for a professional work as the Delta , they seem pretty good at a really good price.

If you want 90% of Delta's performance at 60% cost, pick Leadshine.

Just run the latency tests that come with linuxcnc. If they look ok go with it.
But I've never had much faith with the Atom platform for Linuxcnc.

I did some configuration and testing on the Fitlet3.

I made changes in the BIOS, ran the script created by mozmck ( forum.linuxcnc.org/38-general-linuxcnc-q...ead-and-irq-affinity ) and did the latency test (results in the thread forum.linuxcnc.org/38-general-linuxcnc-q...ead-and-irq-affinity ). It doesn't look too good so far for the Fitlet3.

Does anyone have ideas on how to improve it because I'm all out of ideas (for now)