DEK265gsx inconsistency in management f

Views: 5111

Hi All im facing an issue with my DEK. Once the middle ... - Feb 22, 2007 by vshan  

My guess from your description is that you're talking about ... - Feb 22, 2007 by DEKHEAD  

me yusta werk for dek. dek dood. mpm bad ... - Feb 22, 2007 by

Your vocabulary is improving Tim ... - Feb 22, 2007 by DEKHEAD  

TIM I AGREE WITH U BIG TIME. I CANT STAND THE MPM SCREEN PRI... - Feb 22, 2007 by

but the problem is the stopper comes down only after the boa... - Feb 22, 2007 by vshan  

Software version running? Is this on one product or all pro... - Feb 22, 2007 by DEKHEAD  

yes left to right sensor on left feed whatelse next can ... - Feb 22, 2007 by vshan  

software v4.03 ... - Feb 22, 2007 by vshan  

What software version is running? Assumption it is runnin... - Feb 22, 2007 by DEKHEAD  

v4.03 yes ul protocol under manual currently we are runnin... - Feb 22, 2007 by vshan  

If protocol is already manual, does conveyor start when "RUN... - Feb 22, 2007 by DEKHEAD  

if No FMI is that every cycle we have to press confirm, if y... - Feb 23, 2007 by vshan  

Does your camera / stopper move to a spot where it can catch... - Feb 23, 2007 by Real Chunks  

SRM, you and Tim gonna share a Snickers? LOL! I LOVE T... - Feb 23, 2007 by Real Chunks  

Are you saying that it works in "no fmi" mode, but not in ma... - Feb 23, 2007 by DEKHEAD  

As you are running Left to Right it is the trailing edge of ... - Feb 26, 2007 by

vshan

#47917

DEK265gsx inconsistency in management f | 22 February, 2007

Hi All

im facing an issue with my DEK. Once the middle sensor detects the board, the stopper does not able to stop the board on time.

i have checked all the basic parameters. Can anyone help me

rgd vshan

reply »

DEKHEAD

#47918

DEK265gsx inconsistency in management f | 22 February, 2007

My guess from your description is that you're talking about the board at stop sensor (mounted on camera) that is seeing the board, but the board edge is not hitting the stopper. Either the board stop is not extending fully, or the board is sagging and thus sliding under the stop. If the former, possibly bind in the bearing (may require replacement) or possibly the bearing downstop "twisted". If the latter is the case, try moving the "Y-Board stop" position closer to the board edge (increase the value from the 2/3 BW default value).

DEKHEAD

reply »

Tim G

#47919

DEK265gsx inconsistency in management f | 22 February, 2007

me yusta werk for dek. dek dood. mpm bad

reply »

DEKHEAD

#47921

DEK265gsx inconsistency in management f | 22 February, 2007

Your vocabulary is improving Tim

reply »

SRM

#47922

DEK265gsx inconsistency in management f | 22 February, 2007

TIM I AGREE WITH U BIG TIME. I CANT STAND THE MPM SCREEN PRINTERS. MY DIMINUTIVE COLLEAGUES SWEAR BY THE MPM - SOMETIMES LITERALLY HA-HA-HA-HA-HA - BUT DEK'S HAVE FEATURES GREAT FEATURES THAT MPMS DON'T HAVE. THE SOFTWARE ROCKS! LOVE IT!

reply »

vshan

#47924

DEK265gsx inconsistency in management f | 22 February, 2007

but the problem is the stopper comes down only after the board pass thru

rgd vshan

reply »

DEKHEAD

#47926

DEK265gsx inconsistency in management f | 22 February, 2007

Software version running? Is this on one product or all products? Left to right feed? If yes, is board at left sensor being keyed? Right to left feed? what is setting for "right feed delay", increase it?

reply »

vshan

#47927

DEK265gsx inconsistency in management f | 22 February, 2007

yes left to right sensor on left feed

whatelse next can do

rgd vshan

reply »

vshan

#47928

DEK265gsx inconsistency in management f | 22 February, 2007

software v4.03

reply »

DEKHEAD

#47930

DEK265gsx inconsistency in management f | 22 February, 2007

What software version is running?

Assumption it is running with FMI, what is UL protocol?

Change UL protocol to "Manual", belt should not start running until board is placed over sensor, confirm!

All products or just 1? What is board width of current (or problem) product.

reply »

vshan

#47931

DEK265gsx inconsistency in management f | 22 February, 2007

v4.03 yes ul protocol under manual currently we are running with only one product Board width is 150mm

reply »

DEKHEAD

#47932

DEK265gsx inconsistency in management f | 22 February, 2007

If protocol is already manual, does conveyor start when "RUN" is pressed (without board on rail)? Or does it not start until board is placed?

Try running UL protocol as "No FMI", put in run without board on rails, place board, press "Confirm". Board stop should lower, belts should start.

reply »

vshan

#47934

DEK265gsx inconsistency in management f | 23 February, 2007

if No FMI is that every cycle we have to press confirm, if yes it will effect during production mode

rgd vshan

reply »

Real Chunks

#47937

DEK265gsx inconsistency in management f | 23 February, 2007

Does your camera / stopper move to a spot where it can catch the boad when the middle sensor is triggered? It sounds like you may have your board stop coordinates wrong. Check your X measurement to be sure.

reply »

Real Chunks

#47938

DEK265gsx inconsistency in management f | 23 February, 2007

SRM, you and Tim gonna share a Snickers?

LOL! I LOVE THAT SAYING!

reply »

DEKHEAD

#47942

DEK265gsx inconsistency in management f | 23 February, 2007

Are you saying that it works in "no fmi" mode, but not in manual? Please tell me how it works in both.

I'm asking you to change things to ascertain the problem, not as possible solution... if you can't get the board to stop in the correct position, that is probably impacting the pulse rate of your line as well.

reply »

JCB

#47979

DEK265gsx inconsistency in management f | 26 February, 2007

As you are running Left to Right it is the trailing edge of the board leaving the board at left opto that tells the board stop to lower (not the sensor under the camera - that just confirms the board has arrived at the board stop). How big is the board and how fast are the transport belts running? Other things to try would be turn Event Logging OFF and also edit the Autoexec.bat and at the very top add the command SMARTDRV this enables fast disk caching. Either of these two items could cure the problem because it maybe trying to write Events to the Hard Disk when it is supposed to be telling the board stop to lower.

reply »