Advanced Search

Thank you for all he help you are providing to members of this forum, i do not think the "thank you" button does justice for everything you do here.
Danke schon.

M4MazakUser wrote:

The machine I have went thru a flood - it was 4 metres underwater- about 4 and a bit washing machines in American speak.

LOL
Nice one, thank you.

digiex_chris wrote:

The riocore generator seems to be generating a linuxcnc config and hal file entries for servo drives when I'm using steppers in my config. I've got PID params and other things specific to servos appearing in my rio.ini. Is this intended?

It is for Mesa hardware, so might also be for this.

Yeah, I just wanted to read the value of "L" it would be great if I could display it in a pyvcp panel. This is on a barfeed machine. 

I generally measure on setup and restart at the m00, of course after setting g52 to z0 in mdi. The following pic is the problem.

When I do a program restart (run from here) halfway through the program it looses the g61 command and radiuses everything shouldn't g61 be modal?

Boy I've got a lot better at tuning my 8i20 cards though!

After much stuffing around. I believe I found the problem.
The machine I have went thru a flood - it was 4 metres underwater- about 4 and a bit washing machines in American speak.
There's a rust mark in each ballscrew where it was parked. It plays up rapiding in these areas

Hallo zusammen!
Endlich läuft meine Maschine (prinzipiell), die Motoren bewegen die Achsen, jetzt geht es nach weiterer Pause an die Feinheiten. Hier und da geht das Homing nicht richtig, vor allem stehe ich aber ständig an den Endschaltern und muss mehrere Klicks machen, um wieder davon wegzufahren. Gibt es eine Möglichkeit in QT Dragon, das Keyboard Mapping so zu ändern dass eine beliebige Funktionstaste das override limits machen kann? DAS wäre toll, ich habe aber darüber noch nichts gefunden. (Ja, ich habe das Manual zu QT Dragon gelesen, da steht nur was da standardmäßig vorgesehen ist, nichts über Erstellen eigener Buttons).
Ich fürchte ja, das erfordert Python Kenntnisse die ich nicht habe. Die Python Dateien die in der Config vorhanden sind sind kompiliert, da kann man nichts dran stricken.

Vielen Dank für jegliche Idee dazu!
Arno
 

The riocore generator seems to be generating a linuxcnc config and hal file entries for servo drives when I'm using steppers in my config. I've got PID params and other things specific to servos appearing in my rio.ini. Is this intended? I'm just using the default config for the IceShield for now.

in the appendix my servostar profibus attempt.
Btw, here are details of my setup:
Servostar 603, Firmware 5.76, HW version 49.01
AKM31E Servomotor

Hello endian,
great, in the end I found somebody who is brave enough to work on the kollmorgen servos! Awesome!
In the appendix, you can find a tarball of my current version. As I said, the drive is somehow communicating with lcnc, but I do have terrible timing issues.

In a nutshell, what I did or tried to do:

set up the EL 6731 using twincat3

• PDOs for parameter channel and process data
• cycle time 1ms
• use of Ethercat MDP Mapping and upload the config to the EL6731, hence no init commands or startup sdos in ethercat.xml on lcnc side necessary (Not sure here)
• not sure about settings for Distributed Clocks (just left it default, at the moment)

lcnc comp

• use parameter channel to set operation mode <--- velocity
• byte swapping magic (not sure If I got that right)
• scaling the velocity and position feedback (not sure about the scaling numbers, docu is a mess, as you probably know

lcnc ini/hal

• try to use a simple PID loop: position command (from motion, setpoint) position-feedback (from servostar. Here I do have the issue -- due to comm problems this data is very laggy, hence the PID cannot do its job) PID output == velocity command to servostar

Here are my issues / todos

• I'm not sure if I correctly use the parameter channel of profibus (PKW) Due to lack of understanding of SDOs, I simply put the PKW as an PDO and initialize the drive on startup -- IMHO it would be better to do that via SDO or some other hard-coded init sequence I'm not aware of. Maybe the constantly send/rec of the parameter channel causes the timing issues.
• I need to parameterize the velocity profile for the position loop. Where to do that? Drive GUI?
• Homing: I think of simply use the built-in homing method of lcnc, the implementation in the hal comp seems to be a bigger time effort. Here a question, in case the homing switch is reached (digital I/O of another EL card) how to set the position feedback of the kollmorgen servo to zero.
• Enable the drive is working, disable is buggy -- need to correct this

Sorry for the lengthy message, but maybe you have some hints on one of the issues. I'll definitly take a look at the other thread and your provided info. Thanks again!

BR Franz

this is canopen for sew lteb vfd which should be workable for non rigid tapping purposes ... I running them 18k low cost spindle just for researching

please post your .ini file

I have done profibus interface too... homing is waiting too but it is not yet tested well because of time .... profibus interface will be same for each of kollrmogen product ... as well as s400, s600, s300 and s700 ... defenetly share your code if it is possible ... I will share them when I will on my second laptop

here is thread where is all necessary stuff for ds402.comp for ethercat interface .. homing will be same in profibus and here in the ethercat .. but with profibus it is more fun with byte swaping for motorolas cpus ... and for ds402.comp is homing and all other functions are working for hw 04.00 and fw 5.13 and higher 

regards