Hello Guest it is March 28, 2024, 08:04:32 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 - Vital System Support

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 »
211
HiCON Motion Controller / Re: Active low probe / touch plate
« on: November 02, 2015, 12:40:58 PM »
Hello Jerry,

In the Mach3 plugin, you can go to the "Ports and Pins" config. From there, go to the "Inputs" tab. You should see a list of signals which you can tie the device inputs to, as well as an "Active Low" signal for each one.

Basically, for those signals that are connected to Digital Inputs that are active low, you can toggle the signal active low state from here.

-Marc
Vital System Inc.


212
HiCON Motion Controller / Re: hicon session id mismatch
« on: October 31, 2015, 05:41:14 PM »
please use the plugin and firmware available on the hicon integra web page

www.vitalsystem.com/integra#downloads

and click on the Integra Mach3 Plugin and Firmware.

The default firmware shipped these days is for mach4.  so you will need to update to the plugin and firmware available in the above download.

thanks
VSI Support

213
There are updates happened internally that are not yet uploaded on the main page. sorry I was in the impression they were there. here is the link to download http://www.vitalsystem.com/portal/temp/ArcProIntegra-1.06.zip

Based on our internal testing, we do not observe the gcode line skipping issue any more.

If you do see any issues please provide the following:

zipped profile folder
gcode program and line number where you see the issue
copy of custom screens (if any)
any other plugin aside from default mach4 plugins

will appreciate if you provide brief to the point info so we can assist you better. long essays just makes the job even harder.


 

214

Please download the latest mach4 software and also the latest plugin from our website.  There had been many updates that happened between now and last few weeks.  Please let us know what error are you seeing so we can narrow it down and try to resolve it.

regards
Rufi


215
we are working with mach4 developers on a daily basis to find a solution for this issue.  should have something solid by next week.  This problem is only showing up when the controller itself generates motion, aside from mach4 motion planner.

216
Here is another temporary fix that is shared by Aaron to avoid skipping the gcode line after M05.

...I tried out your doubling up of the g-code so that it would not miss a line. This worked 80% of the time. After about 5 min, it would do it again.... So this is what I found:

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 100ms. This works %100. No problems at all. It will go for an hour and not skip a line. My look ahead was setup for "5".


217
HiCON Motion Controller / Re: M Code "Handshake" – Need Help
« on: October 05, 2015, 04:11:17 PM »
Hello,

You should be able to find a "Scripting Manual.pdf" within your Mach4 installation directory (Mach4Hobby/Docs/Scripting Manual.pdf). In that manual, a good example can be found on page 18.

Additionally, a "LuaCalls.txt" file can be found in this same directory which contains all the available scripting commands.


local inst = mc.mcGetInstance()

local hsig = mc.mcSignalGetHandle(inst, mc.OSIG_SPINDLEFWD)

local spinstate = mc.mcSignalGetState(hsig)

if (spindstate == 0) then
      mc.mcSignalSetState(hsig, 1)
else
      mc.mcSignalSetState(hsig, 0)

end



In the case of your "Laser Ready", you can use one of the generic signals (e.g. ISIG_INPUT0 etc.). The same goes for the output that you'd want to activate (e.g. OSIG_OUTPUT0 etc.)

For waiting, you can keep checking the state of your input under a  while loop and using a sleep.

input1State = mc.mcSignalGetState(input1Handle)

while input1State <> 0 do

     wx.wxMilliSleep(100)
     input1State = mc.mcSignalGetState(input1Handle)

end

 mc.mcSignalSetState(output1Handle, 0)



I do recommend that you go through the documents that I had mentioned above, otherwise my explanation may make little sense without prior knowledge of how lua scripting works in Mach4.


-Marc
Vital System Inc.

218
on the plugin system tab, there is an option to enable debug window.  then restart mach.  you will see a black window show up.

EDIT: This issue was resolved by a Mach3 plugin and firmware update

219
can you send the log on the black debug window?  it will help narrow down the issues.

220
That isn't an error with the limits. It's an error that's generated when the difference between the actual position and the command position goes beyond the configured threshold. This is most likely due to an axis configuration error in the plugin config. Verify that the "Axis Feedback Type and Index" are correctly set, as well as the "Max Following Error".

Another error could be your Motor tuning config. Check that your motors can actually handle the velocity and acceleration that you had configured there.

Please consult page 25 of this manual on how to correctly set up the axis config in the plugin tab.
http://www.vitalsystem.com/portal/motion/hicon/HiCON_Mach3_Software_Integration.pdf

EDIT: Oh, and make sure that you're using the latest Mach3 plugin and firmware available from our website.

-Marc
Vital System Inc.



Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 »