Advanced Search

!Update!:
Removed the dedicated spindle encoder index pin, now all encoder channels are handling the index pulses. In the project configuration you can now use PIN numbers instead of GPIO numbers,  dedicated chinese breakout board config files and picoBOB-DLX config file. 
You can try it with the Test branch.

i would like to thank your contribution to the project with testing, time and resources to Pubcrawlr and Galetops.

I try man hm2_modbus, command not found as you see in attachment i have linuxcnc 2.9.4, i check in linuxcnc official site this is the last version, i dont know where is the problem 

I presume you are talking about settings in the ini file. Neither unit settings nor pyvcp panel setup should require an .axisrc file.
When you say the display always opens to mm do you mean the number of decimal places?

the device was designed for metal materials. It was tested with other materials and although it works, the precision of the measurement is not satisfactory for me to sign under it as a manufacturer. It works quite well with wood, but a change in structure (a knot in a board) can significantly change the capacitance.

so the answer is: No, the device is designed only for metals.

But I have tried both adding gpio to user and not adding. (They were with fresh image install)
I hav read all that link before writing here but nothing changed.
I am using hal and ini files from another working rpi5. Their user names, file names and locations are same.
If i added hal_gpio to hal file, it gives an error about permission.
I added gpio to user, not worked.
I have created 90-gpio-access file as it described, not worked....
The only thing that I havent tried is SPI... I will try it and write here...

I try man hm2_modbus
and man mesambccc
not exist in my linuxcnc i have the last version 2.9.4 i see in linuxcnc official site this is the last version, if there is newest version tell me please
 

Hi all,I’m running into an issue with my 7i77 analog outputs and could really use some help figuring it out.Setup:

• 7i94 + 7i77 + 7i84
• LinuxCNC with Mesa HAL configuration
• QtDragon GUI

The issue:

• When I set hm2_7i94.0.7i77.0.1.analogena to True, I measure about 0.3V on all +-10V outputs, even without setting any value on an analogout<>.
• When I set a value on one of the analogout<> pins (e.g. analogout2 = 0.1) and leave analogena False, I measure no voltage on the corresponding output.
• What I expected:
  • No voltage at the +-10V outputs just by enabling analogena.
  • A voltage at the specific output only when both analogena is enabled and an analogout<> value is set.

My question:

Is this normal behaviour, or am I missing something in the configuration or wiring? What should I check next to diagnose this? 

 



​​​​​​​ 

This is what caught my eyeMaybe the hardware has past its best before date?

I feel like when I calling Microsoft customer's support...
"We dont know what is your problem, but it works with us..."

I know how Linuxcnc does the threading, and know why it is acceptable with LPT and not acceptable with devices using ethernet link.
LPT uses base_thread, ethernet uses servo_thread, so LPT can be ten times faster.

I told you few posts ago, the servo_thread=1000000 (1 ms period) can make delay that can produce 18 degrees positon error at spindle rotates 3000 rpm.
3000 rpm => 50 rps => 20 ms per revolution.
It is mathematics, everyone can make this calculations.

The solution is not send the extended index in hope the Linuxcnc see it, and resets position to zero when received it.
The solution is send raw_count latched at every real encoder's index edge.
We can restore encoder's index (if we need) from (old != new) at the component.
And we can reset position not to zero, but to real position captured at index edge.

We can be confused, because we use "index" word for different meanings (encoder's output, program variable, hal pin) but we can not change this.

Detailed explanation:
Let's assume the encoder's index edge occurs at 1000 raw_counts.
Time goes, counter counts A/B signals.
The component requests data.
At this moment raw_counts is 1050.
We send both values, counted and latched.
The component knows, the index was 50 counts ago and sets position to 50/scale not to zero. (of course only when hal index_enable pin is set)

What don't you understand?

I didn't want attached my project as offtopic, but I see I must.

You're either missing parameters in your var file or you need to update for the latest fix which was done shortly after the latest push was released due to a format error. If you verify your car has the correct car numbers listed so parameters can be saved persistently t then it's an update you need to run to resolve.

Please upload it. Or better yet make a quick video showing your hacking so we can all learn more.

Thanks!

Hello,

I am trying to find the answer to the question why do my axis view preferences not stay persistant between sessions.
Actually some options are persistant like show offsets or alpha blend program.
But some important ones are not like display inches (always opens to mm) and show pyvcp panel.
I have searched the forum and chatted with chatgpt for a few hours now and frustratedly cannot get my machine
to turn on with inches displayed. I have tried to make .axisrc file but that never seemed to do anything.
Does anybody have any ideas? Thanks.

Interesting product. Any idea if your sensor works with PLLA (plastic/polymer)?

Can't test at the moment as the intended laser systems aren't ready yet, but might be interested in testing and/or purchasing units soon.

ok, nevermind.. I rewrote the file from scratch and now its working.. not idea what happened before.