Advanced Search

I think I successfully entered debug mode, but when I rotate the shaft, no change is detected in encCtn. Or I am viewing incorrect information. 



Eventually, as I tested the method further, I found that it actually counted…it worked.
 

Get Debian with the Mate or GNOME desktops, it is miles better than XFCE.
And, yes, it still has issues, Debian issues, but much less than before. Talking about 12 here.

MirkoCNC wrote:

In my case, it would be more convenient, as I only have Linux on the Raspberrry Pi 5.
 

For the Windows convenience I'd still recommend a debian Virtual Machine for the Rio, toolchains, configs, and bitstream gen. They are easy and quick to put together. Only challenge I could think of is the bit file programmer, some VM aren't good friends with USB2.0/3.0 (e.g. Hyper-v).

It's been a decade since I've VM anything and so I wouldn't know which is best to use. Bet Virtualbox does it USB nowadays though.     

You may also install LinuxCNC using the official Debian ISO. It works great.

However, I personally hate Debian.

I believe that Debian is the least user friendly, most confusing, most non-intuitive OS ever made.

Wi-Fi adapters may increase latency.

Be careful!

In general, it is best to physically remove as much unnecessary hardware as possible, then Install Ubuntu.

Just so everybody is aware, linuxcnc-uspace does not install on Ubuntu 24.04 LTS due to dependency errors caused by irrelevant Python version issues. Python 3.13 can run Python 3.10 code just fine!

When you say "us", are you implying that LinuxCNC has its own legal entity and belong to a registered individual/group in the same jurisdiction of this so called EMC2 company?

I have an OSS de-obfuscating project named "Microsoft [name redacted]". They emailed me roughly 30~40 times(I've stopped counting) with endless threats to sue, among others including what sounded like personal threats. Been 8 years... where the f are they?

7I92T firmware for 2X C11G

 

You can build these files yourself with the source supplied
in the 7i92t.zip file and using Efinixes free "Efinity" tool chain.

The pinout source file for C11G was already done (for the 7I92)
so it was just a matter of selecting that pinout source file and building
I just have not got around to building all the 7I92 configs for the 7I92T

awesome, just downloaded and gonna take a look! thanks spumco, I am sure i will have a few questions.. lol

upgraded to 2.9.3 today, camera resolution doesn't fit
 

That all looks normal except you do not have the digital field I/O
probably because there is no field power applied (orange connector)

Are you using the drive enable signals to disable the drives
when there is a fault or LinuxCNC is not running?
 

I'm trying to determine both minimum and nice to have hardware requirements when using the lathe macros.
Assume I already have the following:

• Suitable PC with touchscreen
• MESA 7i96s
• Stepper/Servo for both Z and X axis
• Encoder linked to spindle with A,B,Z outputs
• Manual Start/Stop & Fwd/Rev switches
• Pot presently controlling spindle speed.
• Scales on X & Z not sure the lathe macros need the actual position data but I definitely want the actual position displayed because my leadscrews have a lot of backlash. My assumption at this point is that I will (hopefully) be able to use the macros in a way that actual cutting occurs in one direction only and then the tool retracts, re-positions (including required backlash) and then continues on the next cutting pass, does that sound like a reasonable expectation?

The unclear to me at this point hardware:

1. Pretty sure I need a cycle start button, not sure about a cycle stop?
2. Do the lathe macros need Linux control of the spindle speed, or can I control that manually via the existing potentiometer?
3. Are limit switches required?
4. I will make a control panel so any nice to have features would be good to know about now so I can included them, perhaps a couple of  rotary encoders? what else would be good to have?

Much appreciated
 

Ubuntu 10.04 with LinuxCNC
linuxcnc.org/iso/ubuntu-10.04-linuxcnc3-i386.iso
Does the HP have a parallel port?

Config attached.

The basic stuff you want for the ATC is in 02_atc.hal (shockingly ).

ATC control scheme basics:

• HAL
  • Carousel.comp set to INDEX mode
    • Requires 1 sensor per pocket, plus 1 per-rev sensor (home)
  • Spare Mesa stepgen (not an axis/joint) set to velocity mode
  • carousel.comp motor-vel pin connected to stepgen velocity command
  • Pocket request (for new tools) is connected to carousel.comp via motion.analog-out
  • Carousel enable pin connected to motion.digital-out
• INI
  • All stepgen & carousel.comp 'settings' are in a separate INI section
  • align-dc and decel-time pins are used for carousel's fine-alignment feature (carousel final-approach to sensor from same direction regardless of starting CW or CCW)
  • Some settings present in the attached INI are not needed, but are legacy/leftovers from when I was trying to use carousel.comp in COUNTS mode.  I think carousel.N.scale is one of these.
• Subroutines
  • All the subroutines are pretty well commented, but m10.ngc is the primary ATC rotation management sub
    • Instead of the original PB M10->M11/M12 logic, I simply pass the desired destination pocket from toolchange.ngc to m10.ngc
    • Inside m10 is an M68 E0 Q#<P> line, followed by an M64 Pn (carousel enable)
    • That's all there is to get carousel to drive the platter to the correct pocket.
  • Remaining logic in m10.ngc is strictly used to drive the PB screen widget
  • M11/M12 have been repurposed for using the built-in carousel jogging and keeping it synch'ed with the screen widget
    • I think this could be done better, but it's working and I had other fires to put out.  There's no verification of synch between carousel and the screen widget, nor any synch error handling.
  • M13 is for homing the carousel.  Again, the sub(s) use carousel.comp's built-in homing logic - no math required.

That's about it for the ATC stuff.  Lots of other things in the config, but those are just for all the complications I've added.

Let me know if you've got questions after digesting it for a bit.

-S