LitePlacer.com forums

Posted: **Wed Jul 19, 2017 3:41 pm**

hey guys
I have a problem, which is very weird.

from time to time, when the head goes with a component on the nozzle, randomly head stopped in the middle of the way and sw gives "CNC connection cut".
do you have some experience with that? there are no specific time or action when doing it, its totally randomly.

similar problem happening during height measurement, when nozzle goes up from placed component and it gives an error but the reason is unknown.

where can i find a cause of these problems?

Posted: **Wed Jul 19, 2017 4:02 pm**

The log window content and the TinyG LED behavior might give a hint. Next time this happens, take a copy of the log window (last few lines should be enough) and make a note about the LEDs and email me or post here.

Most likely cause is insufficient shielding of motor (noise source) and limit switch (noise victim) cables causing false triggering, or the tube movement not being loose enough and leaving the Z max switch close to activating (and triggering at a wrong moment).

Posted: **Fri Jul 21, 2017 10:24 am**

after error the red led blink few time and after that start blink green ones and head move in +x and +y at the same time cca 200mm

i dont think that content log give will be helpfull buet here is it:

Code: Select all

{"r":{"fv":0.970,"fb":438.02,"hp":1,"hv":8,"id":"3X3566-KYP","msg":"SYSTEM READY"},"f":[1,0,0,6925]}
==> {"gc":"G0 X113.246 Y120.577"}
tinyg [mm] ok> 
qr:32, qi:1, qo:1
{"r":{},"f":[1,0,30,131]}
PutPartDown_m(): Probing placement Z
Probing Z, timeout value: 10
### {"zsn",0} ignored, cnc is in error state
### {"zsx",1} ignored, cnc is in error state
### {"zzb",0} ignored, cnc is in error state
### {"gc":"G28.4 Z0"} ignored, cnc is in error state
### {"zsn",3} ignored, cnc is in error state
### {"zsx",2} ignored, cnc is in error state
### {"zzb",2} ignored, cnc is in error state
{"sr":{"posx":0.000,"posy":0.000,"posz":0.000,"posa":0.000,"feed":0.00,"vel":1.39,"unit":1,"coor":0,"dist":0,"frmo":1,"stat":5}}
{"qr":31,"qi":1,"qo":0}
{"sr":{"posx":9.191,"posy":9.786,"vel":12072.89}}
{"sr":{"posx":53.894,"posy":57.383,"vel":24139.54}}
{"sr":{"posx":101.824,"posy":108.415,"vel":14241.25}}
{"sr":{"posx":113.239,"posy":120.569,"vel":102.71}}
{"sr":{"posx":113.246,"posy":120.577,"vel":0.00,"stat":3}}
ReadyEvent stat
{"qr":32,"qi":0,"qo":1}
###{"gc":"M05"} discarded, error state on
CNC_XY_m, x: 112.746, y: 120.077
### Cnc in error state, ignored
CNC_XY_m, x: 113.746, y: 121.077
### Cnc in error state, ignored
VacuumOff()
###{"gc":"M09"} discarded, error state on

Code: Select all

==> {"gc":"G0 X94.111 Y106.393 A359.8556"}
{"r":{},"f":[1,0,39,140]}
{"sr":{"posx":194.954,"posy":191.334,"posa":270.000,"vel":2.16,"stat":5}}
{"qr":31,"qi":1,"qo":0}
{"sr":{"posx":185.539,"posy":183.404,"posa":278.389,"vel":12180.25}}
{"sr":{"posx":153.553,"posy":156.462,"posa":306.890,"vel":15822.27}}
{"r":{"fv":0.970,"fb":438.02,"hp":1,"hv":8,"id":"3X3566-KYP","msg":"SYSTEM READY"},"f":[1,0,0,6925]}
==> {"gc":"G0 X94.511 Y106.793"}
tinyg [mm] ok> 
qr:32, qi:1, qo:1
PlacePart_m(): Part down, Z28.483
{"r":{},"f":[1,0,29,109]}
{"sr":{"posx":0.000,"posy":0.000,"posz":0.000,"posa":0.000,"feed":0.00,"vel":1.82,"unit":1,"coor":0,"dist":0,"frmo":1,"stat":5}}
{"qr":31,"qi":1,"qo":0}
{"sr":{"posx":7.764,"posy":8.773,"vel":9941.33}}
{"sr":{"posx":35.235,"posy":39.814,"vel":13353.70}}
{"sr":{"posx":64.376,"posy":72.741}}
{"sr":{"posx":90.160,"posy":101.876,"vel":7682.08}}
{"qr":32,"qi":0,"qo":1}
{"sr":{"posx":94.511,"posy":106.793,"vel":0.00,"stat":3}}
ReadyEvent stat
###{"gc":"M05"} discarded, error state on
CNC_XY_m, x: 94.011, y: 106.293
### Cnc in error state, ignored
CNC_XY_m, x: 95.011, y: 107.293
### Cnc in error state, ignored
VacuumOff()
###{"gc":"M09"} discarded, error state on
{"r":{"fv":0.970,"fb":438.02,"hp":1,"hv":8,"id":"3X3566-KYP","msg":"SYSTEM READY"},"f":[1,0,0,6925]}
tinyg [mm] ok> 
qr:32, qi:1, qo:1

