---In DynoMotion@yahoogroups.com, <tk@...> wrote:

Hi Moray,

What do you mean by "Mach OEM inputs"?

How are they configured?

If you configure the standard inputs do they toggle on the standard Mach3 Diagnostics Screen?

How did you set up the Coolant?

Regards

TK

From: "moray.cuthill@..." <moray.cuthill@...>
To: DynoMotion@yahoogroups.com
Sent: Saturday, November 9, 2013 1:58 PM
Subject: [DynoMotion] RE: A couple questions regarding Mach

 

Hi Tom,

 

thanks for the reply. It's always good to hear when I'm heading the right direction!

 

I noticed the page about passing variables not long after I posted here, and it seems fairly straight forward.

 

However, I'm having a problem getting Mach to read or write the KFlop bits. I added a couple LEDs to a custom screenset which are controlled by Mach OEM inputs and set the ports/pins accordingly, but they wouldn't work. I even tried swapping the port/pins to virtual bits and triggering them via KMotion, but still no response.

I also tried setting up the Coolant, however it also has no response when activated.

Any idea what would cause this?

 

I'm also having problems with the Modbus example, but I'll start another thread for that

 

Thanks

Moray

---In dynomotion@yahoogroups.com, <tk@...> wrote:

Hi Moray,

I think the approach you describe is good.  Create a Virtual EStop input for Mach3 using a Virtual IO bit.  Then if any of your EStop conditions occur set that bit.

Regarding displaying a Variable.  You would need to program Mach3 to upload the variable and display it.  You could upload it periodically (Mach3 Macro Pump) or if you know when it changes then after it changes (ie end of a tool change).  You would need to convert the integer to a double and place it in a pair of KFOP UserData variables (either constantly in KFLOP or by invoking code in KFLOP to do it with a NotifyPlugins()).  Then Mach3 could upload the double value to a DRO.  Then it may (or may not) be necessary to move that DRO value to another DRO on a screen.  See:

http://dynomotion.com/Help/Mach3Plugin/Mach3DROs.htm

HTH

Regards

TK

From: "moray.cuthill@..." <moray.cuthill@...>
To: DynoMotion@yahoogroups.com
Sent: Saturday, November 9, 2013 5:53 AM
Subject: [DynoMotion] A couple questions regarding Mach

 

How is the best way to trigger an e-stop within Mach, so that the Mach Reset button has to be clicked to reactivate things?

 

On my other non-Kflop lathe, this simply happens whenever an E-stop is triggered, as there's nothing complicated needing done, so Mach simply gets notified, I fix the problem, then hit the Reset button.

 

However on my new lathe, I need to monitor a few inputs, and then be able to trigger an E-Stop like condition (probably best to call it a soft E-Stop), which then requires the fault to be cleared before a Reset. One use is for the tool changer, which if it fails to move and lock correctly, I'd like to stop all movement and trigger a "soft" E-Stop without killing power. That way I still have power to try reindexing the tool changer.

Also if a Servo drive faults out, I'd like to do a similar thing.

I did consider adding the faults into the main E-Stop circuit to kill power, but the servo drives are interlinked so if one faults, a stop signal gets issued to stop them quicker, however I still need to notify Mach to stop.

 

There is still a physical E-Stop circuit that kills all movement power if needed, and it has it's status fed back to a KFlop input.

 

The only option I can think of without relying on a Mach Brain, is map the physical and 'soft' E-Stop bits to a virtual bit which the KFlop updates, then have that virtual bit set as the Mach E-Stop input. Is this the best way, or is there some other way to handle this?

I'll be programing the KFlop to handle the actual stopping, as I don't want to rely on waiting for Mach to respond and stop things.

 

 

The other quick question I'm sure I've missed somewhere, is how do I get a variable value within the KFlop to display in a Mach DRO?

I simply want to display the Toolchanger position within Mach, which is stored as an Int within the KFlop (after being read via Modbus from the PLC). I can add a DRO within Mach, but is this something I need to add via a Notify Plugin?

 

 

On a side note, I'm managing the programming for the KFlop reasonably well. I had the lathe moving for the first time under Mach control last night, it's just I'm struggling a bit with understanding how the KFlop and Mach interact, and figuring out best how to acheive what I'd like.

 

Thanks

Moray

---In DynoMotion@yahoogroups.com, <tk@...> wrote:

Hi Moray,

I think your Mach3 Port numbers are off by one.  Port 0 in not used Port 1 is for the normal KFLOP IO numbers. Port 2 is for IO 128 and higher. 

Regards

TK

On Nov 10, 2013, at 2:57 PM, <moray.cuthill@...> wrote:

 

Hi Tom,

 

