Advanced Search

you need to write your hal by hand. check the stiickies and start with an example config.

Dude please don't change the subject, it makes things hard. I check this thread regularly.

atrex77 wrote:

can you share the AXYZ_connect.hal file?
 

The opening post has all the files as attachments, just download and save them.

The hal_parport driver creates the pins & such and also talks directly to the parallel port hardware. I'm not sure if want you do is possible. I would imagine it would require a very special real time driver. I would also guess you wouldn't get any extra performance over using a parallel port as the step & direction timings would be created by the Linuxcnc software.

A great thank you to the team and testers! This is gonna be a big milestone for LCNC…

Well, well done!

Pierre

I just got a SCATECH EV1616DN module with the view of using it instead of parports. I have the hal operating the module.
I used github.com/pklopping/linuxcnc-ethercat-b...asic_digital_outputs for reference.
I'm lost as to how to integrate this back into a linuxcnc hal file generated by stepconf.
I assumed that I could simply change the parport references to lcec but, for example' there are no -reset pins etc.
Can you point me at an example of a compete configuration using ethercat?

I think PCW was referring to the power supply for the mesa card.

You may also be experiencing issues with the RPi4 ethernet powering down, this is a much talked about issue.
If you look at the RPi sticky under installing Linuxcnc the very last post discusses this issue with a link to some trouble shooting.

It is a raspi 4 8 gb version. I tried with a changed power supply and after few hours it again reset. Upon pressing the reset button the axis showed no movement. However, after restarting linuxcnc it started working fine.

Well keep us in the loop with your updates. If you are rapidly changing things then maybe wait a bit for inclusion - unless you are interested in on going linuxcnc development?

This is the reason for crazy data readings on encoders ?
I make now a config that encoder.count and encoder.velocity goes crazy to see if it stops by setting update-hz to non zero

Yes problem of noise in encoders resolves by non zero value to update-hz
verified by different configs that produced random data to different encoders.
All random data stop to encoders if update-hz is non zero but stop and modbus device to work.
 

Yes, this is a long known bug, never set the update rate to 0.

Since the units of maxerror are RPM, I would start with say 25 or 50
(.001 RPM as you found will simply operate as open loop)

Also limiting the rate of change of commanded RPM (with the limit component)
will reduce overshoot
 

Seems to be related also to this
forum.linuxcnc.org/27-driver-boards/5432...v2d-firmware?start=0

If after startup set update-hz to 0.0001 or something non zero problem seem to stops..
Is this division by zero bug?

Can you also include the exact .mod file that you are using?

 

I don't run debian 10, but Bookworm and actually use a rk3588 sbc which works very reliable. But here is the 6.12 kernel for x86 I've used before: drive.google.com/drive/folders/16Xlry00L...SlwznPLv?usp=sharing

But you can also download some from Debian, 6.13:
packages.debian.org/experimental/amd64/l...13-rt-amd64/download

And others:
packages.debian.org/search?keywords=linux-image-rt