Advanced Search

MDI_COMMAND = O <safe-go-home>         CALL

I don't know if this is it, but if that's a copy-paste from your INI file it looks like there's a space between "O" and "<safe-go-home>"

So I'd check if there's a space, as well as double-checking the subroutine path in INI file.

EDIT: Aciera beat me to it.  Again.

Doesn't sound like a problem with your pyvcp panel but rather with your subroutine path.
Have you tried running this in the MDI command input:If that gives you the same error, which I would expect, then check that you have placed the file 'save-go-home.ngc' in a directory listed in PROGRAM_PREFIX or SUBROUTINE_PATH in your INI file.

mBender wrote:

Awesome. I will test it with my oscilloscope. I wonder if I need something like a pull down resistor after/before the level shifter.

I noticed that the one of my outputs is not always switching. It's tied to the "machine on" but when I toggle the machine on an off, sometimes it's not reacting. I also get some error messages in the Terminal.

This is my current wiring.
 

Just a thought, try setting the feed rate very very low, and maybe with a low scale factor. I noticed on my board (based on rio-iceshield but with slightly different parts and design), after about 2khz, the output signal no longer falls near zero and I get a strange offset sawtooth on the oscilloscope. Around 1.6khz I get nearly a sine wave, but with a flat bottom. Under 1khz I get a nice square wave. So I think I have some capacitance issues or the line driver isn't fast enough. Still digging into it. the ULN2803A I used looks like it's fast enough based on the datasheet but who knows!

What error messages? I had to tune FERROR and MIN_FERROR a bit for my setup to solve some following errors.

I have built over 40 pyvcp panels in my life... and I have a button that runs a simple routine to safely go home.
Lift the Z, move to the XY, lower the Z. Simple... here is the code.

O<safe-go-home> sub
G90 G20        
M5         
M9          
G53 G0 Z 0
G0 X0 Y0
G0 Z0         
O<safe-go-home> endsub

The panel has a button with a halpin: safe-go-home

And the custom_postgui.hal has

net panel-safe-go-home  <= halui.mdi-command-00  <= pyvcp.safe-go-home

And lastly, the INI has...

[HALUI]
# add halui MDI commands here (max 64)
MDI_COMMAND = O <safe-go-home>         CALL

All the components I've used like 40 times before.

Now... on this machine... I'm getting...

EOF in file:/usr/share/axis/images/axis.ngc seeking o-word o<safe-go-home> from line 0

What the heck?

Did you try pinning the IRQ?

This script can be used for testing:

 

chmod +x pinirq.txt

then

./pinirq.txt [ethernet_device_name]

My home desktop (a HP EliteDesk G1) needs this
its running  6.11.0-rc3-rt3

Note that Debian RT kernels tend to be terrible
 

I tried searching for a repository of the kernel to see if i could dig through and see what changes were made but its very difficult, it looks like kernel.org was the most informative but i still could not find an actual repository with a history tree to hunt through.  anyone that could direct me to the spot to start digging?

Have you tried importing the rt git project into a git client (eg gitKraken) and then compare 2 branches?
git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git

Will try soon, due to a stupid design of the computer box and that I was too eager in my screwing in the computer, a plastic thing on the hard disc broke.
 
Right now, the computer does not want to know about the hard disc.

Thanks for all the help so far.

PhillC54.
This is an interesting aproach, basically we are muxing the THCAD input, may be some processing power can be saved using only one encoder.
I re-draw your schematic just to make it more readable, I think this will require some changes to PlasmaC componet.
 

Danil wrote:

Or please share a similar code, I would be very grateful

Try searching the forum.  I suggest limiting the search to 'title' only, and go back longer than a year.  Research the numerous posts where other folks have worked through various tool changer problems and see if what they discussed is similar to your situation.

The first problem with your request is that logic for tool changers is very hardware-specific; only you know what hardware you have and how LCNC can control it.

Second problem is that there are many different ways (in software) to control a tool changer.  G-code subroutines, Classic Ladder (i.e. PLC), python + hal via the GUI, and probably others.  As with your hardware, only you know which control scheme is the 'best' for your situation.

Thanks that did the trick.

PCW wrote:

It's not a issue with Intel MACs
If you disable IRQ coalescing
and pin IRQs, You get pretty decent
performance.

For example on this HP8300 I have been running a test on a 7I76EU
with a 3 KHz servo thread for about 3 days while using the PC for general
web browsing, email etc and have not had any issues.
(CPU frequency is 2.9 GHz and times are in CPU clocks)


 

 

I am getting latency with an intel adapter on just about every image release after 6.1.0-13 for some reason. so it seems something got worse after that point in time.  I can repeatably return to the above image and no more delays.  i do check whenever a new release comes out to see if that changes but so far it does not.  im not certain what the difference might be but it seems maybe it could be identified with a narrowed down image update timeline.  I tried searching

not sure if that is helpful, 6.1.0-13 is no where near as good as the 4.9 stretch version was latency wise but it at least did not throw warnings.  

I tried searching for a repository of the kernel to see if i could dig through and see what changes were made but its very difficult, it looks like kernel.org was the most informative but i still could not find an actual repository with a history tree to hunt through.  anyone that could direct me to the spot to start digging?

Chris

Try

I'm afraid jumping between different configs is not going to make things easier. Either follow Rods method or Marcoreps then post your hal and ini files and make a screenshot of the relevant hal pins from the 'show halconfiguration' tool (those will be different depending on which method you chose).

I would like to know what steps to take to have qtplasmac gui to work with ethercat
not trying to be lazy, just trying to avoid another 3 months delay because I could not get my ECR86 drivers to work.
rtelligent service actually helped me out and I finally had the axis moving...
I took notes of everything and I will post my findings here ...

THANKS TO ALL WHO SPEND TIME HELPING OTHERS!