Advanced Search

tommylight wrote:

langdons wrote:

Eventually they gave up and adopted USB-C. (Oh well..., so much for all that work)
nope, they did not "adopt" it, they were forced by Europe.

And I am sure the industry retaliated by strictly enforcing the USBC charging standards so device that used to charge OK on low voltage no longer do.

I never experienced this either But I rarely cut longer than 400mm
Customer says on a long cut, the torch comes down and hits the material and crashes.

I am guessing this has something to do with PID settings but I never used anything other than default settings. Any ideas on how to correct this would be appreciated.

Level flight would be appreciated. I do remember when a light aircraft thought he was flying level but ploughed in well short of the runway with tragic and fatal consequences. Pilot could see the town lights and flew visual instead of by instruments. Seems this is similar,

3 phase CB should be 3 pole, not 3 individual 1 pole breakers, to prevent single phasing. I would also recommend installing a phase monitor and connecting to the main contactor to cut power if one phase is lost from the power grid.

Reported by a customer. Sometimes, QTP freezes. Moving the float switch by hand seems to clear the error and the cut proceeds.
Any ideas or feedback? I have never experienced this.
I wanted to write a script that updates APT to look at the new Buildbot for 2.10 instead of the Linuxcnc.org 2.94  repo so it looks like I need to do that now....

Yes, I would cut off the pins of the IC too. Even if you have hot air, you can fry the connector.
I think these are reverse diodes. Remove the chip, check with a multimeter for a short, and power up the board.
 

Hi Chris,
I've opened mine and I can see how it works. I suspect the vertical and horizontal quills are identical enough that we could swap them.
The bolt with the sleeve is item 2 on the drawing. If you replaced the head of the bolt with a Kipps handle it would work like the vertical clamping handle. So that sleeve will push on the 2 arced pieces like in my photos on page 171, and clamp around the quill.
You have to remove the cover plug to get to the bolt head. Take out the 5mm grub screw and use a normal 5mm bolt to pull it out.Once loose, the quill should be free. Remember to disconnect the hydraulic elbow item 5 at the rear and the feather key underneath the slide item 6. I would think that the quill would slide without removing the front seal system item 4, but it may be full of dirt like mine.
If you look closely you can see the type of markings on the spline they talk about for reassembly. That's on a different spline though.
Looks pretty easy.
Good luck with it,
David

My old T530 has FireWire, the only thing that'll connect to that I have is a camera.
Interfaces come and go, it's the nature of the beast, think coax for networking, ega,CGA, VGA still seems to be hanging in there, IDE, Floppy, old school wide SCSI.
Tho the industrial serial stuff seems to last, thanks to it being electrically robust.

Hi PCW,

Noted on this. Ill first wire the enable of mesa 7i77 to the enable of the servo drive bds4 since I found out that there is a difference in bias/balance (adjustment for zero movement upon drive enablement) if I force enable (jumping the enable of the servo drive (Daredevil)) instead of the mesa board.

I'll first connect the ENAn of the 7i77 to the servo drives so that once the drives are enabled, there will be no movement.

After that, will follow your instructions and use 4096 as a scale starting point to fine tune one axis.

Thank you for your advise.

Regards,
Kelvin

langdons wrote:

Eventually they gave up and adopted USB-C. (Oh well..., so much for all that work)

nope, they did not "adopt" it, they were forced by Europe.

bevins wrote:

You can do it like this.

loadrt toggle count=5
addf toggle.0 servo-thread
setp toggle.0.debounce 50 

net flood-toggle toggle.0.in <= hm2_5i25.0.7i77.0.0.input-29
net flood-control toggle.0.out => hm2_5i25.0.7i77.0.0.output-02

If you need only one toggle, do not use "count=5" as that creates 5 toggles, so that would also need all the addf and setp and inputs and outputs in hal, for all 5, from 0 to 4.

You can do it like this.

loadrt toggle count=5
addf toggle.0 servo-thread
setp toggle.0.debounce 50 

net flood-toggle toggle.0.in <= hm2_5i25.0.7i77.0.0.input-29
net flood-control toggle.0.out => hm2_5i25.0.7i77.0.0.output-02

Thanks for the replies, I should have noted the inhibit logic on the drive itself in my earlier post, but from my interpretation of the datasheet for the 12A8, GND at the input would disable the drive.  Is that correct?
11 INHIBIT IN TTL level (+5 V) inhibit/enable input. Leave open to enable drive. Pull to ground to inhibit drive. Inhibit turns off all power devices.

If so, I would just connect direct to each servo drive with a ground wire connected to the following pins below on the mesa board and then the other side of the floating switch would also go to GND:  
net joint-0-enable joint.0.amp-enable-out => hm2_7i97.0.ssr.00.out-00
net joint-1-enable joint.1.amp-enable-out => hm2_7i97.0.ssr.00.out-01

Alternatively, if I could figure out how to make those into one signal with OR'ed logic for turning ON and AND logic for turning off, I would just drive the 12V relay on the board with one output, however, the Estop approach may be the simplest one to implement when reusing the existing PCB.  

I'm assuming the Mesa board / LCNC don't care if anything is connected to servo enable as long as the motors move when commanded?  Meaning if the servos were enabled externally via Estop for example, the motion control would still work just fine and I could leave out the above two net commands from the HAL file?

No it is not.
FireWire was a very good standard that got killed by corporate greed.
It was also used for networking mainly as interconnect between switches due to it's full duplex speed, besides all DV cameras having it at one point in time.
I liked it and used it plenty, and still have some add on cards rusting away in the shop.

Hi,

I am currently implementing a rack tool changer. My problem is that the Hal Pin "iocontrol.0.tool-prep-pocket" is always Zero. Do I need to activate it in my HAL File? Its currently initialized as following:
My Tool Table looks as follows:
However, even when inserting Tool1 prep-pocket is always 0. Is there something I am missing?
 

Thank you for the reply. Following the video on this thread, I installed the xml provided by the manufacturer but when I try to run linuxcnc I get the error:

~/linuxcnc/configs/sim.axis$ linuxcnc lathe.ini
LINUXCNC - 2.9.3
Machine configuration directory is '/home/phil/linuxcnc/configs/sim.axis'
Machine configuration file is 'lathe.ini'
Starting LinuxCNC...
libnml/buffer/shmem.cc 320: Shared memory buffers toolCmd and toolCmd may conflict. (key=1004(0x3EC))
libnml/buffer/shmem.cc 320: Shared memory buffers toolSts and toolSts may conflict. (key=1005(0x3ED))
libnml/buffer/shmem.cc 320: Shared memory buffers emcError and emcError may conflict. (key=1003(0x3EB))
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(LIB): /usr/share/linuxcnc/hallib/basic_sim.tcl
setup_kins: cmd=loadrt trivkins coordinates=xz
Found file(REL): ./ethercat.hal
./ethercat.hal:1: lcec_conf exited without becoming ready
Shutting down and cleaning up LinuxCNC...
Note: Using POSIX realtime
LinuxCNC terminated with an error. You can find more information in the log:
/home/phil/linuxcnc_debug.txt
and
/home/phil/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal


linuxcnc_debug.txt contains:
13223
Stopping realtime threads
Unloading hal components

Linuxcnc_print.txt contains:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
INIFILE=/home/phil/linuxcnc/configs/sim.axis/lathe.ini
VERSION=1.1
PARAMETER_FILE=sim-lathe.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=X Z
KINEMATICS=trivkins coordinates=xz
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Please help, where do I go from here?