Advanced Search

Dear meister：

When I tested RIO, I was a little confused。

1. I set spi clk is 10Mhz, but 6.4Mhz actually
 
 
2. and I set shiftreg clk 1Mhz, but 323Khz actually
 
 

FPGA is ice40up5k

Is that correct?Thank you.

Tim

Tried to install this modified screenset but got a lot of errors. If I understand correctly here I need a modified handler.py file too?

 

spumco wrote:

Joco wrote:

Don’t make that assumption re feedhold. And tapping. The planner is taking things direct from the Hal pin. Not from the lcnc motmod module.

it needs to be explicitly tested. Unless someone has done so already and can confirm what the behaviour is. 
 

I can confirm that LCNC 2.10 disables feed-hold while synchronized motion is in progress.  FH has no effect during a G33 or G33.1 command until after the synch move is complete.
 

And that behaviour continues under scurve planner?  That was what I was referring to. Not what standard planner does.

@Grotius

Glad I can help. Yes, the code is stupid fine detailed. So for me it is a benchmark (standard tp has trouble to keep the speed, your tp is in generell faster) and not a "normal" everyday nc code. I have the code with different segment length, but the longer ones also hangs up after a while.

I played a little with the cycle time of axis. There is something going on, but I didnt get it. Maybe after you finished your steps we can go into the topic cycle time? I saw that you use a way shorter time than default. But maybe it is just a unknowledge on my side.

Still the same problem, returns every entry in the forum because the title of the forum contains EC300.

Ubuntu 10.04 will work fine with 512MB of RAM.

Hello. Thank you very much for what you share with me. I have already subscribed to you, but unfortunately, you do not offer me the option to translate the audio from your videos into my Spanish. There is some tool in Linux to achieve this translation.
I will install the Ubuntu that they shared with me, but how much ram do they use to work with?
What USB board do you recommend for my 32-bit netbook? Very kind and excuse my ignorance...

After pulling my hair out trying to figure out why G33.1 wasn't working on my lathe while attempting to test the problem raised in this thread, @cmorely pointed out I'm having the same issue.

forum.linuxcnc.org/38-general-linuxcnc-q...pping-problem#319786

So I can confirm spindle synchronization start points vary with spindle speed in G33.1 as well as G76 - and it's way worse on my lathe than the OP reported on his.

In my case a difference of 140rpm (60 vs 200) resulted in appx 0.750" difference between the Z-start point when synchronization kicked in on a 1/20 pitch (0.050").

According the the formula Andy posted earlier, my Z-axis requires the following distance to get up to speed

 

I don't understand why there is such a significant difference between what I'm seeing and what the OP's lathe is doing.

Unless somone has other thoughts, I think this is a bug.

Joco wrote:

Don’t make that assumption re feedhold. And tapping. The planner is taking things direct from the Hal pin. Not from the lcnc motmod module.

it needs to be explicitly tested. Unless someone has done so already and can confirm what the behaviour is. 
 

I can confirm that LCNC 2.10 disables feed-hold while synchronized motion is in progress.  FH has no effect during a G33 or G33.1 command until after the synch move is complete.

cmorley wrote:

I would expect speed changes to change the sync start point.
There is another post about non syncing threads with speed changes.
In linuxcnc, you can't change the spindle speed and track the same thread, the sync point moves.

Linuxcnc moves the axis as fast as possible till it is moving at the approximate correct 'pitch' speed. It then works to get the exact pitch and maintain it. This distance to get up to speed is kept track of for use of calculating position and position error.

IIRC linuxcnc allows 10 rotations past target before deciding there is an error.
 

Thanks for giving this some thought Chris.

I understand that LCNC needs a short period/distance of max accel to go from zero speed to synch speed - the other thread has a code snippet which explicitly states this in a comment.

What I don't get is why LCNC is moving so far to get up to speed.  My lathe has pretty aggressive acceleration - it can reach max speed in a very short distance.

But it's moving over an inch at rapid speed to get to the synch point at only 200rpm with a 0.05" thread pitch.  Feedrate at that spindle rpm and pitch is really slow - like 4ipm or so.

I guess what I'm seeing is identical behavior from the other thread... but much worse start point variation.

The other thread:
forum.linuxcnc.org/38-general-linuxcnc-q...s-with-speed?start=0

If you can use any Linux x86_64 on it, then download the official ISO and try installing it, but might have issues with RT kernel running in a VM.
You can try Debian 12.x or Linux Mint Debian Edition 6, and if they work just install LinuxCNC with
sudo apt install linuxcnc-uspace
This will also install the RT kernel, but it will not be the default one, so LinuxCNC should work OK in SIM mode.

Position mode = 0
Velocity mode = 1
Step type 0 = step/dir
Step type 1 = up/down
Step type 2 = quadrature
I think, been 15 years since i was deep into it, there are 10 step types, so 3 should be 3 phase at 120 degrees, and some more 4 pin types, and 5 pin/phase types.
Yes, LinuxCNC can do 3 and 5 phase stepper control, i still have some of those in the shop, i was very happy when i saw 5 phase motors move using 5 darlington transistors and 5 resistors from a parallel port.

tommylight wrote:

Did you notice i edited the post?
I saw you clicked on thank you after i posted so probably not.

I see it now, i will try your suggestions. Thanks a lot again

tommylight wrote:

No.
Several things will cause that:
-not enough air pressure
-worn nozzle
-to slow cut speed
-
I would also say to much current, but not exactly the same result, so i will just throw a stab in the dark at very, very low accelerations set in the config.

I thought so
I tried with many different air pressures and not much different, that was with 75psi at nozzle.
Consumables was new and speed getting low because i guess is small part??
I will check to set higher accelerations and see.
Accelerations is best to be the same on X-Y axis or not matter?

Thanks a lot