Advanced Search

Clearly you are not understanding the basics of networking. Please watch my 7i76e video. Networking is covered about 17 minutes in from memory.

Thanks for the quick response

Okay I must have misread what others were saying it seemed like a wrong practice to run the same ip for two devices on the network.

I'd like to post a pic but the file size limit is to low here.

Hm2_eth: rtapi_app_main: Network is unreachable (-101)

That's the error I am getting

Still I'm not shure why I'm not getting different ip addresses from the mesa card regardless of jumper location.

I am currently building a CNC control application using Qt C++ to control servo motors via EtherCAT.

I am encountering errors while attempting to execute the following HAL functions within my Qt code: hal_init, hal_ready, hal_export_funct, and hal_link.

Additionally, when I use the halcmd utility to add components or functions, I am unable to use (access) those resulting HAL pins/fields within my Qt C++ application.

Thank you.

Is there any reason you can not use halcompile to build your component. As that is the "traditional" way to build components outside of the build process.

Not entirely clear about what you are trying to say.
Please attach any images to your post. So until you attach an image I can't comment on the boot issue.

You shouldn't be assigning 127.0.0.1 to any interface that requires traffic to go to another computer or device on a network. That address is traditionally used for "internal use only". Or the "local host".

The IP of your computer and the IP of the mesa card must not be the same. It's like having 2 houses on the same street having the same number.

10.10.10 could be considered the street name, the last number is the house number.


Pick ,say 10.10.10.11 for your PC.

Hello,I am encountering a persistent linker error while building a HAL component for LinuxCNC, despite correctly identifying the location of the required function. I would appreciate any assistance from members who have experience using. 1. The Problem I am trying to link my component, but the build fails with an "undefined reference" error for a HAL API function. 2. The Setup and Findings ItemDetailsInitial Linker OptionError MessageSource of ErrorI confirmed that the functionis not defined in.Function LocationI found thatis defined in the real-time library:.Attempted FixI updated the linker options in my build system (afile using qmake) to include both libraries:and.Resulting ErrorThe linker now reports that it cannot find thelibrary.
Sheets로 내보내기 3. The Core Issue The linker path to the directory () is accurate, and the library file () containing the function is confirmed to exist there. However, the build system or linker seems unable to successfully link.Could this issue be related to:

1. A specific linker flag order required for real-time libraries?
2. A misunderstanding of how the HAL and RTAPI libraries should be linked together (especially since

   hal_init

   is present in both

   liblinuxcnchal.so

   and

   hal_lib.so

   )?
3. An incorrect way to specify the library name (

   -l

   ) when using an absolute path or a custom library path (

   -L

   ) in the build system?

Any guidance on how to correctly force the linker to recognize and useforwould be greatly appreciated.Thank you.

I switched w13 and w14 as the instructions declare and I am still getting 127.0.0.1 in either default and eprom.At any rate I am getting a error on boot www.facebook.com/share/p/1BkDAYUf7Q/Fb post with the image of my error. I changed the ip of the pc to match the 127.0.0.1 to match what people are doing with 10.10.10.10 but still no luck any thoughts cant find any eu specific info or a 7i76eu specific profile on linux cnc.

I would still fix the raspi thing, it'll bite later on.

And the kernel supplied RealTek drivers aren't the best.

Are you talking of the resolution of the camera or the size of the window?
There is no built in way to set camera resolution but you can scale the window.

linuxcnc.org/docs/devel/html/gui/qtdragon.html#_camview_tab

It looks like the error is on my side. Lan adapter was disabled in BIOS. After enabling it, Lan connected to network using live installation.

Thank you guys for all your support and suggestions.

M

Yeah it is a bit tricky this one. The basic_cia402 device is a very capable device, but as usual with ethercat one need to know everything in advance.
The documentation github.com/linuxcnc-ethercat/linuxcnc-et...umentation/cia402.md outlines many details and mentions the modParams, with which one can enable and disable features of the drive.

The first error is about sdo 0x6060 and 0x607c, and in the doc one can see what they do.
Your drives don't have those features is my assumption, or not enabled. You need to get rid of all,those sdo download problems.

Anyway, what you should do is take the output of the command "lcec_configgen"
which will have a long list of modParams and select those you are going to use and your drive has.
Not so easy to enable/disable right but give it a go.

Also, errors from ethercat generally goes into syslog, you can see them with the command "sudo dmesg" the last maybe 20 lines are the importqnt.

bentiggin wrote:

Also, do you mean one 1Mohm/2w on each wire for a total of 2 resistors or two 1Mohm/2w on each wire for a total 4 resistors?
 

1 resistor on each wire, two in total.
So my advice on wiring on the rectifier wont work as this seems to be an SCR controlled rectifier, but there is hope, wire resistors to the big terminals on the picture on the left side, use a DVM to find the torch and clamp connections, clamp will be positive and torch will be negative but you have to remove the torch cap to check as the outer torch nozzle is not connected to any of those.
Are the high voltage/high frequency parts on the other side of that metal wall?

From your error report:But that pin is not in your attached hal nor xml file, so wrong files maybe ???

Hello,

I got some trouble - with my ATC
Problem: 
ATC wont align to the right pocket number
Homing works not correct

The ATC has one INI to find Pocket 1 
A servo drives the magazin but i cant use the index for homing because the in comes several times per magazin rev.

my questions:

1. is it possible with the carousel comp to drive these ATC ?
2. if the first answer is yes - can anyone help me finding the errors in my config?

Thanks, bassti

I installed EasyProbe on my gantry mill running AXIS. The probe signal works, the manual zero buttons and the G54 - G59.3 buttons work.
None of the probe motion buttons work.
Any ideas on how to troubleshoot this would be appreciated!