Advanced Search

Might be related to this issue that was fixed in 2.9:
github.com/LinuxCNC/linuxcnc/commit/6bc4...27f7d81c978ff5050436

change this line:

to


Then the pin 'joint.0.request-custom-homing' (the uppermost entry in your 'WATCH' list should give your the options 'Set' , 'Clr' to manually set the pin to true (ie 'Set'))

Thanks for the effort putting in this modification! Now I have time to test it. 

This is what I do:
Download the file el8_homecomp_mod.com and after giving the path to homing.c compile with halcomp
"sudo halcomp --install el8_homecomp_mod.com"

This went ok without errors. 

I changed the Marco's component from the ini to yours:
HOMEMOD=el8_homecomp_mod

Uncommented the drives internal homing in hal on every axis:

net x-home-request         joint.0.request-custom-homing     =>         cia402.0.home
net x-homing             joint.0.is-custom-homing         <=         cia402.0.stat-homing
net x-homed             joint.0.custom-homing-finished     <=         cia402.0.stat-homed

run the lcnc, and the hal pins show up:


I set a hal part for toggle the custom home request:
#custom home request
sets joint.0.custom-homing-is-requested true

After that I have errors, this pin not exists. But is there. Whats next?

Thanks!

However once i had changed all the pin outs to suit my wiring i was unable to open linux CNC as it was throwing errors saying it was unable to find certain pins (i.e. the decode)

That is because 'decode.' pins are created by a custom hal component called 'tumbler_decode'

This is from the 'Deckel.hal' file in the post you linked:

For this to work you will need to install the 'tumbler_decode.comp' from the original zip folder.

