Advanced Search

All Mesa Ethernet cards support Auto–MDI-X so it should not matter.

That said, all testing is done with straight through cables.
 

Hallo PCW,
danke für die Antwort.
Ist es wichtig ob man zum Anschluß der 7I96 ein Patchkabel oder ein Crossoverkabel nimmt?
MfG
Hans

Hey!

I am back on project.
I played a little bit with the arm.. adjust the backlash/teeth play and get now the correct scales for all joints.

In the next days i will machine a sharpie holder... then i will starting with first trails drawing on cardboard. I checked all movements in world mode.. x y z... and it looks good.. tomorrow i will test with a dial.

For my understanding:
The dh parameters doesnt changed... i must set the arm to different ready position over the homeoffset. Right?

Thanks

I’ve recently acquired an older AXYZ 4008 CNC router and am in the process of replacing the original AXYZ controller with LinuxCNC and a Mesa 7I95T.

I thought I’d document the conversion here, both in case it helps somebody else and because I’m very interested in advice from anyone who has already converted one of these machines.The intention is not to gut the machine unnecessarily. Mechanically it appears to be a very substantial router and much of the original electrical hardware looks perfectly serviceable. The aim is therefore to replace the obsolete controller while retaining as much of the original AXYZ hardware as practical.The machine is an AXYZ 4008, approximately 2007 vintage, with a roughly 3 × 2 m working area and an ELTE spindle. X and Y are rack-and-pinion driven and Z uses a screw.Motion is provided by Vexta/Oriental Motor PK299-F4.5A 2-phase steppers, rated 4.5 A, driven by the original Pacific Scientific 6410 stepper drives.The 6410s are particularly encouraging because they accept fairly conventional step/direction control. The existing AXYZ controller feeds the drives through DB9 connectors. We initially considered reverse-engineering these signals with a logic analyser, but having found the drive documentation and previous AXYZ LinuxCNC conversions, that now seems largely unnecessary.We have bought a Mesa 7I95T, which should give us considerably more I/O than we immediately require and leaves scope for additional axes/tools later.The rough architecture we're aiming for is:
 One interesting discovery has been the AXYZ connection board inside the cabinet.Rather than simply removing it, we're investigating whether it is worth retaining. It appears to handle quite a lot of the machine-side infrastructure, including limit sensors, tool sensor, E-stop-related connections and various auxiliary functions.It is associated with a substantial toroidal transformer and appears to provide several control voltages including 5 V, 12 V and 18 V.The board has conveniently labelled connections including:
 There are also connections elsewhere on the original controller for the vacuum pump, dust collection, inverter(s), ATC controller and RS485.So at the moment we're considering retaining this board as the interface to the existing machine wiring and taking the appropriate signals from it into the 7I95T, rather than rewiring every sensor and auxiliary device individually.One difference from some of the documented Mesa conversions is that the 7I95T doesn't provide the convenient 0–10 V spindle-speed output found on boards such as the 7I76. We'll therefore need a separate interface for the VFD's analogue speed command. Spindle run/enable should be straightforward using an isolated output/relay.The other area we're treating separately is the E-stop system. The original E-stop appears to have been interpreted by the AXYZ electronics, but for the retrofit we want an appropriate hardware safety chain rather than relying on LinuxCNC software alone.Our initial milestones are deliberately simple:

1. Get LinuxCNC communicating reliably with the 7I95T.
2. Connect one original 6410 drive and establish STEP/DIR operation.
3. Jog X/Y/Z correctly.
4. Identify and interface the existing home/limit sensors.
5. Implement a proper hardware E-stop.
6. Start/stop the existing VFD/spindle.
7. Add 0–10 V spindle-speed control.
8. Make the first test cut.

