Py3 - Probe Basic Config Conversion Doc Lcnc 2.9+

jay.perez1 wrote:

Hi Chris,

I heard there's been a lot of development on Probe_Basic recently and some new contributors.

Thanks for the fantastic work everyone !!!

Question; We currently have two CNC routers running Probe_Basic on Debian 10 and Mesa cards. We're trying to build a new Probe_Basic controller using a Raspberry Pi 4 and the BTT SKR v1.4 Turbo board. Do you know if the instructions above will work for that situation ?

rpi does not support the vtk used with qtpyvcp and is not supported. some have tried but i have not seen a successful implementation to date that i am aware of, if someone has done it maybe they can chime in?

jc2ktr wrote:

Hi,
thanks to your instructions i got Probe Basic set up.

But i have a weird problem which i don´t understand. I have a working Machine with Axis Screen and Ethercat Hardware (motion & io).
If i start this Machine i am able to jog around and the jogged distances & speeds match the movement on the machine.

In Probe basic somehow the Axis are moving far to slow also the distances are off. Seems that there is some scaling done in background?

I don´t know where i can also look.


My Axis - INI / hal

File Attachment:

File Name: EtherCAT_S...1-06.ini
File Size:2 KB

File Attachment:

File Name: ethercat-c...1-06.xml
File Size:8 KB

 

File Attachment:

File Name: probe-ec.hal
File Size:5 KB

My Probe Basic - INI / hal
 

File Attachment:

File Name: probe_ec.ini
File Size:5 KB

 

File Attachment:

File Name: ethercat_s...1-06.xml
File Size:8 KB

 

File Attachment:

File Name: EtherCAT_S...1-06.hal
File Size:4 KB

 

use the config conversion document in post 1, your increments setting is wrong way to many to fit probe basic and missing the "JOG" label for continuous jogging mode.

PB does not scale anything beyond the on screen sliders and these are scaling via percentage against the ini configuration, if they are too slow make sure they are set to 100% on screen for both the velocity slider and jog slider.  this will set both to maximum, if thise does not resolve the issue i am unsure what else it could be, perhaps a setting in the ethercat configs?  but i am not current on ethercat setup, perhaps @rodw can chime in if the first fix does not resolve the issue.

as for scaling and moves not matching this is 100% in the ini setup and or hal. so you would need to ensure those settings are correct.

Chris

Lcvette wrote:

jc2ktr wrote:

Hi,
thanks to your instructions i got Probe Basic set up.

But i have a weird problem which i don´t understand. I have a working Machine with Axis Screen and Ethercat Hardware (motion & io).
If i start this Machine i am able to jog around and the jogged distances & speeds match the movement on the machine.

In Probe basic somehow the Axis are moving far to slow also the distances are off. Seems that there is some scaling done in background?

I don´t know where i can also look.


My Axis - INI / hal

File Attachment:

File Name: EtherCAT_S...1-06.ini
File Size:2 KB

File Attachment:

File Name: ethercat-c...1-06.xml
File Size:8 KB

 

File Attachment:

File Name: probe-ec.hal
File Size:5 KB

My Probe Basic - INI / hal
 

File Attachment:

File Name: probe_ec.ini
File Size:5 KB

 

File Attachment:

File Name: ethercat_s...1-06.xml
File Size:8 KB

 

File Attachment:

File Name: EtherCAT_S...1-06.hal
File Size:4 KB

 

use the config conversion document in post 1, your increments setting is wrong way to many to fit probe basic and missing the "JOG" label for continuous jogging mode.

Okay i will undo my changes in this section to your defaults

PB does not scale anything beyond the on screen sliders and these are scaling via percentage against the ini configuration, if they are too slow make sure they are set to 100% on screen for both the velocity slider and jog slider.  this will set both to maximum, if thise does not resolve the issue i am unsure what else it could be, perhaps a setting in the ethercat configs?  but i am not current on ethercat setup, perhaps @rodw can chime in if the first fix does not resolve the issue.

Alright then i will test this next time i am on the machine

What i have already tested is the joint.0.vel-cmd output in both Machine sets

in AXIS Screen the output value at jogging the X-Axis was around 2.4 
in Probe Basic the output value at jogging the same Axis was near 20

in Axis Screen the movement speed of the Machine was normal but in Probe Basic it was very slow as for scaling and moves not matching this is 100% in the ini setup and or hal. so you would need to ensure those settings are correct.
i will look at my configs again and compare my 2 hal and ini files in vs code maybe i find something

Thank you 

Sven

Chris

I have built vtk from source on a Pi a long time ago (5 hour build) and it worked with PB
But there is no need to do that as vtk is now supported for ARM64 (raspberry pi 4/5) in the Debian  repositories
try; sudo apt install vtk9
you may also need python3-vtk9

There should be no reason why the qtpyvcp team can't build a pi compatible deb and host it on their repository.

EDIT: if you do that, pleas elet me know and I will include the qtpyvcp repo in the 2.9.2 installers

It’s been looked into, but like anything, its a case of competing priorities.

i dont know if i missed this or not, or its just a issue with how i installed probe basic.

i started with a clean install of 2.9.2  and setup a axis config using a saved pncconf. 
tested the axis config and machine worked like it should.
then i followed the guide to setup probe basic.
when i tried to first start it i had a conflict.   axis vs probe basic manual tool change.  just had to go and hand remove all the axis call outs( dont know how to refer to it ? axis code for tool changes) .

Hello.
I'm an absolute novice on the subject and I need help.
I installed Debian 12 from the website  kcjengr.github.io/probe_basic/quick_start.html
I followed all the instructions.
The installation was successful, and the Probe Basic simulation starts up.
I configured the machine in Pncconf in Axis version, and everything seems to be okay.
Then, step by step, I followed the conversion instructions mentioned above. It seems to me that I did it correctly, only changing in the ini file in the "TRAJ" section from 5 axes to 3 axes and from XYZAB to XYZ. Previously, I changed G20 to G21.
Unfortunately, the program does not start, and an error pops up.
I'll add that the card I'm using is the Mesa 7i76e.
I attach the report generated by Linuxcnc to the post.Perhaps someone will notice something?

I think this entry is located in the file Moja_Maszyna.hal.

But the [EMCMOT] section in your ini file is empty.



[edit]
for your setup I would have expected something like this:

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
SERVO_PERIOD = 1500000