Hello everyone, I have a small problem. I have three VEICHI drives connected via Ethercat in my system. My task was to connect a fourth driver to them, but from a different manufacturer (Servotronix CDHD2S). I purchased this driver, and everything works fine with the PC. Then I connected the driver to the common system with the other drivers via Ethercat, configured it, and added vid and pid. As a result, Linux CNC starts, but the driver hangs in an error and does not switch from PREOP to OP. Please advise what the problem might be. I am attaching my configurations and the xml from the driver manufacturer.       

..in connection with the machine retrofit #338210
, I would like to include the hardware buttons in the configuration, also calculating the mpg. I have a lot of free inputs (all on 7i96s) and about twenty on 7i77 where I left the first three free as I understood that they are analog because of the potentiometer) now I need a suggestion, since dont have schematic for the old controller and not for the buttons, I think they are all on 24vdc including mpg. the outputs that I connected to 7i77 lit the bulbs of these buttons at 24v. should I try the configuration in terms of the mpg pendant for selector increments and mpg, and for spindle and feed override how should I connect? Thanks

Hello everyone,

I’ve been lucky enough to be the recipient of a Brother TC215 midway through a LinuxCNC conversion. I’ve always wanted to try my hand at CNC work, as I’ve done a little bit of manual milling and a lot of fabrication work over the years, and I’m always curious to learn and build new things. It’s been a pretty steep learning curve, as I’m new to basically all of this, but I’ve leaned a lot via search and previous forum threads and I think I’m at the point where starting a thread is worthwhile. 

On the hardware side: 

• Mill is a Brother TC215
• Dyn4 AC Servo Drivers/motors
• Mesa 7i92 / 7i76 / 7i77D control boards
• HP Elite 8300 USDT running LinuxCNC / ProbeBasic

I'm currently planning on running some of the older Brother boards for things like coolant, safety switches, limit switches, etc, just to keep things simple for now, as I already have breakout boards for all the connectors. I can clean everything up later if it gets that far.  My friend validated that the mill’s mechanical functions are in good shape and made it about halfway through the wiring - but my current priority is to wire everything up such that I can get XYZ servo movement first, and then I will add additional functionality. So I’ll try and keep this thread focused on the help I need to get things moving under their own power. 

What I’ve got so far is: The hardware is mounted in the mill, I roughly understand how things are laid out. I feel like i have a broad sense of how this should go together, but the details are oftentimes a little more opaque than I’d like.  What I’ll be doing when I have a minute :

1. Test all my servo controllers and drives (easy to do, just need to get my windows laptop out to the mill)
2. Power up the Mesa board (pretty easy, just need to spend some time looking at all the wiring and make sure I don’t fry anything)

The thing that’s blocking me right now is that I don’t really know enough to confirm that I’m wiring the servo drivers in a reasonable way. My understanding is: I should be able to wire my X / Y / Z servos in the following way, to do analog +10v control as a simple starting point. I need to set it up so I’m wiring: 

• 7i77D +24v from field power to Dyn4 JP4-15 (Servo Enable) 
• 7i77D TB5 (Analog Drive Interface) To Dyn4 JP4-13 (Analog +10v) & JP4-25 (Analog GND)
• 7i77D TB3 (Encoder 0-2) to Dyn4 JP5-2 through 8 (Encoder outputs)

My plan was to disconnect all the motors from the mill and test them on the bench, but running through LinuxCNC, so I can confirm my understanding on how LinuxCNC operates. Once the motors are confirmed to work on the bench, then I would start on wiring up the Estop, limit switches, and other things I would need to get the mill safely moving, and then follow that with wiring in the spindle.


Here's a picture of how things it sits:
image missing https://i.imgur.com/uCXxmRn.jpeg

Any and all feedback appreciated, as well as suggestions about if I should approach this another way. I've learned a lot here and I hope that documenting this in the long run helps someone else

Vielen Dank das du den PP zur Verfügung stellst, ich werde es die Tage ausprobieren

