Hello Guest it is February 18, 2020, 05:54:37 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 - marc1b

Pages: 1 2 3 »
1
HiCON Motion Controller / 7736 and Mach 4
« on: April 22, 2019, 08:43:14 PM »
I am upgrading my Mach 3 (originally installed in 2014) with an Integra to Mach 4 and so far no joy on spindle and axis. I have the limit switches and outputs for coolant, etc working fine. In the diagnostics I do see the motors are enabled when the drives are. But there is no movement.

I have downloaded and installed the latest plugin & firmware (2.03.07)

The current Integra manual shows a 7737 encoder board and I have a 7736. Is this going to work for me? If so what is the mapping as to the drives and encoders?

Thanks!!

2
I decided better to move forward than backwards, I am upgrading to Mach4

3
I have the same issue, can you tell me what you needed to change? Big thanks!

4
I have found a few differences in the pin mapping between the older version of the 7737 manual and the newer. Is there something I should be changing here?

5
HiCON Motion Controller / No motion after Hicon Integra update - Mach3
« on: April 22, 2019, 11:58:35 AM »
In the process of chasing down a problem with interpolating a circle I updated the firmware to 3.26b and .xsvf to IntegraFPGA_7E7B

Integra 7766 & 7737 ,  Maxsine drives & motors

Aside from the circle error everything was fine before the updates. I am embarrassed to say that I didn't make a record of the motor settings in the Hicon plug in and I am pretty sure that is where my problem is. What should the index & output be for 3 axis?

6
I just need to get pointed in the right direction -


I have a Bridgeport Series 2 with air assist on Z axis. If we turn the air off over night and forget to lock the knee the Z will wind up at the bottom of it's travel below the limit and homing switches.

So I want to have the homing routine look at the current position variable, add to it and make a small move to get it above the switches.

Thanks!

7
HiCON Motion Controller / Re: Motors won't sit still
« on: February 04, 2018, 11:54:34 AM »
Got it figured out. I had to set the drives to the correct model motors and be a little less aggressive with my tuning in the drive.

8
HiCON Motion Controller / Re: Motors won't sit still
« on: January 31, 2018, 03:51:19 PM »
Yes I can understand that but this is a live machine. Did not have this problem with the previous drives. And does not do it unless Mach is running. See videos here

https://drive.google.com/open?id=1uIjDfTO16HN-9hBmevzmx6gnxvB7Rluw

9
HiCON Motion Controller / Motors won't sit still
« on: January 31, 2018, 11:51:47 AM »
I have been running my Mach3/Intergra (closed loop option) machine for a few years no problem with Maxsine drives & servos. A drive recently failed and I changed drives to the next larger model (TL10F to TL15F) which required setting parameters and  re-tuning the drives. So I got that all done and everything mostly works.

However when Mach is running the DRO's for X & Y are bouncing around by .0001 or so. There is a monitor utility in the Maxsine software that confirms the motors are actually moving. If I kill Mach the movement stops. I'm trying to figure out what I missed.

Thanks for any input!

10
General Mach Discussion / Machine loses position on first load of Mach3
« on: August 30, 2014, 10:23:47 AM »
Not sure exactly how to describe the subject

We just completed a refit of our Series 2 Bridgeport using a Hicon motion controller, servos and drivers. All that stuff works great.

We are not homing the machine currently or using any offsets currently, we just move the machine to where we want X, Y & Z 0 then click the Zero x, y & z buttons.

Next we load a program and run it.

We found out the hard way that the first time the program is run the axis 0 positions have somehow changed. If we re-zero it and run again it is fine. It's also fine if we load and run a different program. It is fine all day, the only time it does this is if we close Mach and restart it.

Something tells me it is related to not homing the machine.

Pages: 1 2 3 »