Hello Guest it is April 25, 2024, 02:01:54 AM

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 - simpson36

101
General Mach Discussion / Re: AC Servo Spindle and ESS
« on: April 22, 2015, 09:03:41 AM »
Coincidentally, I have been messing with screens lately and it occurs to me that this issue might be easily fixed by replacing the action behind the stop button.

Both my mill spindle and 4th axis have enable/disable states and pneumatic locks, so I have long ago replaced the spindle ON/Off with macros which check the condition of the lock and enable state prior to starting the spindle and check the speed of the spindle prior to engaging the lock and so on. Both spindles are AC servos, but the drives themselves take care of deceleration in the event of a sudden pulse stream loss, so that was never an issue that I needed to resolve.

I jumped into the Mach3 screen editor to confirm that the red 'stop' button can indeed be changed to trigger a VB script. (see attached image)

From there it should be an easy task to program any sequence you want including checking the spindle speed and decelerating it to zero prior to MACH abruptly shutting off the pulse stream. I am unsure if the 'ismoving' function in MACH works with the spindle, but in case it did not, I recall Hood saying that there is a 'speed reached' signal available from the drive.  I use this signal to prevent Mach from moving the axis prior to the 4th axis reaching speed (for turning) and it works fine.

There are probably a lot of ways to skin this cat, but off hand, I don't see why commanding zero speed and then monitoring a 'speed reached' signal from the drive prior to issuing a 'stop' would not be a complete solution. There may be a way to stop the axis movement while waiting for the spindle to decelerate, but I would need to noodle on that for a while.


102
Mach4 General Discussion / Re: Mach 4 Bug Reports
« on: April 07, 2015, 11:59:30 AM »

Modbus diagnostic window will not close while Modbus is running.

103

Just to follow up on this topic, I have a working setup for getting the analog signal into Mach4 thru TCP Modbus using the Arduino DUE development board.

Some details and a very short video are posted in the 'making MACH4 screens purdy' thread.

104
Mach4 General Discussion / Re: Mach 4 Bug Reports
« on: April 06, 2015, 06:57:44 PM »

Mach4 screen editor crashes when a few items are deleted.

Upon restart, sometimes the last couple edits are there and sometimes not.

It is completely random, so no clues to provide.

Win7 Pro 64bit

105
Mach4 General Discussion / Re: Mach 4 Bug Reports
« on: April 06, 2015, 06:54:13 PM »



The 'gauge' screen item does not seem to work at all. 

106
Attached video shows the completed spindle power monitoring.

I have been unable to get the 'gauge' screen item to work at all, but I am developing some tricks to make interesting 'gauges' using different techniques as shown in the attached video fragment.

The analog data is being collected by the Arduino DUE board which does the A/D conversion and maps the values to  0 thru 150%  and ships them across TCP Modbus to a DRO on the MACH4 screen. The PLC program grabs the data from the DRO and controls the 'gauge' bar and the warning light.

The percentage can be a percentage of the maximum or a percentage of the current torque limit setting, which I have in mind to use for rigid tapping.

I *think* I saw a bunch of user accessible data fields in the tools data base, so if that is correct, then each tap size can have an associated torque limit as a parameter and that could be sent to the spindle drive and the displayed torque range could then display from 0 to 1XX% of the torque limit.

With that scenario, the drive could be relied on to fault if the torque limit was exceeded -or- the Torque limit data from the tool table could be used by the script to pause the running G-code if the torque limit is exceeded for the particular tap being used. The pause and associated error message would allow the operator to change the tap and then simply continue along instead of tracking back the line of untapped holes like following bread crumbs until you find the one with the snapped off tap stuck in it.

There are a lot of other interesting and useful things that can be done with the spindle load data once it is in MACH . .  which is now is.

107
Mach4 General Discussion / Re: MACH4 - Modbus
« on: March 23, 2015, 06:34:01 AM »
There is no such thing as an analog register in Modbus . . .

Certainly not per Modbus spec. I think maybe what I was reading was just a reference to a Modbus 'analog' register was just descriptive of the use of the register for xfer analog data (after A/D). I have a separate thread going about getting analog into MACH4 in general. I just posted here specifically about Modbus.

The application is a 0-10V DC signal from an Industrial AC servo drive that tracks motor load. The solution does not need to be Modbus. A plug-in is fine so long as it is stable and not serial interfaced (including USB). So far the options I have collected are the analog inputs on the Arduino DUE processor board in my 4th axis motor controler, and a Pokeys board.

Does Homann have a solution that will accept a 0-10v DC signal and connect via Ethernet?

108
Mach4 General Discussion / Re: Lua 5.3? Yes, No, When?
« on: March 22, 2015, 07:38:57 AM »
This is likely dependent on the release of Lua 5.3 support by the wxLua wrapper
which provided the binding between wxWidgets and Lua.

http://wxlua.sourceforge.net/

Not quite yet:

"wxLua can be built against wxWidgets 2.8.x, 2.9.x and Lua versions 5.1, 5.2, and LuaJIT."

109
Mach4 General Discussion / Re: Display html page using LUA
« on: March 22, 2015, 07:05:01 AM »
Attached program runs in MACH4 so the Lua calls are there. Should get you started.

Note remove .txt from then  of file name. Added to get forum to take the file

110
Opps. The $89 analog input device is serial interface. Really don't want to mess with converters, drivers, etc.