Code: Select all

==> {"gc":"G0 X96.375 Y114.023"} here blue
{"r":{"fv":0.970,"fb":438.02,"hp":1,"hv":8,"id":"3X3566-KYP","msg":"SYSTEM READY"},"f":[1,0,0,6925]}
tinyg [mm] ok> 
qr:32, qi:1, qo:1
{"r":{"err":"{\""},"f":[1,108,3,5325]}
ReadyEvent r
{"sr":{"posx":0.000,"posy":0.000,"posz":0.000,"posa":0.000,"feed":0.00,"vel":0.00,"unit":1,"coor":0,"dist":0,"frmo":1,"stat":1}}
PlacePart_m(): Part down, Z28.483
###{"gc":"M05"} discarded, error state on
CNC_XY_m, x: -0.5, y: -0.5
### Cnc in error state, ignored
CNC_XY_m, x: 0.5, y: 0.5
### Cnc in error state, ignored
VacuumOff()
###{"gc":"M09"} discarded, error state on

you suggestion is to move by rewire everything? it works until last week and from that time i added only camera, bcs old one stopped worked.
im thinking if it can have overtemperature origin.

Posted: **Fri Jul 21, 2017 2:07 pm**

Could be overheating, or power connection getting loose. The logs show random resets, so it doesn't look like a noise issue(that would give a different message).

Posted: **Sat Jul 22, 2017 12:57 pm**

is true that these days are very warm. okay. ill try buy some fans and heatsink and will test it.

btw motors have some over temperature protection?

and one extra question:
i use 20000mm/min speed and very interesting is after few movements the speed decreasing. can i be also caused by temperature protection?

Posted: **Sat Jul 22, 2017 3:08 pm**

> motors have some over temperature protection?

No. I think the drivers do, but I don't have a data sheet here.

> after few movements the speed decreasing. can i be also caused by temperature protection?

I don't think so. If the moves are the same speed but the pauses between moves are longer, it is your computer*. If the moves are getting slower, I don't know what is going on. (On the other hand, my machine is in a basement of a building far up north, so I don't have experience about overheating issues)

*: If the computer is not keeping up with the log messages, you can disable logging entirely, as well as reduce the amount of data that TinyG is reporting back. For the latter, TinyG sends a message at the end of a move anyway, so you only lose real time coordinate updates (but those are just eye candy). To do that, send text $si=3000 to TinyG. (status interval = 3000ms)

Posted: **Thu Jul 27, 2017 2:00 pm**

a could be my problem caused by current pots?
these pots are for zero motor current or its also work as current limiter in dynamic state?

Posted: **Thu Jul 27, 2017 2:30 pm**

The pots are current limiters in general. Be careful with A motor current, TinyG can give more power out than the small motor can handle. For the other Motors, the correct setting is one that doesn't give you issues and doesn't run the motors hot. The motors actually use most current when they are not turning but holding position.

Fyi, my settings right now are, for no particular reason:
X & Y: 80%
Z: 70%
A: 20%

LitePlacer.com forums

random connection cuts

random connection cuts

Re: random connection cuts

Re: random connection cuts

Re: random connection cuts

Re: random connection cuts

Re: random connection cuts

Re: random connection cuts

Re: random connection cuts