Topics

1

HiCON Motion Controller / Homing not working - Using version 2.50.23 firmware, with mach 4.2.0.4300

« on: February 02, 2021, 02:22:19 PM »

My computer quit last week and I had to move everything to a new computer. homing worked on the last machine.
Before the machine completely stopped working I managed to copy the profile folder from mach 4.

I installed mach 4, copied in the plugin files, and copied my profiles over to the new computer.

Problem. I can jog the machine in all directions, but when I hit "home all" the z axis moves very briefly (not getting to the switch) and stops. Then I get the error "motor not enabled" for all the motors.

If I enable the machine again I can run gcode as long as I don't home the machine.

System specs
Windows 10 pro 64bit.
I attached a screen shot of the black window that is usually open in the background, and the text log of events from diagnostics.

Steps taken so far.
1. I updated the hicon firmware to version 2.50.23 today, but the same problem occurs.
2. I updated the config files inside the plugins folder as well.
3. scrolled through the motors settings and all the appropriate boxes seems to be enabled inside of motors, axis mapping,
4. Restarted the controller and computer just in case.

2

HiCON Motion Controller / THC setup Sequence Aborted- Arc Pro combo package

« on: January 17, 2020, 12:32:22 PM »

I have not be able to get this system to work since I bought it. This is a link to the first time I reported the problem. I have upgraded windows since then and the type of error has changed. https://www.machsupport.com/forum/index.php?topic=41710.0

Problem:

At the start of a program the THC sequence begins...the torch moves down, the probe is active, the torch moves up. and then the sequence is aborted.
This happens "almost" every time. Sometimes it will fire the torch and immediately shut off the torch and abort.

Other relevant details.

-The probe signal alone seems to work fine. If I activate it, both Mach 4 and the controller board light up.
-Even if I turn off the THC on the panel it runs the probe sequence but continues to push into the plate requiring e-stop to quit.
- I had to create a different profile in Mach 4 to test everything else. It runs the gcode and cuts the plate without a problem setting the height manually.
-Attached are screen shots of computer specs, the last sample G-code etc.

Things I have tried.
-Restarting everything
-GCode with only "M03" inside it
- Double checked the wiring.

3

HiCON Motion Controller / Mach Four Crashes at Digitize (probe) signal

« on: August 30, 2019, 10:54:16 PM »

I have a hicon ingera (the newer black one).
Windows 7 Professional 64 bit
Intel I7
2.8 ghz
The "probe" input is wired to #8 shown in the picture J13 inputs. I unplugged the Relay input for the torch to take a clearer picture.

The probe signal alone seems to work fine. If I activate it, both Mach 4 and the controller board light up.

I tested it repeatedly with nothing but "M03" as the G code.

The torch moves down and as soon as the probe is active, the torch stops moving and mach 4 crashes.
It happens every time.

There is nothing in the history readout at the bottom, and no error messages from windows.

I tried restarting Mach 4, restarting the computer, and using a different input on the Hicon.

Interesting side note. even if I turn the THC off it still tries to probe. I crashed my torch into the table 3 times because of this. After that I stopped trying. Of course I would like to use THC, but I can't even turn it off temporarily to manual set the height. I had to exit and setup another profile to get around the THC function.

4

HiCON Motion Controller / Is closed loop package required for use with Servo motors and drivers?

« on: April 18, 2019, 10:26:26 AM »

I currently have brushed DC servo motors and drivers (DG4S-08020 DC Servo Drive). I want to use them with the Hicon Integra 6 axis controller. Do I have to purchase the closed loop package?

I am new to this, but it seems like the driver is reading the encoder input and there would be no need to send that information to the controller directly.