Advanced Search

hi there,

I have a long talk with gentelmen from the beckhoff which are talking that 2ms is for them limit of RT control ... I am experimenting with the 7 axis over profibus and there is latency 1336us, but I have not tested them ever... I have setted them to 2ms 

I think for 3 o 4 axis it should be less then 1ms in the optimalized profibus cycle with equidistant mode active... I am running old metronix servopacks over speed loop... Everything works well even homing procedure but I think it is not for extremly precise machines probably I will facing the limits in the future but that servopacks was for 40bugs at locat market place

I have configure CanOpen, profibus, profinet over ethercat too but profinet have terrible delay 4ms which are not enough for anything ... or use the IRT profinet with 31.25us latency(there is limitation of 5 or 6 device on the network) but you will need special interface from continental which is only dealer of them

My machine is running at mesa 7i77 + linear scales, next running kollmorgen packs at 250us + linear scales, next nidec stuff too at 250us{not all stuff integrated as driver build in probing} and now I am experimenting with profibus ... 

S120 is profi solution on 31.25us drivecliQ bus but it is soo soo expensive ... EtherCAT should runs at 62.5us but need native stuff and I have never tested them that fast... probably there will be limitations of lcnc latency hw itself

regards 

I see.

I suppose this is a low-speed spindle?

(not 10000RPM)

I am in North Carolina in the USA, you are thinking of Joco in NZ..lol

yes you want to use the geneva pin for the pocket index so its in the locked position. for homing, you could configure it a few ways, but typically i would use the home switch + the index switch so when homed it will be in the locked position of pocket #1. I was planning on using the same dumb motor step generator so please let me know how it works out for you. here is how my home/index is setup on my little atc build:

 

yes because of all the confusion previously of how to calculate it I made it specific to the subroutine used to set it. not sure if I can make it both manually enterable and via subroutine easily or not. will have to take a look when i have some time again. I have been a bit covered up recently but hope in the next week or two to have some more time to work on the ui.

It is a issue in the component, it happened before where another USB ID for the shuttle was left out of the code and Andypugh fixed the code adding the missing ID. That was 5 years ago. The 011 shuttle ID was not added and is still not provided for in the code even though it is a valid ID for some shuttle pro devices.

Here is where Andy changed the code to add one of the missing USB id's
github.com/LinuxCNC/linuxcnc/issues/702

The shuttle docs list 3 USB codes for use in addding a rule but the 011 code is not mentioned.

For now I connected a shuttlexpress I had and that works fine (its ID is 0020 which is in theShuttle.1 source code)

Do not bother to much with the details for now, assume standard stuff, make some test configs, do some measuring to make sure the axis moves the exact distance as commanded, let it rip!
You can make as many configs as you like for the same machine, you can even edit the scale and some other stuff while LinuxCNC is running and save from there, using the "calibration" from the "machine" menu.
It would help to know the exact screw pitch, so mark the screw and the nut with a sharpie, turn the screw several times, measure, enter that in the wizard.

Google suggests that they are both 1.8 degree (200 steps per revolution) motors, so stepconf's default values should be fine...

Thanks to both of you.Being somewhat impetuous, I put it all together and started tinkering while I waited for advice.... nothing's gone bang. Yet.

Yes: it's a G540. I've just been playing in the workshop and I found the preset for it. Using stepconf, I've been moving the x,y,z and A axes about, like a gleeful child with a new train set!

Sadly, the original computer is now dead and buried. I did keep the hard drive from it, but although I tried connecting it to another Intel motherboard (the original was an Intel dual core) I couldn't get it to boot. Now I think I need to verify the motors. Z and Y use Vexta PK268-02A but the x-axis appears to use an Italian motor HY 200 2232 - 160 88 looks like the model number. I shall have to do some Googling, to find data sheets.

I see a steep learning curve ahead......

Probably a kernel issue, so try installing another RT kernel.
packages.debian.org/search?keywords=linux-image-rt
There are several under the "Package linux-image-rt-amd64" section, try from Trixie and down.
To switch the kernels when powering on/rebooting, hold down the right SHIFT key until the GRUB menu shows up.

Is this the same machine i did reply to with RugBot a while back?
Did you try to find out what he/she is using for CAM? I do recall vaguely mentioning Inkscape somewhere but never checked.
Well id did check now, and it sure does output valid gcode that runs on LinuxCNC without any issues, and changing the scaling in the screenshot does change the angle as it should.
The best thing with Inkscape and GcodeTools is Python, so very easy to edit and modify, i did this for Plasma.

Since you asked for ideas, here i go:
-how hard would it be to run two interpreters and two trajectory planners?
-
-with 2 of 7i94 i would look to have them connected via IDC26 for sure, real time and 1ms or less if faster servo thread is used, given the possibility of Mesa to have all pins as inputs or outputs
-this would also keep everything in hal and with some "creative" components would be much safer than any ModBus or serial.
Just checked, 7i94 has only one IDC26 that in your case is used for 7i77, so reverting back to Smart Serial, and here i have to stop as i have no idea if connecting two 7i94 through SS is possible, but i would venture a guess at yes, but might need some help from the Mesa master: PCW.

HI
Linuxcnc doesn’t support more than one toolpath, for example a lathe with two independent turrets. Typically, this is referred to as a dual path system. 

As seen on other posts on the topic on this forum, it is recommended to use two separate LinuxCNC systems, which is OK Now, I would like to link the two systems and im not sure what would be the best to do this.On the PC side, im planning to set up a local network so that the slave system can load a program written on the master system, so file sharing etc. there should be a lot of info on this on the web… On the linuxcnc side, im running a 7i94 +7i77 on each PC.Typically, I would like to have a link between the two linuxcnc systems so that the one system (master) can interface with some of the HAL data on the other (slave) system.It would be ideal if the master system can read/write hal pins (float and bit). It does not have to be realtime though, but I need it reliableI don’t know what is possible, but I was thinking a serial link from one 7i94 to the other would be the best solution.Is it worth checking out the Mesa Modbus method? Does this seem like a good idea or are there some better options? Your ideas would be much appreciated ThanksHenk

Does the Gecko have G540 written on it?
If not, does it have 4 of DB9 connectors? That would be the G540, so it has a standard pinout and the wizard included with LinuxCNC named StepConf has a pinout for it.
Also do keep in mind that if it turns out to actually be a G540, it has a very strange feature where it does only 1 pulse from 10 pulses on the input, it was labeled as microstepping but it is not, so you do need to add 10 in the wizard for microstepping.
See if you can find a used Dell OptiPlex 980 in the big case, those have a built in parallel port and work nicely with LinuxCNC, usually 30-70$.
You might also need a plain parallel port cable, or old printer cable, sometimes also named centronics.

You need to figure out the pin assignment of the parallel port connector. So the first thing I would try is to get the original Mach3 config file from the old PC. If I remember correctly it's an .xml file in the 'mach3' folder. This should tell you how the signals are arranged on the parallel port connector. This is needed to set up linuxcnc using the 'stepconf' tool.