PDA

View Full Version : Intermittent Z-Zero issue with MTC, and Link.



michael_schwartz
05-13-2012, 07:31 PM
The E-cab link itself seems to be working fine. So far I have used it to cut all the parts for a kitchen. As far as I am concerned it has paid for its self the first week I have had it, and I am very impressed. I will share details of the project I am working on soon.

Now the odd part is that I have the MTC routine setup to where it works most of the time. However There seem to be some "gremlins" at play.

Every, 3-4 sheets, after the MTC routine runs, the SB control software seems to
to loose the &zero_to_bed variable, and &z_adjust value, when I get to the second bit change. This results, in the machine zeroing to the spoil board, as if it were the top of the material.

From my understanding of SB programing, I am assuming this means that something may be overwriting those specific variables. I have observed this, by checking the current variables, utility, after this happens. Maybe this isn't the case. I am not sure.

The only way I have been able to "repeat this" is that it seems to happen every few sheets, that require a bit change. If I air cut long enough, I can usually make it happen. Otherwise, I have not been able to find anything that causes this.

I haven't ruled out static, USB, or other interference but everything else seems to be working perfectly fine. That also means no com errors under normal circumstances, unless SB3 crashes due to some abnormal circumstance. I have been jogging at 8 IPS, and pushing the upper limits of cut speeds for a couple months now.

I am pretty sure that this is not caused by an inadvertent Z plunge, or the bit slipping out of the collet.

I have my dust shoe isolated and grounded back to the system ground, at my dust collector. I have gone over all my wiring to make sure nothing runs parallel to power cables.

Again my experience has been that the current PC, I am running has been quite robust. I bought it, before I planned to purchase the link and If It really isn't up to the task of running the link, I am open to the idea of replacing it. Specs are 1.8ghz core 2 duo. I ordered 4gb of ram for it the other day. It currently, only has 1gb, which I am aware, is less than what is recommended. I have been keeping an eye on usage though, and I haven't seen anything that would indicate that that has caused a problem. It seems to do fine nesting, as is.

For all I know this could be "instability" caused by a windows issue.

I have spent about 10 hours trying to figure this out, and I am perplexed. Maybe I am missing something obvious.

garyc
05-13-2012, 09:59 PM
Michael...
Open the MTC, MtCon and MTCoff files in the SBeditor and search for the term "&zero_to_bed = 0". If found, then figure out the circumstance that would cause that line to change the variable from 1.

The only way I can guess that this would happen is if you answered the "Did you zero to bed?" with no. IF so then this would be the expected results.

2006prt
05-13-2012, 10:01 PM
Michael,

I have had the same issue in the past. I have a work around that is working fine, but when I started running ecabs I had the same issue and burned up my spoilboard with a deep plunge. I think it is in the software and not the hardware or static. Just my two cents, you are not alone. My work around is probably not applicable for you so I won't describe it here. There are many more qualified people to help you, but if you have any questions that I can help you with feel free to reach out.

Todd