Advanced Search

I have recently upgraded both my lathes from 2.8.4 and parallel ports to 2.9.8 and MESA cards
All is running well over the last 6 to 8 weeks and is all stable
However I loaded up a Gcode that I wrote some years ago today and linuxcnc was throwing an error related to the G02 / G03 lines stating that the arc would not meet up or words to that effect

Checking the G03 line all seemed correct, I work in Diameter mode G07 and metric units, the previous X and Z position where correct and a radius of 0.6mm was called for, the finished X was start X + Rx2 and the finished Z was start Z - R
As stated already this Gcode had been written some years ago and used many times without issue

I have amongst others G07 set in the INI files, and as such I do not normall include G07 in my Gcode files (I had always assumed that the INI files would set the machine to G07 and therefore setting G07 in every Gcode was not necessary, I do the same with metric units and never set G21 in my Gcode files as it is set in the INI file)

Running the Gcode all went well appart from the nag message about the ARC but other than that the Gcode ran and produced the correct component, Howerver the graphic on screen display was NOT correct, the white lines (tool path) where drawn at twice the distance from the centre line. When the Gcode was executed the red lines where drawn in the correct place which was NOT over the top of the white lines)
The digital readout on screen was all displayed in Dia mode having the black background and Radius mode the green background
When the Gcode was started the on screen display was moved to show the origin position, this could be moved to show the component being machined.

I found that adding G07 to the start of the Gcode fixed the display problem and the nag message about the ARC
My assumption is that the on screen display is generated from the Gcode file but is NOT utilising the G07 from the INI file
The machine interpeter is using the G07 from the INI files and set the machine to Dia mode and correctly machines the component.

As stated previous versions, at least 2.8.4, did not work like this, and if I'm honest this feels like a bug in 2.9.8
There is a work around to add the G07 to each and every Gcode file but in my eyes this should not be required as it is already set to G07 in the INI file

lower left hand bottom corner of Gmoccapy screen shows active G code and G7 is there even without the G07 in the Gcode
its very repeatable, remove the G07 from the Gcode and save the Gcode and the ARC error message is displayed, add the G07 to the Gcode and save the file and no ARC message
MY lathe is a slant bed, tooling on the back of the machines just in case that could be relavent

Whats your thoughts 

 

Nice!

I did get PIO working and made a pull request . I hadn't announced it yet because I want to stress the heck out of it, and I just ordered a PCB that will form a hardware test harness for it. It seems like it will work well, but I want to make sure that when six axes are chugging along full speed, the scheduling doesn't slip or lock up.

It theoretically should be capable of 200KHz stepping, but again, I haven't stressed it yet.

I bought the WIZNet RP2350 board as well. One of my pull requests should in fact work on it, but I haven't tried it.   I'll check out this code soon!

Hey @scotta , any chance we can get some of the other PRs merged?  They are starting to stack.  #12, #14, #15, and #17 should all be good to merge, and #11 could be closed if #15 is merged.  (The forum won't let me link the PRs.)

a usefull commandline to check changes in hal

You can read the values for any of these controls, except for the jog speed control.

I just ordered two Mesa 7I76EUs, two Mesa THCAD2s, two Hp elitedesk 800 G1 USDT with i5 2.9ghz 16gb ram 512gb ssd, and two cat 8 ethernet cables. So I really want to keep trying until I have a working system. This is my third attempt at trying to achieve a working plasma table and so far I have only got to use my machine for five minutes at a time at most. I really appreciate the amazing support from you all

i am full speed ahead on the dell optiplex 5050...i will mess with the Asus later, probably with a different machine, Right now, I just need this thing to be operational to boost morale a bit

I am thinking ill probably get another 7i77 because i already have a 6i25 and I am eyeing up a fadal VMC40

Hi guys, I'd like to know how to read the value of the jog speed component as shown in the attached image.   

Muecke wrote:

Hi Rodw, 

Your link to the page is gone. 

Wasn't me. Search for @MrRodW on youtube

Hi all

I have found a Kollmorgen servo drive with ethercat that seems to match my requirements, the part number is AKD-P00606-NBEC-0051. But I am not able to find any info on the option code -0051, anyone knows?

@andrax,

Thank you for posting the A6 encoder and homing information - very helpful.

If you don't mind, I have a few questions directly related to your post:

• Step 6 - I assume you mean trigger the drive's internal homing routine, yes?
  • If so, what homing method (of the 33 available) did you select?
    • Reviewing your HAL file, it appears you have a home switch connected to one of the drive's built-in input pins - is that what you used to home the servo?
    • How did you trigger the drive's homing routine?
  • If not, can you clarify "perform a reference run"
• Step 7 - do you mean adjust HAL and INI files as you've described in your post, or some other adjustment?
  • Maybe once the servo is homed, you calculate the joint/axis max & min limits and put that in the INI file?
• XML file - can you post your xml file please?
  • That would help me, and perhaps others, understand the various lcec pins in your HAL file

Again, thanks very much for assisting the LCNC community.

Hi Rodw, 

Your link to the page is gone. 

Cool,
When you go shopping, look for Intel NIC's if you can.
The translation I was referring to was my tuner.
We have only ever spoken English here so I don't know anything about how translation works in Linux.

When you install my ISO it does ask you to select a language for the Debian Operating System.
It also installs the LinuxCNC documents in several languages. I thought Linuxcnc would follow your language.

I also have a motor design spreadsheet on my website too but it won't do the C axis.


 

Oh, that sounds great! 
I still have a PC sitting in the basement; I'll use that for this. First, I'll get two network cards and install them. 
1 x Internet, 1 x EtherCAT, 1 x Mesa Card.

Then I'll install your ISO. 

> I can probably add German as a language now the framework is there.
What do you mean by that? Do you mean German for Linux, for the installation, or for LinuxCNC?
Having a German language option in Linux would be great for me; I'll let the translator handle the English. 


> I guess it could be made to do that but it never made sense to use both at the same time to me.
I wouldn't prefer that either. My problem is: My machine was built with stepper motors, and I don't know the actual torque required. 
That's why I've now purchased this A6 750 W AC servo.
I want to replace just one stepper motor at a time with this servo and check what torque is actually required. 
Once I know all the torque values for my machine’s X, Y, Z, and C axes, I’ll buy the appropriate servo motors and convert everything to EtherCAT servo AC. 
 

Yes its a complete system.
The optimisation/tuning for a NIC for a Mesa card is the essentially the same as ethercat, just different installation steps.

It installs Ethercat, optimised the NIC for it and configures it to use the optimised NIC.
Yes it will configure a NIC for Mesa with the 10.10.10.1 Ethernet IP address on the assumption that the Mesa card is on 10.10.10.10
I'm not sure if Mesa and Ethercat could be used together. It was never intended to do that. I guess it could be made to do that but it never made sense to use both at the same time to me.

These are the new commands I've added recently from the --help page
I can probably add German as a language now the framework is there.

Note some tuning functions are not preserved on a reboot so the --autostart function installs a service to run the tuner again in a passive mode to set them on startup.

+1
Also wish to have option to remove G54 on M2/M30
Thanks