Advanced Search

So much for AI replacing everybody. I guess that would stand for Algorithm intelligence LOL

Should we nail it ...hmmm pin it ?
And adding the download link would be good.
Thank you.

Aciera wrote:

The documentation is outdated, try clicking on the colored channel buttons on the bottom of the screen to toggle channels on/off. Eg the red button with '1' on it.

Hi Aciera, thank you. I have just now re-run it. It works as you have indicated. Best regards.

Oh you found that....
Been editing the damn thing since yesterday afternoon, copyright claims all over as i can not work without music.
I must say, it did a good job of removing music and leaving my voice and other sounds still audible.
But takes ages, currently the 4th is getting edited out, i have 5 or 6 more to go.
Still, it does play consistently despite editing in the background. At least something works properly on youtube, given that the algorithm is a total disaster, very iffy and extremely bad at figuring what to show me on "new to you", it has a 2 o 5% hit rate. No wonder tiktok is wiping the floor with them...

First lets talk about the images.
1: They are based on Debian repos built by a collection of custom scripts.
2: Whilst some images have been written to SD card via RPi Imager Balena Etcher is recommended.
2a: If you use Linux there are plenty of other tools, Ubuntu\Mint has USB Image writer.
3: If you use the RPi Imager any adding of user or wifi info does not work. As the image is a custom one, only the kernel is built from RPi Sources.
4: If you are using an Rpi5 & a 7c80 0r 7c81 the driver to be loaded is hm2_spix
5: If you are using an RPi4 & a 7c80 or 7c81 the driver to be loaded is hm2_rpsipi
6: The images now have the SPI interface enabled by default.
7: Location of config.txt  /boot/broadcom/config.txt once again this is a custom build.
8: raspi-config is not in the image, the tool to use is menuconfig.
9: The default username is cnc.
10: The default password is cnc.
11: The images are not meant to be a fully fledged daily driver Operating System, the are just enough to run Linuxcnc.

Links to images:
www.linuxcnc.org/iso/rpi-5-debian-bookwo...25-01-27-0140.img.xz
www.linuxcnc.org/iso/rpi-5-debian-bookwo...7-0140.img.xz.sha256

www.linuxcnc.org/iso/rpi-4-debian-bookwo...23-11-17-1731.img.xz
www.linuxcnc.org/iso/rpi-4-debian-bookwo...7-0404.img.xz.sha256

Why don't you document what you did ?

hmm seems to work in my tests now.

Thanks Tom I will give those video's a look after I finish watching you build your computer. LOL


 

That fixes the display, but doesn't allow spindle synchronized motion.

The way to fix this is to set the encoder scale to -180

I have a pretty convention setup (I think) with a Huanyang VFD connected via RS-485. Before switching to RS-485 controls, it worked fine from the control panel (on/off, fwd/rev, speed, etc.) but now that I've switch to RS-485, I cannot control the speed. I CAN turn the spindle on/off and set the fwd/rev directions from the Axis GUI. When I press the + and - buttons, I can see the speed changing in the "Spindle Speed:" GUI, but the spindle itself does not change; it's always at the minimum.

Here's a screenshot which shows the GUI, custom.hal, and some HAL display from Axis.

custom.hal:
loadusr -Wn vfd hy_vfd -n vfd -d /dev/ttyUSB0 -p none -r 9600
#type, name              val: source           >  destiantion
net  spindle-cmd-rpm-abs spindle.0.speed-out   => vfd.speed-command
net  spindle-fwd         spindle.0.forward     => vfd.spindle-forward
net  spindle-rev         spindle.0.reverse     => vfd.spindle-reverse
net  on                  spindle.0.on          => vfd.spindle-on
setp vfd.enable 1

Any ideas here?

Thanks


 

As an FYI I tried this and it doesn't allow the spindle to increase or decrease. 

it works on another computer without modifying anything I have an esp32 wroom with an spi card do I have to change the card number here?
and by what number?

Hi All.
What do these two qtdragon_hd.prefs vars denote?

 ps_probe_max = 20.0
 ps_probe_max_z_travel = 10.0

 

Ahmed.emara wrote:

• my Questions are : 
  • 1- if i switched to spherical shape instead of rectangular one will it simplify the calibration process, especially when compensating for B-axis tilt?
    2- is there is a predefined probe radius compensation in linuxcnc which i can use and it take considaration a titled workpiece
    3- For a DIY probe using the method described above (24V signal on contact), will this provide sufficient accuracy and reliability for calibration purposes or should I invest in a commercial probe for the long term ?

• 1 - All commercial calibration artifacts I've seen are spheres
  • They are attached to the work surface, and the probing routines (DIY or purchased) probe the sphere at various locations - including A- and B-axis tilts.
  • Center of rotation for each rotary axis is calculated after the calibration ball is probed in multiple locations
  • Some machines then write the absolute value of the rotary axes CoR to non-volatile parameters for use by TCP.  All that's needed from that point is to re-probe a few locations after operation to check & adjust for thermal changes.
• 2 - A number of the GUI's available with LCNC have probing features/functions.  I believe all of them have some sort of probe tip diameter compensation adjustment.
  • I don't think any of the LCNC GUI's offer rotary axis calibration probing macros, however.
• 3 - This is not the way commercial probes work - they don't pass current through the probe and part back to the controller.
  • Probes have a number of internal mechanism designs, but they are essentially a switch.  When the probe stylus is touched/displaced from it's resting point, the switch triggers and the controller sees that state change as a 'touch.'
  • Higher-cost probes use internal strain gauges to detect stylus deflection.  Lower-cost probes use the 6-ball mechanism Andy mentioned in his response.  An internet search for 'CNC touch probe mechanism' or similar should help you visualize what's going on inside.
• If you don't want to DIY a probe, and you don't want to pay for a Blum or Renishaw, there are lower-cost probes (wired & wireless) available which provide quite decent results.
  • The nice thing about purchasing a higher-end probe is that they generally come with a suite of probing macros which can be installed on the controller.  I've never used a commercial probe with LCNC, so I don't know if commercial probing macros are compatible.

It works now!


Is there some sort of step-by-step beginner's guide or something?

There should be.

It would make life so much easier for beginners.