Advanced Search

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

 

Hi can someone help me with the spindle. I have it working on a basic level 0-10v through a VFD, but want to add the encoder. I'm getting confused with the PRUencoder and linuxcnc encoder. I have no spindle speed displayed. I think I need to add the phaseZ pulse somewhere. Pv and raw count is counting in both directions. I have no index enable , is this a physical output pin connected to something? phaseZ is coming in on remora.input.13.

blazini36 wrote:

Oh and is there any way to use a progress bar for something like spindle speed feedback? I don't see progressbar in the docs
 

I've added a QProgressBar to monitor the HAL pin you give it.

gnipsel.com/linuxcnc/flexgui/hal.html#progress-bar

No time left this morning for a video...

JT

we found the lathe backplot error and the fix is on the latest develop version push, if you are on the develop version and run an update, should resolve. if on the stable version a new release will be coming today or tomorrow which will resolve on the new and updated stable branch.

happy to help!

will have a look! thank you for bringing to our attention!

I would recommend to only use the latest versions for fixes are pushed regularly now on them and the methods used to pass variables will work in all circumstances of call, for example in remap the parameters from the ui were not accessible, the later versions used the var file which makes them available in remap also.