Advanced Search

RotarySMP wrote:

I updated my lathe to 2.9.8 on Trixie with RTAI.

I read that and thought "RTAI, resolution issues....", but nooo, you had to find something i have never seen, and it irrevocably seems a GmoccaPy issue.
This keeps reminding me of an American saying: never change a wining horse.
I am i am not helping.

RotarySMP wrote:

I got the Schaublin updated to Trixie and 2.9.8.

I really like the update you did to the look and button layout of Lathe macros. Thanks.

 

Be a bit careful with them, I found a bug with my system (which uses Touchy, so may be different). 
Pressing the hardware "go" button was running the lathe macro even when the MDI window or Auto (G-code) window were at the front. 
This might not happen with Gmoccapy. 
It was previously prevented by code in the GUI telling the Glade panel when it had focus, but the signalling method used is't available in GTK3. 

Also, the problem went away after a restart, so I haven't been able to work out the cause. 

I may be the only one using the macros with Touchy...

@Don,
Do those replies belong on this topic, or am i missing something?

I think you are on the right track.

Single-phase to the machine, and use 220vac step/dir drives and a 220 vac single-phase-in, 3-phase-out VFD for your spindle.

Based on some low-cost (maybe Stepperonline A6) servo specs, you've probably got enough power budget to realistically drive 4/ea 1kw servos (XYYZ), a couple of 750w servos (A&C), plus a 4-6kw VFD for a decent ATC spindle.

If you want a big vacuum for hold-down or dust collection, you might need to put that on a separate circuit.

I'd recommend planning on using timer relays (hardware or software-driven) for the drive and VFD main contactors.  Cheaper drives (and some expensive ones, too) don't have great inrush-limiting features and turning everything all on at once can strain (or overload) the supply circuit.  If you break up the inrush over 2-3 'stages' with some on-delay timers it'll be a lot more gentle.

Clear the estop and you'll hear clunk...clunk...clunk... over a few seconds before everything is ready.

Hi, my bad i did not mean COM but parallel port (must be a habit from my Arduino days). I did try to put the encoders on the second par port (parport 1) and for some reason it works now (parport 0 = stepper outputs, parport1 = encoder inputs). No idea why, i don´t think it is grounding related though.
As for the encoders: They are linear scales (5µm), my math was 5000 to 10000PPS * 0.005mm * 60 = 1500 to 3000 mm/min. The spindle has a 400PPR Encoder and max spindle speed is 3000rpm.
I still have to get the inputs on parport0 working to read the spindle encoder. Tomorrow i can send pics of the wiring.

Hi Guys,

I updated my lathe to 2.9.8 on Trixie with Preemt-RT. Now Gmoccapy appears to have a bug causing it to scale up each time you exit the tool table or the max preview. window size setting also doesn't work correctly, as the screen reduces in height when commanded to increase in either width or height.

I made a video to show the behavior. 


Like this, the lathe is nearly unusable, as I have to keep shutting down and restarting LinuxCNC to reset it. Any suggestions how to correct this greatly appreciated.
Cheers,
Mark

Thanks for that, I was not able to get into the forum for the last couple of days.

I had similar advice from AI, and tried both the solution yours and mine gave and it has not corrected it.

I even used visual code studio, and rewrote the whole program be hand, to ensure there were no secret character codes in there. (See attached file)But the result is still the same.
hal:turret:1: character unknown '  '

Any other suggestions much appreciated. 
Cheers,
Mark

spumco wrote:

Before you make any decisions, you've got to sort out power
 

THat's what I did today:
The VFD takes 480V directly from source (I am going to replace VFD and spindle, so it doesn't matter).
A 480V single phase line powers the DC bus which in turn supplies power to all 4 drives.
The transformer ties two of the lines into a neutral-ground, and outputs 120V to power the controller and peripherals. I replaced this with 120V AC to test if the controllers are working. Was told by seller that it takes a while to boot. It's abootin as I write this.

The servos are all 140V 65amp max. I do not need the maximum capacity (I am carving wood, and I am doing low throughput. I was thinking to sell the drives (they are out of production and I imagine someone who is running this machine in a production setting would want parts) and replace them with step/dir ones as someone else had recommended. The VFD takes 3 phase power at 360 to 480. I was wondering if I could just supply 220V power 3 phase to the VFD and have it power a 220V 3 phase spindle. This would make the work a lot easier, or just replace it with a single phase 220V VFD to power a 4ish HP spindle. That would work too. Either way, I really don't see why I should stick to 480V single phase since the part that is drawing power is the spindle which I really do not need.

placeholder

Aciera wrote:

What would be needed here is to have the _interpreter_ reject the axis word which was disabled. 

So the NML description in the LCNC manual isn't accurate? Or perhaps not exactly clear what happens?

I would have thought 'turns off all the calculations..." would have removed that joint/axis from the TP calcs entirely.  

On second thought it probably wont work like that  I can't have "v" defined in case-0 as well as an 'unused coordinate.'

But maybe there's a way to define the motion math of case 1  pos->v= j[0]; so that no motion results regardless of input.
 

I wonder if this could be done through the switchkins component.

Do you think LCNC would throw an error if I just left joint-0 out while operating under Case 1? 

Instead of this:
Maybe this:
And do something similar for the inverse later in the comp.

​​​​​​​

What would be needed here is to have the _interpreter_ reject the axis word which was disabled. So just like if the operator used an axis letter that was not configured in the ini file. Any MDI or gcode program line containing the disable axis letter would create an error 'Bad character x used'.

Unfortunately I do not know how to dynamically pass the disabled axes to the interpreter during runtime.

Not sure if there is an easier way of trying this but I inserted the the actions of 'EMCMOT_JOINT_ACTIVATE' / 'EMCMOT_JOINT_DEACTIVATE' (ie set/reset 'SET_JOINT_ACTIVE_FLAG' for a specific joint :
 

into 'EMCMOT_SPINDLE_ON' / 'EMCMOT_SPINDLE_OFF':

 
 


Which lets me clear 'joint.1.active' using the spindle control but it does basically the same as disabling the drive as 'joint.1.pos-cmd' is still updated as the axis is jogged or commanded through the interpreter:

 

The problem with the following error when reactivating the joint remains the same as if it was done in hal or the drive disabled. 
 

After you set it the first time, does it disappear from the sdos listing or does it just become read-only?