After that we can tackle the tool sensor, vacuum/dust control and eventually the ATC.We have already found the earlier AXYZ 4008 retrofit thread here extremely useful, particularly because it demonstrates that retaining the original AXYZ steppers/drives and interfacing them to Mesa/LinuxCNC is quite practical.I’m documenting photographs of the machine, original controller, connection board, drives, motors and mechanical drive system on our workshop site here:continuumkit.org/workshop-inventory/axyz-cnc/I'll add wiring diagrams, Mesa configuration and anything else we learn as the conversion progresses.If anyone has experience specifically with the AXYZ connection board, Pacific Scientific 6410s, or interfacing an AXYZ spindle/VFD to a 7I95T, I'd be particularly interested to hear how you approached it.

If this is a drive level issue, note that a 26C31 does not swing to 5V
and its output level is about 2 diode drops below 5V (3.6V) with a 5 mA load.

can this also be used for sister tools/replacement tools that point to another tool number?

Why doesn't anyone tell me that there's been a Rio Board in China for three years now?
www.ruten.com.tw/item/22418437051883/

cool

and a video: www.bilibili.com/video/BV15nG96kEQt/

Hello folks,

Wondering if anyone has incorporated a hall effect sensor in their Bridgeport gear head to pick up real-time spindle RPM.

My plan is to drill and tap a hole to pick-up the bull gear teeth with a hall effect sensor, then wire the sensor into my encoder_4 inputs on a  mesa 7i77.
Is this is viable? If it is what I am looking for is measurements and locations on where to drill/tap the hole for the hall effect sensor, also what sensor do people use for this job? I currently have a ZF GS100502 gear tooth speed sensor good to 15khz.

I have the following hardware:
Bridgeport V2XT {1996) donor mill using the legacy servo motors and drives.
Mesa 7i92M and 7i77D
cheap amazon VFD.


Please advise.
John VanAtta
 

Looks ok for me

I have bad experience with xml file.
I don't know why, but a slight difference in the block order made everything work fine, or the motors wouldn't turn...
Therefore, I recommend writing a file for one slave first, testing it thoroughly, adding another slave, testing it again and so on until the last one.
This take more time, but if something will not want to work, at least you will know where the error occurred...

Hey, that’s a bit mean – I want a board like that too

Yes, that really is strange, but I can’t explain it at the moment and I’d be glad if I knew the solution.

All I can do here is take some more measurements; I’ll connect it to a logic analyser again and record the pulses for a bit longer to check them.
But on that board too, please measure the voltage arriving at the driver.

That board looks really good

Hello all,
Just out of curiosity has anyone been able to integrate Okuma drives and encoders with Linux CNC?I know that it is proprietary tech so you are not going to get much information Okuma, but was wondering if anyone has been able to crack it?Thanks

rodw wrote:

Some large commercial tables have a central exhaust duct down the side or up the centre and as the torch passes into a zone, a gate opens and the others close (usually by pneumatics) so the draft is centralised in that particular cutting zone. It is possible to track the torch position and activate the relevant zone with LinuxCNC. The dust is usually filtered and the exchaust ducted outside of the building. I did write a component that did this for another user which triggered a bank of air solenoids.

Rod, you catched me, thanks for this heads up. I have not even thought about that problem of exhaust gases and
pollution stuff. I was thinking to make a water based table under the torch, but this solves just partly this
problem of gases. We have a luck of being in a country where its hot the whole year so everything is open and ventilated, but that does not mean I dont need it.

I have a Riocore + ICEBreakerV1.0e + 26LS31 (pulse, dir) control board. I tested connecting it to an unmodified DM542 (dir / pc817), but it still cannot return to the zero position correctly.There shouldn't be any problem connecting this board to the motor driver using the 26C31 differential output. Adjusting the dirhold value had no effect.  I suspect it might be caused by a deviation in the dir/step during the forward and reverse rotation of the riocore.

 ICEBreakerV1.0e board
 

26C31 Differential Output Driver
 

FPGA
 
 

Can you give details on the procedure you are using to test the sim?
I can't see this behavior on my system but maybe I am doing it wrong.

Thanks