2nd Hand Machine : Limiters / Controller Something very wrong !

[Jeffrey Aley]

Distilled issue :
Proximity Sensors react and work when a job is controlled from RDW. IE light up and stop the Gantry or head.
Proximity Sensor do not light to show activation when metal is presented to it when static.
Proximity Sensors do not Light when in start up and the gantry and head are "homing"
( Side note as this might help diagnosis ) The Z axis still refuses to move from the Ruida "direction arrows" .

My logic suggests that the Proximity sensor work as in not broken as a piece hardware.
Why work with RDW but not with Ruida controller alone. ?
When writing a job from RDW ie ; Draw a rectangle and then press start, does it write the information to the Rudia or pass through ?


Has anyone else had this as a symptom ..

Very odd. I agree with your assessment - the Proximity Sensor is probably working properly. It's almost as if the GND for the sensor is hooked up to a switchable power source (like OUT1, OUT2, or WIND) instead of directly to GND.

Here's my hypothesis: the proximity sensor does not light up because there is no power going to it.

How to test the hypothesis: find where the wires from the sensor are connected to the RuiDa controller. Verify that the correct two wires are connected to +24V and to GND (you will need the datasheet for your particular brand of sensor to figure out which wire is which). Measure (with a voltmeter) the voltage across those two wires. If necessary, disconnect the wires and measure the voltage coming out of the RuiDa for the two connections.

Regards,

-Jeff

[Gene Uselman]

Hard limit is a different function than homing of course. But it seems your limit switches are functional and the controller sees them. Are you asking the laser to run outside of the 'safe' bed area? That is what sounds like is happening. The controller has built in functions to protect itself and when you pressed ESC you over-road the safeguard and said- go out there... that is what I want [you did not want that]. That behavior cannot be changed in the software that we have access to.

First check your file- try running a preview to see if it is what you expect and make sure your software boundaries agree with your machine. The homing must be not enabled somewhere in the software that we do have access to... triple check all those places.

[Andrew Woore]

Very odd. I agree with your assessment - the Proximity Sensor is probably working properly. It's almost as if the GND for the sensor is hooked up to a switchable power source (like OUT1, OUT2, or WIND) instead of directly to GND.

Here's my hypothesis: the proximity sensor does not light up because there is no power going to it.

How to test the hypothesis: find where the wires from the sensor are connected to the RuiDa controller. Verify that the correct two wires are connected to +24V and to GND (you will need the datasheet for your particular brand of sensor to figure out which wire is which). Measure (with a voltmeter) the voltage across those two wires. If necessary, disconnect the wires and measure the voltage coming out of the RuiDa for the two connections.

Regards,

-Jeff
[/quote]

Jeff you might be on to something there I've just checked the switching , knew exactly the wires as i'd already changed a switch like for like .
Guess what the two blue are wired into Out1 !!
I've got to go out tonight ( PM here in the UK ) but first thing tomorrow morning I'll swap them to GND and test ..
Fingers cross .. Actually quite excited to test ..

Update tomorrow 8.30am GMT !!

[Andrew Woore]

Distilled issue :
Proximity Sensors react and work when a job is controlled from RDW. IE light up and stop the Gantry or head.
Proximity Sensor do not light to show activation when metal is presented to it when static.
Proximity Sensors do not Light when in start up and the gantry and head are "homing"
( Side note as this might help diagnosis ) The Z axis still refuses to move from the Ruida "direction arrows" .

My logic suggests that the Proximity sensor work as in not broken as a piece hardware.
Why work with RDW but not with Ruida controller alone. ?
When writing a job from RDW ie ; Draw a rectangle and then press start, does it write the information to the Rudia or pass through ?


Has anyone else had this as a symptom ..

Very odd. I agree with your assessment - the Proximity Sensor is probably working properly. It's almost as if the GND for the sensor is hooked up to a switchable power source (like OUT1, OUT2, or WIND) instead of directly to GND.

Here's my hypothesis: the proximity sensor does not light up because there is no power going to it.

How to test the hypothesis: find where the wires from the sensor are connected to the RuiDa controller. Verify that the correct two wires are connected to +24V and to GND (you will need the datasheet for your particular brand of sensor to figure out which wire is which). Measure (with a voltmeter) the voltage across those two wires. If necessary, disconnect the wires and measure the voltage coming out of the RuiDa for the two connections.

Regards,

-Jeff

Jeff and Gene your both Bobby-Dazzlers !
1st Step in getting the KH-5030 back on the road.
This morning I followed the suggestion of checking the wiring and that they should be wired to GND.
After identifying that the Proximity sensors / Limit switches were wired to OUT2 and should have been wired to GND I restarted and it homed like a dream .

So conclusion is that if the proximity sensors are not responding to the controller or manual triggering but work when RDW or Laserburn sends a job then check your wiring ..

Now the next thing for me to start fixing is the Z axis as this still refuses to budge .
The side buttons "up/down" no response
Ruida Z setting to move up/down ( which is the left and right ) no movement.
The Ruida controller finally shows X & Y as 0,0 position but Z is 3000.0.
When sending movement request via Ruida to Z Axis the position reading changes but bed does not.

If anyone has had this issue then let me know what you checked to fix.
I'll be looking at the wiring for it later today as i think that if the X&Y were not cabled who know what else the previous owner "replaced" or "fixed"


THANKS AGAIN to Gene and Jeff for support to date really appreciated

[Gene Uselman]

I had to look up - bobby-dazzler in British English, noun, dialect --anything outstanding, striking, or showy, esp an attractive young woman

I will take that as a compliment even tho I am neither Attractive, young or female.

I was just getting used to Bob is your Uncle...

If you have up and down buttons on the cabinet, the software has no control over your Z. Some machines have steppers and stepper drivers to make the lead screws go up and down- I am guessing yours is a DC motor with it's own circuitry.

[Andrew Woore]

I had to look up - bobby-dazzler in British English, noun, dialect --anything outstanding, striking, or showy, esp an attractive young woman

I will take that as a compliment even tho I am neither Attractive, young or female.

I was just getting used to Bob is your Uncle...

If you have up and down buttons on the cabinet, the software has no control over your Z. Some machines have steppers and stepper drivers to make the lead screws go up and down- I am guessing yours is a DC motor with it's own circuitry.

Bobby Dazzler "a person or thing considered remarkable or excellent." Think that suits your assistance to date

As to the Z axis , thanks for the steer , again! , I'll trace the wiring tonight to see what goes where check the connections and if the wiring seems to be in the right place.

I'll see if i can find a wiring diagram for the cutter to assist .. I had a dig around on the forum but did quite find what i was looking for .

Will be Updating the thread tomorrow i'm sure ..

[Gene Uselman]

My opinion is that most lasers with the Z motorized have a stepper motor and drive for that axis- it is then controlled by the... controller. I have seen a few of the machines with up and down buttons but I believe it is less common. Your system will probably be easier to troubleshoot.