Advanced Search

Easyprobe should work from 2.6 on (valutransformations in the messages) if I am right.

I wrote the most parts with 2.8.4 an finally with 2.9.2.

Julian

I have no idea how to share my screen or errors on the screen... I have to type everything or is there a way to copy / paste ?

Square brackets are used to separate sections of the ini file so they can not be used as comments.
# <<< this should be OK, most probably

IT WORKS!

I deleted the offending lines of text (supposed to be comments but I forgot the # ) from the ini file and it worked. My mill is calibrating my probe as I type this.

Thank you for your assistance in getting this working. Really appreciate the help.

-Sean

can you please post your current hal and ini files?

I have tried using other commands, find center, find edge, etc... and I get the same error message: Named Parameter #<_ini[probe]vel_fast> not defined

Is there a difference with version 2.8.4 for declaring variables in the ini file versus newer 2.9 versions?

-Sean

onceloved wrote:

However, it outputs the count value and has no direction. The encoder forward counter value increases, and the encoder reverse counter value also increases instead of decreasing.

In this video, the man controls the position of the axes through the counter. He does it through the arduino, but I think it's not so important and it's about the right connection.

Hit
the google drive link requires an invutation
but for those interested ,
the project was a python2 suite
and so is complex to use with a recent linuxcnc

today is -6aug2024 and
i had looked into the project
as i was wiriting a way to use arduino
ide compatible bpards for extra io

extra io is not the central use of hal2arduino/emc2arduino
so i am bot investigating firther
but
for those interested
here are notes and file
for a python3 version-

---

notes below vvv

---

Hal2Aeduino-notes.txt
06aug2024
Tom Powderly tjtr33
i was working on arduino io subsystem
for emc
( i am dictating this so it has lees typos than i genetrate

I came across Hal2Arduino/EMC2Aeduinoi thought it was a
similar solution that would allow boards compatible with the
arduino ide to be used with linuxcnc

well it does do that
but
does not enable all the io possible...

ppre-reqs
The pcb must hacve serial communications,
usb is hanbdies
tBoard must use the prescrobed protocl
( simpler than jepler's arduuino prorocol)

To discover what Hal2Aeduino could do,
i rewrote the main script for python3
(it was py2 and lib call and prints and range(,,,)
re different)( each change is noted )

and I offer it untested to anyone interested
( the comp ran enough for me to see it was not my path

in general
there are a lot of messages that could be passedfrom
linuxcnc to the arduino board

these messages are likethe nml message...
and are not useful for my project
others may find them useful

it took me a long time to discover
what this system actually did

i suggest for anyone interested can,
study instruction.txt
      &the top of the main python file
      & the contents of the .ino file
      
    Hal2Arduino it does not give access to all i/o pins
     of the arduino ( DI DO AI AO PwmO as i refere to them)
     Communicating those data is central to my project
    So I stop working with Hal2Arduino
    

   for anyone wanting to try it with python3
    here is the up converted file.
    
  note
   the code to discover the active
    serial ports
    that are connected to active arduino type boards
    is interesting in i think i will use it
    
   that code makes a list of all active
    serial ports
     and sens a special message to whatever is connected
     it's the connected board replies to the secret handshake
     then it is added to a list  of connected arduinos
     arduinos  here meaning a board compatible with the arduino id
      basically meaning a board capable of cereal communications
      
  i hope this could be of use choose some users
  tomp tjtr33
   
NB rebane P3HAL2Arduino.tx to P3Hal2Arduino ( noi extent)
make it executable
place in your $PATH
(i put it in .usr.local.bin)

I adfjusted the .ha; for ythe new comp name

find remaining files at Kurt Jacxobson's github
github.com/KurtJacobson/HAL-2-Arduino

Solved: All active PDOs needed to be filled up to 8 Byte, can't have a half empty one

Well, not completely just yet. There are still a few "no sync" error messages every 20 seconds or so, but we have a successful bidirectional communication which is a huge step forward. I hope I can treat the sync issues (which don't seem to bother the Leadshine servo drives) with rt-preempt kernel and <master idx="0" appTimePeriod="1000000" refClockSyncCycles="-1"> as per github.com/sittner/linuxcnc-ethercat/issues/45

Ah. You are right..He did not mentioned that he deleted the "[...]".

I notice that there are inline-comments_

I know it has already been suggested to use '#' instead. IIRC there should not be any inline comments in the ini file.

So maybe try:

If that works for VEL_FAST then do the same with all the inline comments.

Maybe another line ending story?

Did you copy it with a windows machine or something like that?

I would type the VEL_FAST... separately with the keyboard. Just in case...

He has it at the end of the .ini file.
The error sounds strange and I never had this one.

Other than copy paste the parts again I have no clue.

Julian

You need a G1 move to the last X Y position, before the starting line

Hi,

I found out the problem.

This is a test board i made a few years ago. It uses ethercat and drives stepper motors.
 

I found out that i can run the testboard on hal-core with a sample script.
This scripts only load's the stepgen.so and the lcec.so. It drives just one motor.
When i set a new position using halcmd : ./halcmd setp stepgen.0.position-cmd 1000
It runs to that position, as it should. The stepper sounds nice, and is quick.

So the underlying problem is the trajectory planner of halcore. This consumes too much time as it
is also added to the servo update thread. It slows down the servo update thread. I think this is the cause
that the production machine on the parport also run's not good.

So i will qreate a chrono timer, to first measure the total time of the trajectory planners cycle.
I expect it will exceed the 1ms time of the servo update cycle, but i don't know for sure at the moment. We will find that out.

Then we have to pin point where the time consumers are located in the trajectory planner.
So far i am happy that the ethercat works ok.

Running on : 6.1.0-23-rt-amd64