Advanced Search

 
and also radeon rx580

endian wrote:

zmrdko wrote:

Thank you for explaining. So basically we are better off with position mode. Because servo drive is better at handling position commands from linuxcnc. I am running 8kHz linuxcnc servo thread which is the same as 8kHz cycle in B3 drives. The following error showed in servo drive is basically zero with proper tuned servo drive. The linuxcnc shows following error 0.22mm at 3000mm/s speed and 0.44mm at 6000mm/s and 0.88 at 12000mm/s. Does it mean that I should just set MINFERROR in linuxcnc with some room (so that I dont get following error errors), because the the following error which lonuxcnc shows is not the true following error? I will come back with screenshots and exact values later.
hello zmrdko,

your thread in the linuxcnc are running at oversample 8kHz .. what is your confing for them ? hardware and else.. ethercat has which time period ?

Hi foxington,

i am running i7 9700k (8c/8t - i think it’s the last cpu with one thread per core)
32GB ram and z390 motherboard and external intel ethernet card. I had bad latency with onboard ethernet adapter. I have also better experience with full size built pc, rather than office desktops (dell, lenovo). I dont know if it’s the motherboard thing, but i achieved better latency results with desktop PCs without any hassle. Might be the power efficiency crap in office pcs.

The board name in the conf file is for building the firmware, the developer has a branch for another board that uses a different brand of FPGA, the tools used for the build will depend on the FPGA brand used. The conf file defines the configuration you want for your board, Linuxcnc does not use it.

The actual board name presented to Linuxcnc is buried within the vdhl files.

Towards the end of the gitub README
TODOs
add more boards
use InM and OutM instead of GPIO
make pncconf and mesact work out of the box

Which looking at the latest commits there has been no mention of.

So for the time being one would expect a user to start with the developer supplied ini & hal files and modify to suit.

