Advanced Search

Search Results (Searched for: )

  • theoneandonlyoreo
  • theoneandonlyoreo
24 May 2025 20:52
Replied by theoneandonlyoreo on topic problems with Verser Probe Screen 2.9

problems with Verser Probe Screen 2.9

Category: Basic Configuration

That's a good suggestion. I comment out the offending lines and looked around "Show HAL Configuration"

Turns out, probe.* pins don't exist. HOWEVER, gladevcp.* has all the pins that have been implicated, including gladevcp.toolchange-change and gladevcp.ps_probe_max

The Z-height probing routine kicks off a message complaining that probe.ps_probe_max is not available so I thought I'd try to name it at the outset. I tried using EBMED_TAB_COMMAND to adjust the component name with -c probe but that doesn't run.
EMBED_TAB_COMMAND=halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -u psng/python/probe_screen.py -x {XID} psng/probe_screen.glade

I dug around some more and found a line in probe_screen.py that was commented out.
self.halcomp = hal.component( "probe" )
I un-commented it and it may have this particular problem. Makes me nervous because there are other lines nearby that are commented out...

Thanks for the tip, Aciera. Great handle, too.
  • knipknap
  • knipknap
24 May 2025 20:15
Replied by knipknap on topic MESA 7i76E burning out issue

MESA 7i76E burning out issue

Category: Driver Boards

Ah-ha! The 24V field power GND is not connected to earth ground, I was not sure that it should be. That probably explains it then.

Just weird that the machine ran fine for so long.

Thanks, I was getting frustrated with the constantly changing symptoms. I will connect those grounds tomorrow and test again.
  • atrex77
  • atrex77's Avatar
24 May 2025 20:13 - 24 May 2025 20:14

W5100S-EVB-PICO stepgenerator and encoder driver

Category: Driver Boards

The hal driver installation is easy, you need to open terminal navigate to the hal-driver directory and run ./install.sh

Sample hal configuration in the hal-driver/test_config directory
  • atrex77
  • atrex77's Avatar
24 May 2025 20:09

W5100S-EVB-PICO stepgenerator and encoder driver

Category: Driver Boards

Precompiled .uf2 in the repository binary directory, you not need to rebuild the project if you want to use
  • PCW
  • PCW's Avatar
24 May 2025 19:59
Replied by PCW on topic MESA 7i76E burning out issue

MESA 7i76E burning out issue

Category: Driver Boards

Ack!! 40V is a real issue and indicates a grounding problem. This likely
what damaged the step/dir outputs (accidental contact to shield ground would do it)

I would verify that the drive frame grounds connect to earth ground and that the
7I76E ground (24V logic power ground) is also connected to earth ground.
  • ihavenofish
  • ihavenofish
24 May 2025 18:36
Replied by ihavenofish on topic help with ethercat and omron drives

help with ethercat and omron drives

Category: EtherCAT

well now all 3 drives are in op mode with no errors showing.

... now what do i do? haha
  • ihavenofish
  • ihavenofish
24 May 2025 18:11
Replied by ihavenofish on topic help with ethercat and omron drives

help with ethercat and omron drives

Category: EtherCAT

Yeah that didn't work. I found a different xml with more "stuff" (pdo, etc) and it has put me in OP mode. even though I don't see any actual difference.

But its progress!
  • cakeslob
  • cakeslob
24 May 2025 17:53
Replied by cakeslob on topic New side panel and axisui pins

New side panel and axisui pins

Category: AXIS

Hey, you can try this one out, its still got some buts but it does the thing you want
github.com/cakeslob/regularmac_800/tree/search_gcode
  • Hakan
  • Hakan
24 May 2025 17:41
Replied by Hakan on topic help with ethercat and omron drives

help with ethercat and omron drives

Category: EtherCAT

From that Omron thread, it looks like Arvidb got it working, so can you try with the ecat-conf.xml?
<masters>
	<master idx="0" appTimePeriod="1000000" refClockSyncCycles="1">
		<slave idx="0" type="R88D-KN02H-ECT">
			<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
			<watchdog divider="2498" intervals="1000"/>
		</slave>
	</master>
</masters>
It's the same xml that Arvidb used, but I have changed to what I think it the right model, based on the product code 6 you use.
  • Aciera
  • Aciera's Avatar
24 May 2025 17:30 - 24 May 2025 17:33
Replied by Aciera on topic problems with Verser Probe Screen 2.9

problems with Verser Probe Screen 2.9

Category: Basic Configuration

You need to remove this from your hal
loadusr -W /home/cnc/linuxcnc/configs/lycnc/psng/python/probe_screen.py


You are already loading probe_screen.py with the EMBED_TAB_COMMAND in the INI.

To troubleshoot the pin problem, comment all lines with 'probe.' pins so the config starts up and use the 'Show Hal Configuration' tool to check if the pins are there.
  • ihavenofish
  • ihavenofish
