Jogging problem <solved, noise issues>

[mario.morosavljevic]

Thank you for your reply.

1) Our machine has a stationary table and tool is moving. I'll draw a picture fast and attach it.

2) Problem is not homing in the wrong direction but jog is not working on Y negative direction (works fine in Y +), therefore we can't home our machine since Y just wouldn't move when pressed a jog button, alt-j jogging, homing or anything which requires it to move in a negative direction. We've noticed that Y- starts to work AFTER we move Z first (jog it manually) in a negative direction. After we homed our machine (with Z- movement then home) we tried to operate with our Y axis in MDI. Works fine in a positive direction and problem occurred again when we tried to move it in a negative. We've noticed that CNC12 is counting as if the machine is moving but it's not (there is no signal from Acorn to drivers).

3) Limits tripped message is because we've been restarting CNC12 and every time we start it there is a message "limits tripped, cleared etc"... Every time we started a software we tried to home our machine again to check if we fixed a problem, therefore Z limit was tripped since it's the 1st axis in a homing sequence.

4) We're using NPN NO limits and it's working fine when tripped. We've tried with HomeALL, LimitALL setting but "PLC compile error". I've seen on a forum it will be fixed in 4.14

5) There is a fresh report zip in between pictures, every post so far I've generated a fresh one.

6) We've tried to connect Y and Y slave drivers on the same port and still, the same problem persists. Then the same problem started to happen with X-axis and Y (X not moving in a negative direction). And the same solution, press Z negative and then it works again which is weird.

[cnckeith]

Thank you for your reply.

1) Our machine has a stationary table and tool is moving. I'll draw a picture fast and attach it. << Ok great! this is just the way i have my router setup>>>

2) Problem is not homing in the wrong direction but jog is not working on Y negative direction (works fine in Y +), therefore we can't home our machine since Y just wouldn't move when pressed a jog button, alt-j jogging, homing or anything which requires it to move in a negative direction. We've noticed that Y- starts to work AFTER we move Z first (jog it manually) in a negative direction. After we homed our machine (with Z- movement then home) we tried to operate with our Y axis in MDI. Works fine in a positive direction and problem occurred again when we tried to move it in a negative. We've noticed that CNC12 is counting as if the machine is moving but it's not (there is no signal from Acorn to drivers).

3) Limits tripped message is because we've been restarting CNC12 and every time we start it there is a message "limits tripped, cleared etc"... Every time we started a software we tried to home our machine again to check if we fixed a problem, therefore Z limit was tripped since it's the 1st axis in a homing sequence.

4) We're using NPN NO limits and it's working fine when tripped. We've tried with HomeALL, LimitALL setting but "PLC compile error". I've seen on a forum it will be fixed in 4.14 <<< I didn't say use LimitAll, i said use HomeAll, if you would post a current report i could see how you have it set up, but all i have is a report from 3-7-19 which is outdated, wire like this. but set input 2 to UNUSED in the wizard>>>

5) There is a fresh report zip in between pictures, every post so far I've generated a fresh one. <<see above>>

6) We've tried to connect Y and Y slave drivers on the same port and still, the same problem persists. Then the same problem started to happen with X-axis and Y (X not moving in a negative direction). And the same solution, press Z negative and then it works again which is weird.

<< this is not the test i was suggesting. take the X signal wires and move them to the Y axis (2nd axis signals on Acorn) , and put the Y axis signal wires on the X axis outputs on acorn. What happens?>>

[cnckeith]

do you have teamviwer 12, installed with a good internet connection?

[Gary Campbell]

Mario...
A couple things to try..

First, set all your inputs to "unused" except for the estop and set all to "NO" test motion, report. then:

1) Set parameter 968 to 12 to allow a longer pulse in the step & direction signal. If that doesn't cure the issue:

2) Connect your step and direction signals to the DB25 header.

[mario.morosavljevic]

Thanks for a fast reply,

currently, we're not in a workshop (midnight here). We have Teamviewer on a machine PC installed and a stable connection. We'll rewire it tomorrow as you suggested and if you're free then we can do a Teamviewer meeting. Since we have 6 hours timezone difference, when are you going to have free time to do a TeamViewer meeting?

I'll attach again 3-8-19 report.


Mr. Campbell thanks for a reply. We tried both already, that was the first suggestion by Mr. Keith.

[Gary Campbell]

Mario...
Hopefully it will work out for you.

Sorry, I do not do TeamViewer support sessions for systems that I have not built.

[cnckeith]

mario, hello. when we say we want a "fresh" report.zip than means one from Today! in other words, a "current" report.zip
the report.zip contains all the cnc configuration settings and message logs, if we look at one from a few days ago, that won't show us the settings you currently are using or the message logs.

[mario.morosavljevic]

Hello,
Today we tried all of the solutions you suggested.

1) We rewired it as Mr. Keith suggested as Homeall and tried it and we still have the same problem. I'll attach new report.zip. generated when we tried this solution.

First, set all your inputs to "unused" except for the estop and set all to "NO" test motion, report

2) We tried as Mr. Campbell suggested to set all inputs to unused and NO except ESTOP and still the same problem is happening.
The machine is jogging fine in Y+ and X+ and when we tried to move it in a negative direction it just wouldn't move. Then we move Z in a negative and both X and Y started to work again. During that "bug" when Y and X won't move in a (-) direction it works just fine in (+). So the same problem is still happening.

3) We swapped Z driver with Y one and Z with X, as Mr. Keith suggested and we still have the same problem on same axes (X and Y).

[Gary Campbell]

Looks like its time to follow steps 1) and 2)...in order

[mario.morosavljevic]

Looks like its time to follow steps 1) and 2)...in order

Thanks for a fast reply.
I'm not sure I entirely understand what steps you're referring to