Hello Guest it is May 30, 2024, 04:18:26 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Analias

Pages: « 1 2 3 4 5 6 7 8 9 10 11 »
Brains Development / User LED values not tracking correctly
« on: March 01, 2018, 12:03:50 PM »
I am attempting to write a brain to handle the MPG on my Yaskawa pendent. I'm using the PoKeys Pendent Core board from CNC4PC. I'm seeing a weird behavior when user LEDs. I'm not sure if it is a bug or if there is an explanation for it.

I am trying to modify the behavior of the "Handle" button on the Yaskawa to do the following:

  1. If not in MPG mode, switch to MPG mode using button 327.
  2. When in MPG mode, cycle through MPG Jog Modes using button 302.

I have configured the PoKeys to use two user LEDs. User LED 1899 tracks state of "Handle" button Yaskawa. User LED 1898 acts as a inhibit flag to avoid changing MPG Jog Mode when switching back into MPG mode using button 327.  User LED 1898 is turned on and held high with a timer. During that time, the brain for switching MPG Jog Modes (with button 302) is disabled.  This avoids both enabling MPG Mode and cycling to the next MPG Jog Mode when switching back from Jog or Rapids on the Yaskawa.

It almost works. The oddity I am seeing is that the user LED 1898 used to inhibit the MPG Jog Mode cycling tracks opposite to what the user LED is set to.

I have included the brain. Yes, I have double and triple checked that nothing else is using the user LEDs and that the PoKeys is set correctly. I have the PoKeys configured to set the user LED 1899 to the state of the "Handle" button on the Yaskawa (Matrix Keyboard 3, 1). Only the brains set the state of the user LED 1898.

Any help or advice would be appreciated.


PoKeys / Re: Are Matrix Keyboard monitoring realtime or latched?
« on: February 28, 2018, 11:09:31 AM »
To answer my own question :)...

User LEDs are updated realtime with the actual state of the signal from the PoKey, there is no latching or buffering involved.


PoKeys / Are Matrix Keyboard monitoring realtime or latched?
« on: February 27, 2018, 12:38:01 PM »
When I configure a Matrix Keyboard entry to use a user LED value (1899 in this case) is it updated in real-time with the state of the input or is it latched?

I have a Yasakawa pendent I'm re-configuring to allow stepping through MPG modes each time the "Handle" (MPG jog select) is pressed. Implementing the brain would be easier if the user LED was updated real-time based on if the pendent button is pressed or not. Otherwise, I need to add a time out for the LED to reset it and simulate a button release.


When displaying long Material names (such as, "Hardwood Plywood"), the name exceeds the available space in the Job Settings and overflows box boarder and is truncated by the tool path display.


Mill Wizard 1.0.17 [licensed]

I have a job that uses the Keyway Slot operation.  The generated g-code only specifies the feed speed (F) when plunging and does not override the feed when executing horizontal moves.


Mach4 General Discussion / Re: Screen Set Ideas
« on: October 21, 2014, 02:03:16 PM »
Oooooooo... nice.  An ethernet based panel with keybooard, switches, MPGs and DRO outputs running off a BeagleBoardBlack was on my wish list.  Nice to see it can be done.

Mach4 General Discussion / Re: Mach 4 Feature Request
« on: October 16, 2014, 01:11:00 AM »
Would it be possible to specify having the menu bar hide itself when in full screen mode, and have it show when the user presses 'alt'?  This would allow maximum screen area to be available for use by mach 4 screens.

This is similar to several Windows apps that I know of.


Mach4 General Discussion / Re: Mach4 Printer Port Discussions
« on: October 15, 2014, 02:28:27 PM »

Should homing work with the latest Darwin (2030, 2035)?  When I initiate a "ref all" or per axis with lua calls nothing moves.


Mach4 General Discussion / Re: Mach4 Printer Port Discussions
« on: October 07, 2014, 10:04:38 PM »

It looks like Mach 4 build 2030 and Darwin 2035 (both licensed) is work exceptionally well.  The stutter I use to observe when jogging in Mach 4 has disappeared.  I'm running Darwin at 40,000 with no problems.  


Mach4 General Discussion / Re: Screen Set Ideas
« on: September 05, 2014, 11:10:31 PM »
Scott, after swapping back in the code to load my image, your changes worked flawlessly.  I'll spend some time this weekend writing up the code to convert mouse click X-Y into operations  (Probe-X, Probe-Z, Edge probe, etc.).

Thanks for the insight.


Pages: « 1 2 3 4 5 6 7 8 9 10 11 »