24 May 2025 17:19
help with ethercat and omron drives was created by ihavenofish

help with ethercat and omron drives

Category: EtherCAT

Sooo, back at my ethercat fun and I think I've made progress, but I'm stuck.

I've gone right to the basics and am just using halshow to poke the drives.
I made a super basic xml file following some other examples on here.

So, following this:
EtherCAT: How to use the dedicated OmrG5 lcec driver? - LinuxCNC $ ethercat slaves shows me my 3 drives just fine
$ ethercat upload -p 0 -t int32 0x6064 0x0 shows me position just fine
$ ethercat safeop doesn't work and returns error 90 because the default sync0Cycle is wrong. This seems expected.

My xml is:

<masters>
<master idx="0" appTimePeriod="1000000" refClockSyncCycles="1">
<slave idx="0" type="generic" vid="#00000083" pid="#00000006">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<watchdog divider="2498" intervals="1000"/>
</slave>
</master>
</masters>(using the generic driver here cause the omron one was saying no drive found)


then we do this in halshow:
loadrt threads name1=master period1=1000000
loadusr -W lcec_conf linuxcnc/configs/ecat-test.xml
loadrt lcec
addf lcec.read-all master
addf lcec.write-all master
start

All works, except after we get to start, the drives show error 83, and if you look at the pins, its actually cycling through preop, safeop, inti, op, error every so many ms.

So what have I done wrong here, or what do I need to add? The are many gaps in the information and steps people provide so I expect there's just something missing I don't know about.

Thanks!
  • knipknap
  • knipknap
24 May 2025 17:08
Replied by knipknap on topic MESA 7i76E burning out issue

MESA 7i76E burning out issue

Category: Driver Boards

Thanks a lot for your help!

Now that I hooked up an oscilloscope, the problem disappeared completely again - can't reproduce it anymore, at all.

That made generating pulses easier of course, I simply jogged the thing along. The levels of the step+/- pins on the motor side are around 4.8 volts, and -4.8 on a pulse.

I also noticed that the level between STEP- and the cable shield (GND) is around 40 volts AC (50 Hz). I can't say I understand why that would be so. Is that normal/intended?
  • theoneandonlyoreo
  • theoneandonlyoreo
24 May 2025 16:52 - 24 May 2025 16:54
Replied by theoneandonlyoreo on topic problems with Verser Probe Screen 2.9

problems with Verser Probe Screen 2.9

Category: Basic Configuration

It appears that the pins in question (probe.toolchange-change, etc) would be created by probe_screen.py.

In the INI file,
EMBED_TAB_NAME=PSNG
EMBED_TAB_COMMAND=halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -u psng/python/probe_screen.py -x {XID} psng/probe_screen.glade
EMBED_TAB_LOCATION = ntb_user_tabs

And from custom_postgui.hal
# Ensure all toolchange pins are free to use
unlinkp iocontrol.0.tool-number
unlinkp iocontrol.0.tool-prep-number
unlinkp iocontrol.0.tool-change
unlinkp iocontrol.0.tool-changed
unlinkp iocontrol.0.tool-prepare
unlinkp iocontrol.0.tool-prepared

net tool-change            probe.toolchange-change      <=   iocontrol.0.tool-change 
net tool-changed           probe.toolchange-changed     =>   iocontrol.0.tool-changed
net tool-number            probe.toolchange-number      <=   iocontrol.0.tool-number
net tool-prep-number       probe.toolchange-prep-number <=   iocontrol.0.tool-prep-number
net tool-prep-loopback     iocontrol.0.tool-prepare     <=   iocontrol.0.tool-prepared

net tool-prep-loop         iocontrol.0.tool-prepare      <=   iocontrol.0.tool-prepared

#loadusr -W probe_screen

loadusr -W /home/cnc/linuxcnc/configs/lycnc/psng/python/probe_screen.py
 
  • cmorley
  • cmorley
24 May 2025 16:49
Replied by cmorley on topic Keyboard shortcut rempaping

Keyboard shortcut rempaping

Category: Qtvcp

Try this.
in your config folder add folders qtvcp/screens/qtdragon_hd

in the qtdragon_hd folder add this file, name it qtdragon_hd_handler.py
  • Lcvette
  • Lcvette's Avatar
24 May 2025 16:38
Replied by Lcvette on topic Install Probe Basic

Install Probe Basic

Category: QtPyVCP

for installing qtpyvcp and probe basic use the apt install, it stay updated and will update as updates are available when you run sudo apt update for the system.

the linuxcnc installation seems to be a moving target, i use my own instructions in the stable_quick_start_apt for installing debian and linuxcnc and it seems to be the most reliable. but you technically should be able to do it the way you outlined above. please report back if you get errors.
Displaying 3391 - 3405 out of 24524 results.
Time to create page: 0.212 seconds
Powered by Kunena Forum