Advanced Search

There's some generic information here:

linuxcnc.org/docs/html/getting-started/u...e_to_the_new_version

But it might be better to just ask here on the forum with an appropriate topic, like
 "How do I update LinuxCNC to the latest"

etc



 

Which one is that?

PCW,

Okay, I am trying to start with 2.9.3 but am having some trouble, is this just done through the terminal? Do you happen to know the commands to do it? Do I need to find 2.9.3 and install the package on my machine first? 

If it is not too much trouble I could go straight to 2.10.  But I have found zero info on how to do that..

I am running bookworm.  I know that I tried to download whatever was best and most recommended when I set this machine up. 

Thank you.

Best,
-Dylan

2.5 is quite ancient. Maybe have a look at
github.com/jethornton/position-logger


Or simply the subroutine posted above:

Ok,

Now, to cheer you all up,  i just put here some movies i made tonight.

It might be supported by 2.9.3 if not then you must use 2.10

You should be able to upgrade to 2.9.3 with the package manager
if you are running s normal Debian LinuxCNC release

PCW,

Thank you.

Okay, as best I can tell I am running 2.9.0 (that is what is show at the top of my axis gui and what I see when I use linuxcnc -v).  You reminded me that Peter said something about needing 2.10.. Do you know if I need 2.10?

Can I update linuxCNC? Do I have to wipe the entire machine or can I just update? Will I loose any system configuration data if I do this or will that all be stored in my machine folder? 

Best,
-Dylan

Looks like you are possible running too old of a LinuxCNC version to support the periodm
though in this case, LinuxCNC should report an unknown module number.

Here's what I get for periodm pins and parameters on the 7I96S

halcmd show all | grep periodm

    35  u32   I/O            0x00000001  hm2_7i96s.0.periodm.00.averages
    35  float OUT           0                    hm2_7i96s.0.periodm.00.duty_cycle
    35  float IN               0                    hm2_7i96s.0.periodm.00.duty_cycle_offset
    35  float IN              100                 hm2_7i96s.0.periodm.00.duty_cycle_scale
    35  float IN               1                    hm2_7i96s.0.periodm.00.filtertc_us
    35  float OUT            0                    hm2_7i96s.0.periodm.00.frequency
    35  bit   OUT             FALSE             hm2_7i96s.0.periodm.00.input_status
    35  bit   I/O                FALSE            hm2_7i96s.0.periodm.00.invert
    35  float IN                1                    hm2_7i96s.0.periodm.00.minimum_frequency
    35  float OUT             0                    hm2_7i96s.0.periodm.00.period_us
    35  bit   OUT              FALSE            hm2_7i96s.0.periodm.00.valid
    35  float OUT              0                  hm2_7i96s.0.periodm.00.width_us

 

Well I now see there is pos_desired and pos_error but it looks like maybe a relative position.
relative to synced position?

I'm currently rewriting the i2c stuff from scratch,
until now, each device needed its own bus with its own pins.
now i can configure several per bus and also separate them again via multiplexer chip

 

was a lot of work, but this is only the config of one i2c-master, you can also create several, on different pins with different speeds.

I'm still testing and not all the types I've created are working properly yet, but I'm hopeful
 

MichaSch96 wrote:

Do you see, that there's an issue with RealtimeIO and EtherCAT in parallel? (For EtherCAT I'll use the NIC of the PC chipset. For RIO I wanted to use the W5500 Ethernet module with an USB-Ethernet adapter to the PC.

Thanks for your support!
 

never tested, sorry
 

Why do you think that spindle speed is uncoupled from spindle sync position?
look in tp.c at tpSyncPositionMode()

Now I don't understand the code completely but I think the general idea is to:
-accelerate (at max) the axis to match the calculated spindle speed for the requested units per revolution.
-when it is synced speed then maintain the sync.

With a fixed acceleration rate, a faster spindle will take longer to sync speed.

To have threads always match you would need to also sync position and probably with a longer section of out of spec threads. I see no indication of position tracking

So I think it's a feature not a bug.

You mentioned that the 200 RPM plot is broken. Are you referring to the change of slope in the velocity before it starts oscillating?

No, I am referring to the fact that it never reaches a constant velocity but seems to only exponentially approach a constant velocity, I am ignoring the sawtooth velocity waveform,. You should be able to get rid of most of the sawtooth by using the interpolated encoder position (so the position is updated every ms rather than every encoder slot)

Here's the values for Z:
MAX_VELOCITY = 1.8
MAX_ACCELERATION = 2.0
These were set after a lot of experimentation. Higher values stall the stepper motor. I could try increasing the acceleration somewhat, but probably in the 10-20% range. Not sure this would make much difference. Let me know if you think I should try it anyway.

You mentioned that the 200 RPM plot is broken. Are you referring to the change of slope in the velocity before it starts oscillating?

Is it likely that the 10 pulse/revolution pulses are causing the problem? I could redo that part of the lathe. Getting greater acceleration will require a new stepper or servo motor and a lot of work.

I have two choices for the encoder-

1) I have some encoders in my junk drawer. They're both quadrature. One is a US Digital 1000 pulses/rev with a separate index signal, and the other is a more robust looking Accu-coder 2500 pulses/rev. Both are designed for small shafts, so I'd need a belt or gearing to connect them.

2) I could machine a gear to bolt on the spindle pulley. It'd be about 7 1/4" or so in diameter, so how ever many teeth I could fit on it. Maybe about 90 1/8" teeth? Or 180 1/16" teeth? I don't have any feel for how many pulses/revolution is appropriate, so maybe this would not work.

Here's a photo of the two pulse generators. The 1 pulse/rev is magnetic and the other one is proximity. The teeth are for locking the spindle.