Guten Morgen liebe Leute !
Ich möchte euch Heute von einem Seltsamen Phänomen berichten und bin gespannt,ob schon jemand dieses Problem hatte ,oder gar einen Lösungsvorschlag.   Der Sachverhalt ist folgender : Ich habe eine Platte in Fusion 360 Konstruiert, mit unter anderem 6Stk  8er Bohrungen,die zuerst im Bohrzyklus Gebohrt werden und nachher eine 13mm Senkung für den Schraubenkopf durch Bohrfräsen erhalten sollen,alles im selben Setup. Ganz Simpel,schon tausend mal gemacht,aber diesmal will es partout nicht Funktionieren !  Der Fräser will die Senkung 10mm in X Achse versetzt machen ! Wenn ich dann den G Code für den Bohrzyklus Lade,dann fährt der Fräser aber genau an der richtigen Stelle ins Material. Habe schon vieles Probiert,anderes Werkzeug,neues Setup mit genau dem selben Nullpunkt ect alles Erfolglos.  Ich werde als nächste ein neues Setup erstellen,mit dem Nullpunkt in der ersten Bohrung,die ja im Borzyklus Korrekt angefahren wird... Nächste Woche werde ich dann sehen. LG

I forgot to mention the state machine also has a "manual jog" mode, which I can use to move the machine if, for instance, I manage to crash one pallet into another.

I'm rebuilding a robotic loader. I have a GUI built with GladeVCP hooked to a python state machine. (I am not going to run this robot with Axis or any other machine-tool-oriented user interface).

The state machine already has an interpreter that spits out waypoints, which depend on the state machine's internal variables. What's the best way to connect this to the linuxcnc motion planner?

the small one is an RS422 to TTL

little update:

youtube.com/shorts/vfd948wLu4w

I spent a lot of time studying the machine schematics and have a decent grasp of the workings thereof. 
I removed the old Anilam GXM control, screen and manual control panel. The MESA 7i77 connected up to the encoders and I can read XYZ in the DRO screen. I can plot W in the HAL Scope, but it does not show on the DRO yet. (I think I selected encoder as rotary axis in PNCConf and will sort this out later.)
I now want to start connecting the limit switches and other IO's but have some things I am not clear on. 
On the schematic attached: 
D_A/18 and EXP/18  (37) would connect to V-Field on TB2
D_A/17 and EXP/17 (00) would connect to Ground on TB2
D-A/21, D-A/24, D-A/26, EXP/22 can be ignored for now. Was only pulled high to prevent fault condition for axis not in use on GXM
D-A/23 (83) is a input to indicate E-Stop active when not high.
D-A/25 (62) is a input to indicate Lubrication unit fail. (Feed Hold/ External Stop)
D-A/22 (820) is a input to indicate no axis overtravel and E-stop out.
D-A/26 (87) X Positive vector (Input)
D-A/24 (88) X Negative vector (Input)
D-A/23 (89) Y Positive vector (Input)
D-A/25 (90) Y Negative vector (Input)
D-A/19 (91) Z Positive vector (Input)
D-A/21 (92) Z Negative vector (Input)
D-A/09 (81) E-Stop Out and Reset Pressed (Input)

D-A/02 (72) M8 Coolant Off (Output, Drain)
D-A/08 (69) M5 Spindle Stop(Output, Drain)
D-A/04 (71) M7 Coolant On (Output, Drain)
D-A/12 (67) M3 Spindle Forward (Output, Drain)
D-A/10 (68) M4 Spindle Reverse (Output, Drain)
D-A/06 (70) M6 Tool Override (Output, Drain)
EXP/10 (236) "M Strobe" (Output, Drain)
EXP/20 (230) "Fin" (Output, Drain)
EXP/14 (235) "S Strobe" (Output, Drain)
EXP/06 (2311) "T Strobe" (Output, Drain)

Once I can get the limits and E-Stop circuits connected, I should be able to connect the motors and start tuning them. 
Any thoughts or comments welcome.
 
 



 

How use MB2HAL with Huanyang FC01 :
1) Install userspace component if you don't have it:sudo apt install linuxcnc-uspace linuxcnc-uspace-dev 
2) create fc01_vfd.ini 3) create vfd.hal ​​​​​​​4) add vfd.hal to your machine ini file
 

I could not get Linuxcnc to launch on Mint. This could have been due to me not setting up the Hal and ini files correctly. I switched back to my old installation and it now seems stable. PNCConf was the key to get me up and running, Thanks!

Sorry, I am using version 2.9.3.

and uname -srm:
Linux 6.1.0-30-rt-amd64 x86_64

 

ok, works also on the 7c81 ports