Hello Guest it is March 28, 2024, 03:36:57 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.


Topics - boilerbots

Pages: 1
1
G-Code, CAD, and CAM discussions / Mach pukes on this code.
« on: March 30, 2009, 05:44:40 AM »
Something to do with the Macro call at line 353. I am using Mach3 R3.042.024 and the only option I had was to disable macros in my post processor and re-generate.

I later experienced a problem with a macro call where the line following the macro return is skipped. So maybe this is related to that failure.


2

<a href="http://www.youtube.com/v/tTDpoNrs7rI&amp;hl=en&amp;fs=1&amp;rel=0&amp;border=1" target="_blank" rel="noopener noreferrer" class="bbc_link bbc_flash_disabled new_win">http://www.youtube.com/v/tTDpoNrs7rI&amp;hl=en&amp;fs=1&amp;rel=0&amp;border=1</a>

This is a very old Wells Index mill that I reworked the electronics. It has the original steppers, Gecko drives running at 76V, and a SmoothStepper. I am using Mach3 right now to interpret the G-code. This short clip is that last little bit of roughing and then a quick finish pass at my max speed of 100IPM. I am cutting with a 0.625 dia Cobalt 3 flut end mill and this let me tell you it can slice this aluminum like butter. I tool path is setup to limit peak spindle horse power to about 1.3Hp, I have a 3Hp spindle but I don't like to push it.

Curt

3
Hi,

I have a real problem but I am not sure it belongs to Mach3 or Warp9. I am running a SmoothStepper on my mill.

When an axis is moving, sliding the FRO up or down causes such an abrupt change in velocity that I will loose steps or sometimes totally loose coupling (is that the right word) with the stepper phases. Adjusting the FRO appears to totally ignore the acceleration parameter and will just jump to the new speed.

It would be really great if I could get this solved. I would like to be able to take the feed rate up and down dynamically as the program is running for safety reasons, like when running close to a clamp or fixture for the first time.

Maybe there is a way I could fix this in a Macro or Brain thing?

I plan on cutting a lot tomorrow so shoot me some ideas please......

4
This is somewhat strange and maybe I am trying to do something that just isn't possible yet but it almost works.

What I am trying to do (in two parts). I have a VFD for my spindle that I communicate with via Modbus. Without enabling any thing on the Spindle config screen I was able to get it somewhat working. I configured the Modbus and then modified the M3, M4 and M5 VB scripts to set the appropriate bits. I also modified the spindlespeed script to calculate the appropriate value to send out and then send it. I am able to use the MDI screen and execute these scripts and they work fine. I can execute G code programs and they work fine.

What doesn't work is using the Spindle controls on any of the screens. Pressing the Toggle spindle button or F5 doesn't get any action on the GUI. This is probably caused by some code dependency on the Spindle configuration in the Config menu (proven below).

Next I wanted to configure three OEM inputs to run the spindle forward, reverse and stop. These are existing buttons on the control panel on my mill so I figured why not. I mapped them to the OEM codes for CW(110), CCW(173) and I couldn't use Spindle stop because the above are toggles. Not surprisingly it didn't work. It probably doesn't work for the same reason as the GUI buttons also don't work.

Second experiment. I setup Output 4 to map to the Modbus bit that enables the VFD. In the spindle configuration I enable the spindle relays and set both CW and CCW to #4. I enable Modbus Spindle control and set that to #64. I do not enable the spindle motor output because that forces me to assign it output pins for step and direction.

Now the GUI button can at least turn the spindle on/off and control the speed. Also the OEM buttons will cause the spindle to toggle on/off like the GUI. There isn't a true Enable/Disable signal in the OEM codes. In Modbus land Enable is a bit, Reverse is a bit and the speed is a register value. The available codes in Mach don't exactly map to the Modbus control of a VFD.

Another problem with this configuration. The M3, M4, and M5 scripts don't work anymore which means that G code won't be able to control the spindle. When you execute a script it changes the state for a brief instant. It appears that the script changes the internal state of the modbus bit and then something else comes along and wipes it out. I would guess that it is the update from the GUI that overwrites the memory with the state it currently wants to be in.

The questions:
  • What is the best way to solve this problem?
  • If I forget about the OEM buttons, how do I get the GUI and the M3 and M4 scripts to work properly?
  • Would a Brain controller have the ability to solve this problem?

Thanks for any suggestions.

5
Modbus / Modbus setup screen is different than documented??
« on: May 23, 2008, 07:10:59 AM »
I am trying to configure Modbus to control my VFD. It appears that the Modbus screen has been changed since the documentation was done.

All I need to do is write to the first 4 coil registers on my VFD. I can control the VFD through the mod test screen without any problems. How do I translate the address and register locations used in the test screen to the modbus config screen?

I have tried executing a VB script I wrote and nothing is happening. Can you provide some suggestions?

Pages: 1