Advanced Search

Thank you but if you have a system adapted for the standard BCL-AMP and you measure frequency, my device is not adapted for this.

The output signal of my converter is an analog signal 0-10V or digital serial transmission (USART).

Yes now I see it I made a mistake, my English is very poor and the automatic translator also does not quite convey the meaning of the sentence.
Thank you.
I have one more question in the case of the spindle speed slider I have strange values depending on the last selection in the MDI panel even though I have them defined ini.

Ich habe nun einen Ecoder mit 10000 Impulsen pro 90 Grad an die Achse angebaut. Dann habe ich die Achse versucht mit PID Regelung zum laufen zu bringen. Das Ergebnis ist enttäuschend. Ich bekomme die Achse nur ruhig ohne zittern wenn sie sich in Zeitlupe bewegt. Die Achse ist am Ende zwischen ca. -70 und -90 Grad und -20 und 0 Grad total unruhig. Einzig im Bereich zwischen -20 und -70 Grad ist sie halbwegs ruhig. Damit ist leider keine halbwegs vernünftige Bearbeitung möglich. Die Linear-Spindel wird ja durch 34er Stepper mit angebauten Encoder an einem HSS86 Treiber (Closed-Loop) angetrieben. Die B-Achse sieht man im ersten Beitrag hier im Thread.
Nun habe ich eine vielleicht dumme Frage:
Kann man die Achse in open Loop laufen lassen? Also nur gesteuert und nicht geregelt.
Vielleicht kann man ja mit dem Encodersignal irgendwie den Stepgenerator ansteuern?
Ich komme da leider nicht weiter. Hat jemand hier irgend einen Vorschlag?
fragt Peter


 

If you get stuck, I am in Australia and have a 500W laser head I need to buy a BCL-AMP for.

Good so far.
lcec_configgen reads the info from the ELMO drives and formats it in a suitable way.
You can read out the info yourself with "ethercat -p 0 sdos", "ethercat -p 0 pdos" and "ethercat -p 0 -v slaves"

For the error you have, was kind of expected. No easy way I know off to know the halpin names of a built-in device like the basic_cia402.
But you can find out with this series of commands (linuxcnc not started)From that output you should be able to find something that resembles cia-statusword (index 0x6041). Do the same for the other missing variables.
So with that info, you replace lcec.0.0.cia-statusword with whatever the output above says for 0x6041.

One can also look up the index of interest, any places but here are two basic ones
doc-legacy.synapticon.com/software/44/ob...pdo/rxpdo/index.html
doc-legacy.synapticon.com/software/44/ob...pdo/txpdo/index.html
You will probably need that for the other halpins, I guess they will give the same type of error.

Ideally your g-code should be designed and generated in a fashion that the tool is actually capable of achieving the programed feed rates. It isn't really a good practice to program code to execute at say F200 but the moves will only allow F40 and then expect to rely on that F40 as your feed.

Right now since the machine is trying to cut at the higher feed in the slow sections but "can't". When you slow the machine with the feed override, the slow sections will not slow down until the feed override percentage lowers the programmed feed rate below the actual capabilities of the machines parameter settings for those sections of code. So if the programmed feed is F200 but the machine can only reach F40 in a section, you would not see a reduction in feed in the slow section until the feed override is set below 20%.

If you were to insert realistic feed rates for the "slow" sections of code. Then the feed override should give you the results you are wanting.

Other things to do to improve this would be to increase the machine's acceleration capabilities in order to reduce affect of slowdowns caused by short moves. Run the code using G64 mode with more optimal blending settings (larger P and or Q tolerances.). Improve G-code optimization by using curves instead of approximating them with short line segments, increasing code segment lengths and making segments more co-linear (less corners). Really any thing you can do to make so the machine moves at the actual programmed g-code feed rate rather than at the limits imposed by the configuration settings/physical limitations.

The new edits will allow shift once fully tested.

As for key binding, that is inside linuxcnc, there is a blurb on it in the docs I think, but don't recall where and not sure if it would be connected to PB or not. You would be on your own there

Thanks for the reply again Hakan,
I have been trying numerous files from different cia402 examples, and im having a hard time understanding what is what. for example, my `lcec_configgen` output seems a bit disjointed. for example it seems to show some drives as "generic" and some as "basic_cia402", but they are indeed all the same make and model of drive. How does `lcec_configgen` generate this information? Is the a basic .hal, .xml & .ini available that has only the bare minimum to establish a connection? I have made the suggested changes and now have an error at "lcec.0.0.cia-statusword".

Thanks again for your patience

Steve Cap

Yes, that label with all the specifications is great!

Yes I have your config. It's also for CSS? I have the cycles add on installed. When I try and turn something. It starts the tool change , and starts the spindle but then nothing. Id image it's waiting for spindle index enable.

When I set spindle.index-enable to true in halshow it's says parameter or pin not found 
Trying to set any of the others like spindle-encoder.index-enable etc says it's already connected to a signal 

JT

noqui wrote:

Hi. 1) How did you started your Flexible GUI? Just modifying the AXIS.GUI (don't know where it is), or creating a new one? And 2) how do you compile it then with linuxcnc? Thanks a lot.
 

You can start with a blank slate or start with one of the examples. You don't have to compile anything.
The documents are at gnipsel.com/linuxcnc/flexgui/index.html
The videos are at www.youtube.com/playlist?list=PLzYeNVt90...AsRGVDCtpW9_7ZXiSTak

JT


 

I wonder if this could be related to the order of how the components are added in hal. I've just had a somewhat similar issue with my own encoder disconnect component and I moved the addf of my component up above 'motion-...' and it worked fine.

so maybe try to change this


to this order

I just tried it and it works like this.

Because of my keyboard layout (mini keyboard) is it possible to change the "+" key to the shift key?

Another question that has been on my mind for some time is: Can keyboard keys be assigned to change the different increments (5mm - 1mm - 0.5mm etc...?

spindle enable is something that gets turned on and off when you are about to do a tapping operation or something. when spindle-index is high, when it rotates and sees the index pin, the index enable will go low and one of the spindle counts resets. if you are using the hal file from me, its already connected to what it should be. you can turn the index enable pin on in halshow, and when you rotate the spindle you should see it turn off when you hit the index