Advanced Search

Thank you for respond anddypugh .

I go to check my file backup in cloud , oh  yes in  .ini file group DISPLAY lose  CYCLETIME [Gmoccapy.GMOCCAPY.GETINIINFO][WARNING]  Wrong entry [DISPLAY] CYCLE_TIME in INI File! Will use gmoccapy default 150 (getiniinfo.py:56)
float division by zero

Tomorow i will try.

Thank you,
Asis
 

That indicates that the RS-485 interface is OK

Hi,

I found a sophisticated solution..ethercat master igh(which one we already using) has eoe enabled from default.. it should be set during installation itself .. --enable generic --disable 8190too etc... when u add a --disable eoe... It will newer use them.. read ethercat master igh manual for more details

Let me know

Regards

Are Toggle and Toggle2inst separate independent functions?  Most of the examples I come across for toggling buttons use both. 

Is there a simple button toggle for a Mesa output using one or the other?

Italy

The card is repairable with inexpensive parts but requires SMT repair experience.
where are you located?

That's amazing!

It is nice to know that a more modern step-generation option exists that doesn't need Mesa boards. Eventually, the supply of the decade-old business-class machines would have run out so it's a much-needed find to keep homemade CNC machines affordable.

It looks like now you can piece together a decent machine with 2nd hand and new parts for less than $300

Example for those wondering:

Mobo: PRIME A320M-F ASUS - $60 eBay
Cpu: AMD Ryzen 3 1200 - $32 eBay
Gpu: R5 430 2GB GDDR5 - $14 eBay
Ram: Samsung DDR4-2133p 8GB - $17 Amazon
Psu: Thermaltake Smart 500W 80+ - $40 Amazon
SSD: Patriot P300 M.2 PCIe Gen 3 x4 256GB - $22 Amazon
Case: Matx case - $35 Amazon
StarTech.com 1-Port Parallel PCIe Card PEX1P2 - $32 Amazon

Total: $252 including sales tax (For IL that is)

You can definitely find some of these parts cheaper but I think the prices above are pretty average.

faaaasteeer!


Very nice. now I have questions on the spindle though, hahaha.

I did some further testing today, switched from Cinnamon to KDE, which runs much better and even better than XFCE. Here are the results of my stress testing, running for a couple of hours with 8 glxgears, two YouTube videos constantly playing, working with FreeCAD for my new machine design, and doing some compiling in the background.
Please notice that I run KDE on Wayland. When running on X11 the results are worse. The runtime of the test in the screenshot was only 4 minutes, but that was where the graphs had stabilized already. It looked the same after hours.

 

Below is the same test setup, but now with only isolcpus=3.
 

I believe I have the same N100 mini PC. Here are the results of my stress testing, running for a couple of hours with 8 glxgears, two YouTube videos constantly playing, working with FreeCAD for my new machine design, and doing some compiling in the background.

I running on Debian 13 (Trixie, weekly build; so far absolutely stable despite being not released yet), running KDE and LinuxCNC 2.9.3-1+b2

 

Hi PCW,

thx for your effort.

OK-- I just realise your strategy : We tested P1 and found the Hardware OK at P1 and than I fell into a trap with the loopback ---I assumed we were going to something similar to what you have been suggesting in

forum.linuxcnc.org/38-general-linuxcnc-q...-modbus-help?start=0

loop the onboard rs-485 to the pktUARTS on P1 so yesterdays results were the results of such a test.

But you wanted me to test a direct loopback from RX+ to TX+ and RX- to TX- of the onboard RS-485 -- sry my fault

The result of this test is:

without loopback:
0000EBFF
00002BFF
00006BFF
with loopback:
0000EBFF
00000BFF
00006BFF

 

So to give you a clear idea of my understanding of how things work.

1. before homing the controller is in 'joint' mode and axes (eg X,Y,Z,...) do not exist
2. a successful homing procedure ends with the joints being in a known position (ie each joint position is either zero or offset by the OFFSET or HOME_OFFSET values set in the [JOINT_n] section of your ini file or has a known position from an absolute encoder)
3. these joint position values are then passed to the Forward kinematic model which calculates the initial values for the axes position.
4. Axes are created as setup in the ini file (eg X, Y, Z) and are initialized with the values calculated in step 3
5. The trajectory planner calculates the axis positions and passes them on to the Inverse kinematic model which calculates the joint position values to be passed on to the motor drives (eg by way of step generators, ethercat command, analog voltage, etc).

Is it a correct assumption that the forward transformation is only called when homing the machine - and beyond that is not referenced?

That is what I _think_ is happening but I'm not positive. If you home your machine manually I wonder if you could simply set the cartesian position to zero in your forward kinematics:

As long as you have no OFFSET or HOME_OFFSET values set in the [JOINT_n] section of your ini file then that should give you a cartesian coordinate of X0/Y0 for joint0.pos_fb = 0/ oint_1.pos_fb = 0. But again I'm really not sure as to what actually happens behind the scenes which I think is here:
github.com/LinuxCNC/linuxcnc/blob/master...emc/motion/control.c

I have a ryzen 5 1600 on a b350 (or 450 can't remember) and a ryzen 2600 on an a320 (or whatever the cheapest board was at the time)

Both show numbers around what you are seeing and work great!

Thanks that worked, also the +5V GND on the encoder section also works. No need to provide separate power to MPG.

thanks