Advanced Search

Thanks for that answer...  however... it still is unanswered in my original post I did this:

"G0 Z#<_ini[TOOLSETTER]z_tool>

It errors and says that the variable doesn't exist.  Hmmm...   so I tried doing ..

#<_ini[TOOLSETTER]z_tool> = -1.25

It took that without issue...  I then executed 

G0 Z#<_ini[TOOLSETTER]z_tool>

and now it works.  hmmm..  What am I doing wrong?  It is supposed to have a variable defined during ini time... but it isn't, at least that is what I am seeing."


So, it is ok to generate a variable of the form  _ini[TOOLSETTER]z_tool ?  That started my path down this thread.  If all _ini variables are READ ONLY, then why did it all me creating and setting the variable like I did in the first example?  It should have errored out and give me some message like "ini variables cannot be dynamically declared"  or something like that.

I thank you for finding the documentation on the proper usage of the ini variables..
 

I can not find it, cr@p, having stuff scattered over 2 NAS and several USB's and 4 laptops does not help.
The PC that had the config is gone, it was with the 2.9 version from the Debian repositories.
I think the 2.10 does not have this issue, i think i made a new QtPlasmaC config on a Lenovo laptop that just worked. OK i just checked this, it is an existing PlasmaC config converted to Qt and it worked properly.
-
RNJFAB, can you try editing the config and choosing something else for e-stop? There are 3 types.
And what type did you choose on this config?

Lcvette wrote:

2.9.3 works rock solid

I also switched to PB develop vers... any reason I can't just switch LCNC from 2.10 to 2.9.3?

unterscheiden sich die Handräder je nach Händler oder sind die mehr oder weniger gleichwertig? Die nächste Frage wäre ist Funk okay oder besser die Kabel Variante? 

Vielen Dank und einen schönen Feiertag
Erwin

Hi,

I did everything in the twincat 3 from the beginning... All stuff have to be visible and workable via local PDO setup... then I active configuration on the local PC with right scan time... for us should be a 1ms which U have to define in the PLC tasks...then rebuild them and active configuration but you have to upload PDOs configuration in the Process datas section... if is everything green means OK and you should disconnect it from the Twincat3 PC and plug it to the debian ethercat master rj45 socket.... then command
and you have to see active configuration in the EL6751 master ...

take care about the shape of the PDOs because they are different from the shape of twinCAT3 PDO configuration then you have to export startup in the Startup section .. export them to excel as .csv and then copy paste it in to the ethercat-conf.xml file with "complete" config definition just copy paste them in front of SM managers and if you have luck and no syntax issues you made everything should work from first shot... I do not experiment with different setup and legacy setup, it is there because of very old stuff which should use little bit different shape of communication datas or protocol..check files in the attachements for a hint 

if nothing helps you should run commandwhich will create you a working PDOs config of your acual stuff in the el6xxx master

I will check your file tomorrow because I am currently busy with my configuration too..

regards...

Murphy, here is how I have done my spindle

github.com/cakeslob/RRW_LAB/blob/main/Li...t/remora-xyz.hal#L95

lost wrote:

I reckon the transistor was a pretty good invention, yeah an improvement on what the vacuum tube does, but a new way of doing it.

Shame on me, i forgot that!

vre wrote:

How can i switch parallel to input mode?

loadrt hal_parport cfg="0x378 out"
to
loadrt hal_parport cfg="0x378 in"

You just specify input on the hal command line that instantiates the driver (hal_parport or rtapi_parport), and it will export the needed hal pins.
Jon

I made some progress since yesterday but currently it is not working.

• countless tries editing the initcmd file to get EL6751 up and running did not succeed i ended up with dmesg output "invalid input configuration" but i have no idea how to debug/fix the wrong config (Preop).
• switching the ethernet cable on the fly from twincat to lcnc lead to OP-State (only PDOs are configured in lcnc, no initcmds or SDOs).
  • with "ethercat pdos" i can see the list of PDO entrys configured in twincat.
  • but some parameters like baudrate are set to 500 kbit/s instead of 1Mbit/s
  • changing only the baudrate parameter with initcmds sends EL6751 to Preop.

Does anyone know how to store the parameters from twincat in the backupstorage of EL6751 to avoid using the initcmds?
I thought the button in the screenshot does this but after power up the unit has a totaly different konfiguration.

Thanks you in advance.

pncconf can set this up, though you may need to swap A/B to get the spindle direction correct

Well using 24V power might resolve the MPG use permanently with fire and smoke if it's a 5V MPG (most are)

Did you check the input levels? If the A/B high levels are less than say 3.5V, a pullup resistor to 5V may be needed

yeah that would require a major bit of changes and components. is there a reason it couldn't use the 24v field supply for the mpg vcc/gnd instead of 5v? wold that resolve if it was a low voltage issue?

that would work too, but be sure you are only using a text editor. the safer way would be to use qtdesigner for most folks i think less chance of breaking something from an unforced error or typo... i do that sometimes...lol  

shipmodeller wrote:

3: So that begs another question...  is there any script that can be configured to run on initialization of LinuxCNC so we can create variables and set them to certain values? I don't remember reading anything like that in the manual.   It would be nice if the ini section had an entry for that.I can't really mark this solved, because of the remarks I made here. Yes, I have a better understanding now.. IF I am correct in my assumptions.  But it has led to some confusion, and days wasted troubleshooting this.  ( I have been programming since 1967, long retired now. )

[code][b][b][b][code][b][color=#3498db]Thanks for reading this.
 [/color][/b]

[/code][/code][/b][/b][/b]
 

In Flex GUI you can have spin boxes to set hal values
gnipsel.com/linuxcnc/flexgui/hal.html#spinbox


or you can set user numbered parameters from the GUI and use them in your NC code
gnipsel.com/linuxcnc/flexgui/parameters.html


JT