Messages

231

HiCON Motion Controller / Re: Significant Problem - Mach4 freeze on M codes

« on: September 14, 2015, 12:47:23 PM »

Hello,

Unfortunately, the bug with the motion sync isn't completely fixed. I had hoped to get a complete fix before posting a reply on this thread, but it looks like things are getting delayed. Right now, Mach4 build 2686 should be available on the web and it should prevent the GCode interpreter from getting stuck, but instead of getting stuck, it may skip GCode lines instead.

However, there is a work-around available that can be done to avoid skipping the gcode line after M05


If you place another M code right after the M05, like so:
M05
M2001 (has a milisleep inside)
G00 x1 y 1 z0
m03

Inside the M2001 I put a milisleep function of 10ms. This works %100. No problems at all. It will go for an hour and not skip a line. look ahead was setup for "5".


I'll also post a another notification on this thread once the bug is completely fixed and this workaround is no longer needed.

If this still doesn't solve the problem, then email me your GCode file (support at vitalsystem dot com) and I'll try running it here myself. Oh, and I'll also need those "custom macros", and your profile as well.


-Marc
Vital System Inc.

232

HiCON Motion Controller / Re: Significant Problem - Mach4 freeze on M codes

« on: September 08, 2015, 02:31:17 PM »

Hello,