I actually meant the normal Mach inputs. I originally had used the OEM trigger inputs, before realising I had scrolled past the normal inputs. I spent a bit of time yesterday working on a custom mach screen, and I suspect I may of put the wrong code in for the LEDs I added, however nothing showed on the diagnostic screen for the normal inputs either.

 

The coolant I set up as normal through the ports and pins. I set Mach Output #3 (default output for flood) to Port 1 Pin 27 (should be FET 3) and nothing happened so I tried setting it to a virtual bit, Port 0 Pin 62, and it never got activated either despite the LED turning on in Mach.

 

Thanks

Moray

---In DynoMotion@yahoogroups.com, <tk@...> wrote:

Hi Moray,

What do you mean by "Mach OEM inputs"?

How are they configured?

If you configure the standard inputs do they toggle on the standard Mach3 Diagnostics Screen?

How did you set up the Coolant?

Regards

TK

From: "moray.cuthill@..." <moray.cuthill@...>
To: DynoMotion@yahoogroups.com
Sent: Saturday, November 9, 2013 1:58 PM
Subject: [DynoMotion] RE: A couple questions regarding Mach

 

Hi Tom,

 

thanks for the reply. It's always good to hear when I'm heading the right direction!

 

I noticed the page about passing variables not long after I posted here, and it seems fairly straight forward.

 

However, I'm having a problem getting Mach to read or write the KFlop bits. I added a couple LEDs to a custom screenset which are controlled by Mach OEM inputs and set the ports/pins accordingly, but they wouldn't work. I even tried swapping the port/pins to virtual bits and triggering them via KMotion, but still no response.

I also tried setting up the Coolant, however it also has no response when activated.

Any idea what would cause this?

 

I'm also having problems with the Modbus example, but I'll start another thread for that

 

Thanks

Moray

---In dynomotion@yahoogroups.com, <tk@...> wrote:

Hi Moray,

I think the approach you describe is good.  Create a Virtual EStop input for Mach3 using a Virtual IO bit.  Then if any of your EStop conditions occur set that bit.

Regarding displaying a Variable.  You would need to program Mach3 to upload the variable and display it.  You could upload it periodically (Mach3 Macro Pump) or if you know when it changes then after it changes (ie end of a tool change).  You would need to convert the integer to a double and place it in a pair of KFOP UserData variables (either constantly in KFLOP or by invoking code in KFLOP to do it with a NotifyPlugins()).  Then Mach3 could upload the double value to a DRO.  Then it may (or may not) be necessary to move that DRO value to another DRO on a screen.  See:

http://dynomotion.com/Help/Mach3Plugin/Mach3DROs.htm

HTH

Regards

TK

From: "moray.cuthill@..." <moray.cuthill@...>
To: DynoMotion@yahoogroups.com
Sent: Saturday, November 9, 2013 5:53 AM
Subject: [DynoMotion] A couple questions regarding Mach

 

How is the best way to trigger an e-stop within Mach, so that the Mach Reset button has to be clicked to reactivate things?

 

On my other non-Kflop lathe, this simply happens whenever an E-stop is triggered, as there's nothing complicated needing done, so Mach simply gets notified, I fix the problem, then hit the Reset button.

 

However on my new lathe, I need to monitor a few inputs, and then be able to trigger an E-Stop like condition (probably best to call it a soft E-Stop), which then requires the fault to be cleared before a Reset. One use is for the tool changer, which if it fails to move and lock correctly, I'd like to stop all movement and trigger a "soft" E-Stop without killing power. That way I still have power to try reindexing the tool changer.

Also if a Servo drive faults out, I'd like to do a similar thing.

I did consider adding the faults into the main E-Stop circuit to kill power, but the servo drives are interlinked so if one faults, a stop signal gets issued to stop them quicker, however I still need to notify Mach to stop.

 

There is still a physical E-Stop circuit that kills all movement power if needed, and it has it's status fed back to a KFlop input.

 

The only option I can think of without relying on a Mach Brain, is map the physical and 'soft' E-Stop bits to a virtual bit which the KFlop updates, then have that virtual bit set as the Mach E-Stop input. Is this the best way, or is there some other way to handle this?

I'll be programing the KFlop to handle the actual stopping, as I don't want to rely on waiting for Mach to respond and stop things.

 

 

The other quick question I'm sure I've missed somewhere, is how do I get a variable value within the KFlop to display in a Mach DRO?

I simply want to display the Toolchanger position within Mach, which is stored as an Int within the KFlop (after being read via Modbus from the PLC). I can add a DRO within Mach, but is this something I need to add via a Notify Plugin?

 

 

On a side note, I'm managing the programming for the KFlop reasonably well. I had the lathe moving for the first time under Mach control last night, it's just I'm struggling a bit with understanding how the KFlop and Mach interact, and figuring out best how to acheive what I'd like.

 

Thanks

Moray