Hello!
I'd also like to enter the discussion on getting MS300's CMM-02 module from PROP to OP. I did a bit of digging through the forum and tried a bunch of steps that seem to lead nowhere. I tried the steps in  silden's post  - no result. Tried a bunch of different initCmds - same dead end.
I tried to use EC Configurator but wasn't able to get it running as it asked me for registration key.
I have updated my EC master from the new repositories. When I run dmesg I see the skipped datagram and a bunch of errors regarding the PDO mapping of the original SII image. The hardware revision of the board is v2.01 ( at least that's what the sticker says).
I'd really appreciate any advice. If there is need to post any files, please let me know.

Best regards!

I posted this into that topic.

I found a site that describes how to make a generic cable (not the expensive HP one) work. Plug the cable into the PAR connector on the motherboard. On the other end, remove the two nuts and slide the plastic sleeve back. The pins will be exposed. If you look carefully at the connector holes (magnifying glass...) you will see they are numbered. Join pin 21 and 25 using a jumper wire. That's it - the port will appear in the BIOS, but it should already be working with no other config needed

I found a site that describes how to make a generic cable (not the expensive HP one) work. Plug the cable into the PAR connector on the motherboard. On the other end, remove the two nuts and slide the plastic sleeve back. The pins will be exposed. If you look carefully at the connector holes (magnifying glass...) you will see they are numbered. Join pin 21 and 25 using a jumper wire. That's it - the port will appear in the BIOS, but it should already be working with no other config needed

Tried to pin down version more accurately and got this:
LANG=C dpkg -l mc
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-============================================
ii mc 3:4.8.29-2 amd64 Midnight Commander - a powerful file manager

LANG=C dpkg -l linuxcnc
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
un linuxcnc <none> <none> (no description available)

So, for midnight commander I get a decent version number and apparently linuxcnc is not installed????

Now I am confused
greez
chris

RiJa wrote:

I'm using the same file as you posted earlier, the path on line 14 is:
loadusr -W ./lcec_conf ethercat-conf.xml

Yes, I know. I looked at my git repo before replying. But the difference is it worked for me and is reporting a file not found error for you. Read the error message you posted. I have also experienced similar errors in the past. You can either continue to complain or undertake some troubleshooting at your end to resolve the error like I did. I can't help further.
 

Kasper-001 wrote:

hello guys
i got a par of these Haas panels 
is it possible to set it up and running linuxcnc ?
 

Hello,

Did you managed to go further on this project?

 

Hallo! Ich will mir einen Plasmaschneider Bauen und bin noch ganz neu in linux unterwegs. Ich habe mal ein test setup mit einem Thinkcenter, 7i96s und thcad 300 erstellt. Ich denke das ich alles schon gut konfiguriert habe. habe auch testweise einen schrittmotor angeschlossen was sich auch mit der richtigen umdrehung dreht. Das einzige was mich daran stört, in allen videos die ich finde wird die Brennerposition angezeigt und bei mir nicht. hätte da einer eine erklärung/lösung dafür? ist aber nur in QTplasmac. Wenn ich die GUI Axis nehme dann sehe ich die position. hoffe das es nur an einer kleinen einstellung liegt 
Installiert habe ich es nach Talla83 von Youtube
uname -a
Linux Linuxcnc 6.1.0-18-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.76-1 (2024-02-01) X86_64 GNU/Linux

Ich bin auf was neuen draufgekommen.
Wenn ich das Programm starte sehe ich den Maschinentisch mit den grenzen aber sobald ich Home oder irgendwas mache Verschwindet es und ich sehe die größe des Maschinentisches nicht mehr

Help me please. I could not get.
I installed the mesaflash patch, it refused to see the board, mesaflash from LinuxCNC saw the board.

 
If I find the board, apply it and close it, the board starts with errors in the hal file, as I showed earlier, after restarting pncconf, and this window appears, the board stops starting.
Replacing it in the hal file does not help.

Then I noticed that when I search for the board through pnconf via DiscoveryOptions, it finds it:
 

What seemed strange to me is that the name of the board is MESAlhm2
 

Why? 
Because after I clicked AcceptChanges, it gave me an error.
 

And then I noticed that if you select the lhm2 board then everything works, perhaps this is the correct procedure. However, there are doubts that it is possible that on the initial firmware of the board I specified this name for myself, and this entails a number of errors.

 
Because The developer's instructions are outdated because it does not have board.conf and litehm2.bit.
From the current examples, it was not possible (initially) to install the firmware. I installed litehm2 which is here for XU. Then the board started up.
When I install other bit files they go through and the config changes, but something is wrong.

Now in the example configs the name of the board is RV901t

 

 

/

Donb9261 wrote:

I doubt it. It is a hard question to answer without seeing the settings for both sides. The B3 manual is a very lengthy one. I would start with ensuring the electronic gear ratios are set correctly and that the values match on both LCNC and the drive.

I am not too familiar with Delta products to be honest.

I would check that the motor type settings are correct, then EGR values. If the results are the same, then you may need to send a tech support ticket to Delta with the drive model and motor model with encoder type.

If you are running the motors unconnected to LCNC and the results are drawn from the Delta tuning software then I suspect the motor/drive settings are not correct. PPR for inc encoders or bit specs for abs encoders must be set correctly. Also verify the drive/motor current is compatible. I assume these have no brakes on the motors that are still engaged.

 

Delta products are great but servos and VFDs are really budget solutions.. delta asda with underestimated EEPROM which you have to overwrite before you want to use the ethercat is joke... if you want to use that as PTP manipulator or plasma with no expert tunning - ok... but for critical applications I do not recomend it ... there is more sophisticated solutions on the market 

zmrdko wrote:

Thank you for explaining. So basically we are better off with position mode. Because servo drive is better at handling position commands from linuxcnc. I am running 8kHz linuxcnc servo thread which is the same as 8kHz cycle in B3 drives. The following error showed in servo drive is basically zero with proper tuned servo drive. The linuxcnc shows following error 0.22mm at 3000mm/s speed and 0.44mm at 6000mm/s and 0.88 at 12000mm/s. Does it mean that I should just set MINFERROR in linuxcnc with some room (so that I dont get following error errors), because the the following error which lonuxcnc shows is not the true following error? I will come back with screenshots and exact values later.

hello zmrdko,

your thread in the linuxcnc are running at oversample 8kHz .. what is your confing for them ? hardware and else.. ethercat has which time period ?

Servo current is always calculated from the the end effect torque requirements and load inertia.

Velocity, weight, rigidity, and friction coefficients must be calculated +=2%. There are other factors to consider such as gear, belt, ballscrew driven axis. Whether one uses a precision gearbox to increase torque.

In the case of CNC, the cutting tool will add additional torque requirements but are variable sometimes needing higher response rates to remain on P/T path. In these cases, an appropriate safety factor for torque requirements is needed. The cutting will either try to pull the tool or push the tool which the servo must respond to. If I incorrectly size to a machine without the cutting tool consideration the drive may not have the excess power to control the dynamic load and will cause indeterminate cutting conditions especially through an interpolation move where one axis cannot stay in sync due to the dynamic load condition.

The drives available today have higher dynamic response rates. In many cases they have a 3x peak load that can be accessed in the dynamic range for a n time value based on the drive characteristics. But, this type of drive is more expensive.

Regardless, every drive has a specific set of characteristics and every motor has the same. The calculations for the axis are the same and your choice should be based on your specific application. In general, if the true dynamic load is unknown, it is best to choose a power range above the known values to account for your actual application. 125% of net need is usually a solid safety factor to assist with the dynamic loads for CNC machining.

If using Chinese servo motors and drives, I have found that in most cases the values given for the actual drive/motor combo are well, over blown. I always use a 135% to 150% safety factor for these motors to account for the variability of the actual specs.

Do your homework before you buy. Know your specific application. If unsure, then many servo OEM's will assist with the calculations if you can give them relatively accurate values for your machine axis. The math is not easy for sure.