Advanced Search

Need to know all the version info, what Debian, what linuxcnc etc

At least i uninstalled Probe Basic and reinstalled it over this documentation.
kcjengr.github.io/probe_basic/stable_develop_branch_change.html

I use the second window frequently for moving files around without needing to exit full screen.

That said, If you guys find it important enough to put the time in to make the updates to the ui functionality and want to submit a pull request I will gladly review and accept into the main branch.

For me I have a list of more pressing items that I have on my plate that I need to carve out and allocate time for. But don't be shy to submit pull requests for features that make it better and more universally useful, the more folks puttig time in the more gets done! And it's appreciated!

Thanks guys,

Chris

You would use the encoder velocity as the joint feedback source for the joint used for the Z Axis

Basically, if you make a configuration (using pncconf or MesaCT) with Z being a
normal step/dir axis, you would replace the feedback coming from the stepgen
with the encoder velocity. What drives the Z axis?

Note that you need to scale the encoder velocity so it reads in machine units.
In addition, you will likely need to offset the reading
(perhaps using the scale or offset components)

The encoder scale will probably be a large negative
number, I can give you the math for this later. just stepping out
the door...

How are you installing?

Dies the sim show correctly?

Linux docs for hal things, probe basic docs for the rest

I would also like it, if the there were just 2 larger windows for the code and the files instead of 3.
I never use the left window becouse i did like @rodw said and use a shared network-folder as workfolder.
So i can export my file directly from fusion and have it in my Probe Basic. (with one litle problem, i have to go into a folder and back, after this the new file is there - sadly there is no F5 or Fileupdate-funktion or i don`t know..

Further more, for me it would be much better, becouse me Filenames are very long, becouse i write some important infos, sortnumbers and Version into the filename. This leeds to that i can`t read the full filename at the Fileexplorer. 

Best regards
Jens

I am retrofitting a machine, where I need to control the precise movement of the Z axis, I am using the feedback from the THCAD2 electronic board to transform the signal from the analog ruler from 0 to 10 v into frequency, the frequency is being read by the 7i96s board, the speed information hm2_7i96s.0.encoder.00.velocity appears. How do I configure the connection in the HAL file to recognize this signal as a Z axis position encoder? Please, if you have any examples, I appreciate it.

Before applying it to the real machine, I am performing some simulations in the laboratory. Below are the examples

In this image, we have a stepper motor connected to the shaft with a potentiometer that provides a voltage of 0 to 10 volts to simulate what will happen in the machine.

 

In this image, we have a THCAD2 electronic board that receives 0 to 10v from the potentiometer and converts it into a frequency of 100 to 1000 KHZ

 


In this image, we have a 7i96s electronic board that receives only one signal A in ENCA+ and ENCA+ from 100 to 1000KHZ

 


It seems to me that only the hm2_7i96s.0.encoder.00.velocity signal is usable to inform the position.  Because the other signs are always counting and adding infinitely regardless of the movements.

 


I didn't find any example on the internet to apply this hm2_7i96s.0.encoder.00.velocity signal in Z position return position setting, please, can someone help me with example?

 

explanation video translated by artificial intelligence, sorry if there is any misunderstanding
https://youtu.be/5GN0cps-YLc

Just occured to me that you maybe missed that the error message is not about 'motion.so' anymore but about 'liblinuxcnchal.so.0'.


[edit]

The file does exist in the usual place so maybe a path issue somewhere:

That is what switchable kinematics was developed for so create a 'switchable' kinematic file (you can use the 'millturn.comp' as a template) which will enable you to switch between joint and tcp mode.

Also see the 'sim/axis/vismach/5axis/table-dual-rotary/xyzab-tdr.ini' simulation config for an example. You will find the kinematics component used for that in 'src/hal/components/xyzab_tdr_kins.comp'

Recloned to new repo and went through the whole process again with the same result (ie same error) so I did

and ran './build.sh' but still the same.

Anyway, thanks for the effort, I'm out of time for today.

The "fails registration" message most likely indicates that
communications were lost during card initialization.

Is it possible there is a 5V power issue?

You might try simply pinging the 7I95 card
to see if there is a intermmitent communication failure

 

Since Today I have an error at startup. My machine is worked well the last two years. But today it comes to an error at startup. When I used it last time, two weeks ago everything was okay. I have not made any changes on the machine and pc has no internet.
It looks to me there is a problem with one of the Mesa cards. Report tells me “board fails HM2 registration”. I thinking this is the important message. Unfortunately, I’m not sure where I should start to search.
I have a Mesa 7i95 connected over ethernet. Over smart serial I have connected 7i83 and 7i84.
I can ping 7i95 and mesaflash readhmid recognize the board.
Someone know more about this problem?

Strange that it doesn't work on yours. Maybe I oversee something, although here it works on both, the last things i can try is using the same config as the non-rt version that works for you and only change the following settings:
github.com/orangepi-xunlong/linux-orange...s/rockchip_rt.config

Already tried another power cord/adapter?

Did you try to write the bootloader to mtd (spi flash) from my previous message?
Are there other people who experience the same when booting from nvme?

Mine shows the same cpu usage by the way, even while running latency-histogram. You'll see that rtapi (the realtime component) with priority -99 runs on the last cpu, so it works how it should.