I ran into a bug during testing that involved the Mach4 GCode Processor getting hung up with an MCode command (I think this is also what you're seeing). This was due to Mach4 waiting on a response from our plugin, but the problem is that the plugin never got a corresponding request from Mach4. We were able to track down the problem to the Motion Sync, and are now working with the Mach4 team to fix it.

Right now, I'm waiting on a new build from them, but I'll reply on this thread when the problem gets fixed.


-Marc
Vital System Inc.

233

General Mach Discussion / Re: Recommendations on BEST Breakout Board by General Mach3 Users !

« on: September 02, 2015, 04:50:18 PM »

Like to bring our Integra Controller + Breakout into the mix here:



We are working closely with Mach developers to match latest Mach4 releases.  We provide feature rich plugin, outstanding support and USA made high reliability hardware systems.

regards,
VSI Sales Team
www.vsys.co/integra

234

HiCON Motion Controller / Re: Mach4 Build 2660 and HiCON MPG

« on: August 31, 2015, 08:37:21 PM »

If you have more counts per unit on the axis motors, you can achieve even better mpg click resolution.

235

HiCON Motion Controller / Re: Mach4 and HiCON -

« on: August 31, 2015, 12:03:49 PM »

Hello,

The first message indicates a slow-down of the data exchange rate between Mach4 and the motion controller which usually appears when Mach4 is just started up, or if a connection is first established by the controller, in which case is pretty normal. However, if it occurs during normal operations, it could indicate that there is an issue with the network connection.

The 2nd message is a result of the plugin waiting for motion buffer to be consumed by the controller, and not any data loss over the network. This is evident with the "Motor Set Still..." message for motor1 which can only be triggered if the controller has successfully processed all the necessary motion. In the plugin, there are sequence number checks to ensure that each and every move vector is processed by the controller and no packet is dropped.

In the debug window, instead of calling it "SET STILL DELAYED.." it should be something like "WAITING FOR MOTION COMPLETION..."  Will try to update it in the next release.

So the answer to your question is that these conditions that are being 'reported' do not need to be corrected

Regards
Vital Support

236

HiCON Motion Controller / Re: Easy questions on continuous rotation axis

« on: August 24, 2015, 02:06:16 PM »

Hello,

I just finished speaking to one of the Mach4 guys, and it looks like there is simpler way this can be accomplished.

You can use this function mcJogVelocityStart(MINSTANCE mInst, int axis, double dir)

Essentially, what you would need to do is map the 4th axis to one of the OB axes (these would be axes 6 - 11), then create a script/macro with the above function. According to what I was told, this velocity jogging works independently of the normal motion, so it should be exactly what you need.

You could also use these functions if you need to map/unmap a motor in order to perform GCode motion with it.
mcAxisMapMotor(MINSTANCE mInst, int axis_id, int motor_id)
mcAxisUnmapMotor(MINSTANCE mInst, int axis_id, int motor_id)

I've never used this myself, to be honest, so let me know how it goes.

-Marc
Vital System Inc.

237

HiCON Motion Controller / Re: Easy questions on continuous rotation axis

« on: August 24, 2015, 01:52:41 PM »

Hello,

The best way this can be accomplished is by using the HiCON Macro feature which allows you to write programs, download them to the motion controller, and execute them alongside Mach4. This feature was originally added to the HiCON platform to overcome the limitations posed by Mach3, and in your case, you want a feature that Mach4 cannot currently support (which is independent axis movement outside of the Mach4 motion planner).

With the HiCON Macro, you can simply write a short script that commands, what we call a "Velocity" move which moves a motor independently in one direction (according to a specified acceleration and velocity). This behavior can then respond to maybe a digital input, or one of the userLEDs in order to start or stop.

In Mach4, you can then write a custom script/macro that will map/unmap the motor from the axis and issue the "Velocity" movement when necessary.

Here is the user guide for creating macros in BASIC
http://www.vitalsystem.com/portal/motion/hicon/HiCONBasic.pdf

Here is the user guide for creating Macros in C
http://www.vitalsystem.com/portal/motion/VSI_CMacro_Documentation.pdf

The HiCON Macro feature does require an additional purchase which you can make from the Integra webpage. Just scroll down to the purchase listing and the item should be labelled as "HiCON-MACRO".

This may be a lot to take in, so feel free to reply if you have any questions.

EDIT: with the above behavior, you wouldn't need to disconnect the encoder feed back with your specialized circuit as a "Velocity" move will sync back the axis position (commanded, and feedback/encoder positions) when stopped. This means that the encoder position will not be at an extremely high value when you re-map your 4th axis for GCode control.

-Marc
Vital System Inc.

238

HiCON Motion Controller / Re: HiCON Integra - MACH4 - Servo Spindle - Assigns spindle as slave

« on: August 24, 2015, 01:07:33 PM »

Hello Steve,

Yes, I think I can see what the problem is now since we always intended the GCode Spindle to be mapped to an axis. I can make a fix so that the axis mapping/remapping doesn't occur unintentionally if an axis was never originally specified. In the meantime, try mapping the spindle motor to an unused axis like say Axis C and see if that resolves the issue (just so I can verify that this is indeed the problem). I'll post an update if a fix is made, and I'll send you a notification as well.


-Marc Lim
Vital System Inc.

239

HiCON Motion Controller / Re: HiCON Intergra Card.

« on: August 24, 2015, 12:42:06 PM »

Hello Mauri,

We really appreciate you taking the time to write this honest and good review, and of course, the time you had spent working with the HiCON Integra. 

I'd like to clarify the current issue with the MPG as it also encompasses incremental/step jogging (or relative motion in general) for those who may be seeing a similar problem.

It appears that the current version of the Mach4 motion planner generates a trajectory that can be 1-2 counts off the intended target (this was verified in our testing when we checked the vectors that Mach4 was plotting). This is NOT present, however, with absolute position as it appears to be spot on to the very last count according to what we've seen with testing. This may or may not be a problem depending on the required level of precision, but it is clearly a concern for your application. As for the solution, we've brought up the problem with the Mach4 development team, and they're currently looking into it. We're still waiting on a response if the fix ought to be in Mach4, or if there is something that can be done from our plugin.

Thank you for your patience, and we'll upload the update once this issue gets resolved.

-Marc
Vital System Inc.

240

HiCON Motion Controller / Re: Easy questions on continuous rotation axis

« on: August 24, 2015, 12:30:48 PM »

Hello simpson26,

To answer your questions:

1. Im not sure if you mean that you want multiple GCode Spindles, or if you want another motor to be slaved to the GCode spindle? I believe the 2nd can be accomplished.

 - In the Mach4 config, make sure that all motors in question are enabled and properly configured.
 - In the plugin config, make sure that all the motors are configured (GCode Spindle too) as indicated in the Mach4 integration manual.
 - Go to the motor tab for the other motor, and set the command input index to that of the GCode spindle motor.
 - You should have the slave motor mirror the command position of the GCode spindle.

If this isn't what you're looking for, then please explain your requirement in greater detail so I can instruct you accordingly.

2. The axis "letter" for the spindle axis in GCode is the axis where the GCode Spindle motor is mapped to. The GCode spindle must be assigned to an axis in the Mach4 axis mapping in order to receive the corresponding GCode axis command. For instance, if you set Motor5 as the GCode spindle, and you mapped Motor5 as the master motor of Axis C, then a command like "G0C5" will move the GCode spindle motor to 5 units.


- Marc
Vital System Inc.