This is what I`m implementing now, but delta and leadshine are not correct and did not advertise just the half of the truth of gantry control. They both working on it, and many functions are not implemented yet. Like homing at all, rigid gantry function and align function. But I have the promise from leadshine they will finish the dual homing for the end of the month and will release a new fw.

Here is an example from Delta for Gantry control. Is this ideal, I would think not. But it would work for sure. The issue would need some research and direct questions to Delta on how homing/squaring is completed. Delta is a sharp group and most likely have this solution ready if asked to provide the details. I will review the manual to see if they detail this.

As shown only one axis is on the ECAT bus with the slave axis being controlled via the master drive via S/D with encoder FB from the slave closing the loop. 
 
Scroll to about the middle of the web page to "Gantry Control". The graphic is pretty simple to understand. 

www.pbasystems.com.sg/product/asda-a2r-delta-ac-servo-motor/


 

Hi Everyone
I am in the process of trying to get my Deckel FP4nc shifting gears.
I have ditched the standard motor control system of contactors and resistors and fitted a VFD that is configured to run at 50Hz as well as a jog at 5Hz to allow the gear shifting to take place.
I have set up the gear motor relays the same as stock and there are 3 gear selector motors that are able to turn the selectors 360 deg.
Each selector has 3 microswitches to determine the position.

I have been looking into a few methods of setting up the gearbox comp including a modification of RotarySMP's MAHO component (i am struggling to get the halcompile to work correctly)
Or alternatively i have also found another user Niko provide his config in the following thread forum.linuxcnc.org/10-advanced-configura...-gearbox-comp#246671 
Running the gearbox through classic ladder (which i am finding a little easier to follow and seems to be a perfect match for my machine)
To make this ladder based system work for my configuration i copied across the parts i thought were relevant from the hal file.
However once i had changed all the pin outs to suit my wiring i was unable to open linux CNC as it was throwing errors saying it was unable to find certain pins (i.e. the decode)

I tried opening the ladder program once i reset the hal as it comes straight out of PNCConfig but it seemed to be missing variables/pins as they were replaced with ????  (could be related the the hal??)

Apologies in advance for my lack of knowledge when it comes to hal and linux i am definately in over my head when it comes to code. I have attached my Hal and the ladder program for reference.

Regards
Josh

Yeah I see what you mean. Like you said in your other post, LCNC is not a company so therefore cannot itself become a registered or certified compliant OEM. Which places the burden on the community to decipher the proper logic and exactly where to place that logic to get the results you want.

As for tandem axis control such a gantry, wouldn't that be the job of LCNC? The drive is merely a slave. Sure it knows how to the job requested but each slave is an individual. But, I have read that ECAT has the ability to manage this axis configuration. I am not 100% on whether the control is in the master domain or slave domain. I will see if I can locate that document. It may help understand where the logic needs reside.

At the end of the day, most ECAT setups I have worked with use pure ABS and very seldom rely on limit switch/index. On Fanuc, even though the ABS value is valid and stored the user can still tell the axis to home to the switch even though the switch is not considered and stops at the pre-stored ABS value. This was done back years ago because users complained they did not trust the "home" position from the 23bit ABS encoder. Lol.

Both Siemens and Fanuc have a quasi ECAT bus. Fanuc calls theirs FSSB and Siemens the MPI bus. In their controls tandem axis control is relatively simple. If there is a squaring issue, the axis motors can be temp separated allowing for the MPG motion handwheel to be used individually for each motor(X>U) or X1>X2. The user moves the axis into a squared position and then looks at the ABS position for each motor. Then sets each motor to use those as the permanent home location. The motors are then rejoined as a tandem. When you call the home procedure, both motors move their respective offset locations remaining square. These motors are still treated as individuals in reality but shared the same motion thread meaning both X1 and X2 receive the same motion commands. Now, this works because the machine is highly rigid. If you have a "soft" machine the frame can twist forcing the frame to rhombus or the machine has R/P not ball screws. In this case, one would need to have some logic to "square" from the master through routine. Difficult for sure.

There is an ISO on the CiA402 schema, but on the slow bus side this is where the ability to use the extended params of your drive. On the PDO high speed bus, the standards are quite firm and I see no builder trying to shortcut that. It would be a 10 thumbs down and they would be warned by the ECAT Found. If they not a "certified vendor" then it would be anyone's guess on all of the drives workings. Sadly, there are many who "gray market" knock off drives that are "compatible". Only not so much and the docs they provide are useless.

I think the most successful hardware should be a true multi-turn battery backed encoder with a drive that uses the stored value for homing and LCNC position updates. The work around you found POS_ABS = POS_FB or something like that would work as long as you can tell LCNC homing is complete, set the is_homed flag, and use the value from pos-act from the drive as the current machine position location for this session.

In the event that a user does not have the higher grade drives with mutli-turn and stored ABS then the routine would be 100% controlled by the LCNC side no different than if an FPGA was used if I understand correctly. The switches would be directly hal'd to the LCNC controller and use the existing LCNC homing routine in CPM mode. Just like it was a simple ParPort emulated S/D axis. The drive would have to have an Index pulse output for that to work. So there is that. Lol. Complicated stuff. But, imho this defeats the EtherCat solution to the problem this creates. Sure you can stick a stepper on the ECAT network and use inc encoders, but you are outside the box of the intended design of ECAT. These are far less expensive, but what is lost in the "customization" aspect has a cost also. Time is money. So, what is the true cost benefit? Hard to say.

For me, I am retrofitting a DMG DMU 50. It is used and I am rebuilding the machine to new condition. Because it is 5x and the project will cost me $150k+ it makes sense for me to use ECAT with solid drives and motors at $1000+ per axis. If I were to install the latest Siemens control with motors and drives my cost would exceed $225K total. Which is outside my exposure limit. If I were building a home brew machine with low rigidity, I would stick with a MESA card with S/D because the ROI would never be realized based on the complexity of building a FrankenSolution to force ECAT to work with my machine. Can it be done, absolutely. But at what cost.

Just my 2 cents minus taxes for net -2 cents with current inflation. Lol.

As linuxcnc is in the debian repos
No, what I am saying is that Linuxcnc does not support SPI interface on the RPi5. Too many hardware changes from RPi4, no new drivers written for the RPi5.

are mentioning SPI won't work when boot image using sdcard. Actually i want know it is possible to install linuxcnc using terminal.i am using this Debian GNU/Linux 12 (bookworm in my raspberry pi

This have gotten out of hand in a jiffy !
Thank you all for keeping it civilized, i do read everything all the time but had no time to reply.

I think Linuxcnc predates ethercat by 20 years or more so linuxcnc had to do it all. Don't forget there is a lot of other things involved in homing like squaring the gantry etc. How do you tell an ethercat drive it has a mate on the other side of the gantry and they are not perfectly aligned so it needs to move 2.0mm more to be square by a HOME_OFFSET? What about the HOME_SEQUENCE to lift the Z axis up above possible obstacles before moving X & Y? This is not specific to ethercat. We still need some of the standard elements of homing.c

The whole concept of the custom homing module is to do exactly what you seek. That is to tell linuxcnc to get out of the way so the drive can home itself. But the custom homing module was only a conceptual skeleton written by one very smart LCNC developer and its not just for ethercat. Its up to us to make it work for ethercat it.

If you read some of the lengthy issues on Scott Laids Git repo, you will find that CIA402 is not as rigid a standard as you think it is.

The other issue is that there needs to be a method to enable the drive and commence homing at the right time. Thats not in the homing module or the hal driver.

When I got involved in this, I was really stuck because I could not get ethercat installed on Bullseye that I had to run to get kernel support for my NIC drivers. Grotius was a life saver as he built a .deb file for me. At the time we were relying on an obsolete ethercat master code repository. Eventually I found the igh Repository on Gitlab and finally worked out how to simplify installation which I documented on the forum here. Over time Igh improved their repo as it came out of beta. I was really lucky to get some support from the guys at igh who contributed to some of my work by debugging the hal driver that had not been worked on for a long time

I built the 2.9 Bookworm installation ISO on the downloads page and moved  elements of my sticky into the ISO. Initially, I was hosting a repo for the hal driver. Then igh struck a deal with Sasha Ittner who initially wrote the hal driver to host the debs on their ethercat repo. This let me retire my repo. Not long later, Scott Laird got permission from Sasha to take over maintenance of the hal driver and started to do some significant upgrades to it. I was able to join the dots and before long, with help from igh, Scott had an automated build and test environment on his repo and his debs are automoatically built and deployed on the igh repo with the ethercat driver debs thanks to Bjarne at igh. 

So we now we finally have a reasonable ethercat installation path  for users in comparison to the dark mysterious abyss that existed before I got involved. There is enormous interest in ethercat now and many users are taking the plunge.
The time is finally right to push forward with ethercat as the build and distribution environment is in place.

So lets assume we get this homing sorted out in the short term, the next step is the sequencing of the switch on and start homing  logic.
I dd a lot of work to attempt to bring this into an earlier homing module that was never finished because it was obsoleted by big (but positive) changes to the custom homing framework and i lost interest in this for a long time and nobody attempted to take it on until recently.

I subsequently have formed a view that this is the wrong place for it. The reason  is that while homing is serviced by the servo thread, because it is an internal module, it will sit outside of the lcec ethercat loop. At best, this means our cia402 control will lag one cycle behind and at worst things will break. So the sequencing needs to happen in the hal loop (between lcec read and lcec write ) either as a seperate component or built into a ethercat driver module.

So sorry for the long winded essay, but ther is a lot of history to understand to go forward.

Hello, I am honored to be in such a forum.
First of all, I would like to say that I am new to Linuxcnc. I have 4 mtors and drivers that are not absolute encoders with ethercat cia402a support?? The drivers are working now but I couldn't manage to make it home. drivers manual link download.plcsystems.ru/Xinje/docs/DS5C1_servo_manual.pdf

I have 4 units of the 750w model, I can buy more After installing rodowan step by step and making the settings I knew, I made the step settings of the motors and started them.
Now the home and limit switch are not working????
All are in working order, so tested on Linux CNC The drive has h cw and ccw limit siiwtch inputs, but I did not understand how to connect it as a tom and I could not find enough information in the user manual for the connection.
All the additional linear rails and screw precision mills required for the machine I want to build are available, all of them are THK or Bosch brands.
I would be honored to test it I'm new to linuxcnc But I bought all the necessary hardware and all that remained was testing and processing.
If you wish, I am open to testing via remote access. ???? Please note that I have limited knowledge of Linuxcnc. I have a thinkercentre pc, asus touch lcd and many other hardware,
even a second cnc. I BOUGHT MES 7i95T, I will open a topic soon and add my progress for two cncs.
I will continue with the drivers of the other CNC, a delta asda-m-0721 3 axis single driver, a special driver. I am ready to test anything regarding ethercat. I am open to anything if desired. I speak a foreign language. I would like to thank Google Translete for its valuable contributions every time. I'M SO SORRY IF I DROPPED THE TOPIC.   

I've put a question in with the UK distributor for Leadshine to see if they have any info.

Did you try Leadshine directly? Or ask where the person on github got theirs?

I think R2EC are new so may not have made it to retail channels like Aliexpress yet