JavaScript is required
Polski

Hello Ruida Support, We have two laser machines using Ruida RDC6445S controllers connected to the same local network. Machine 1 works perfectly under the same conditions, using the same computer, so

35JMJ0H5

Hello Ruida Support,

We have two laser machines using Ruida RDC6445S controllers connected to the same local network.

Machine 1 works perfectly under the same conditions, using the same computer, software, and network setup.

Machine 2 has an intermittent communication and execution problem.

The controller responds to ping commands and appears normally on the network. However, during engraving and fill operations, we experience a very unusual issue.

During a fill engraving job, the laser sometimes unexpectedly jumps back and starts filling an area that has already been completed. For example, it may reach the middle of a filled area and suddenly return to a previous section, creating overlapping fill patterns or loops.

The problem is not a simple communication loss. The machine continues operating, but occasionally repeats previously completed fill sections as if old motion data were being processed again.

This issue occurs more frequently when the job is executed directly from the computer through LightBurn or RDWorks.

When the same file is first downloaded to the controller memory and then started from the machine control panel, the problem still occurs, but much less frequently.

The issue occurs with different files and different engraving jobs.

What we have already checked:

* Network cable replaced.
* Different network ports tested.
* IP address verified.
* No IP conflicts detected.
* Firewall disabled for testing.
* Same computer tested with another Ruida controller that works perfectly.
* Mechanical components inspected.
* Belts checked.
* Motors checked.
* Factory reset performed on the controller.
* Firmware settings reconfigured after reset.

The factory reset did not solve the issue. The behavior remained exactly the same.

Because the issue is more common when data is sent directly from the computer, we suspect a communication problem, controller memory issue, firmware issue, or a fault in the Ethernet communication circuitry.

Could you please advise:

1. Is this a known symptom of controller hardware failure?
2. Can a defective Ethernet interface cause engraving loops or repeated fill areas?
3. Is there a diagnostic procedure to test controller memory integrity?
4. Is there a firmware recovery procedure beyond the standard factory reset?
5. Are there internal logs or diagnostic tools available to identify the cause?
6. Could a defective controller buffer or memory chip cause previously executed motion commands to be repeated?

Controller Model: Ruida RDC6445S

Thank you for your assistance.

Best regards,

Ilque Martins

Czy możesz odpowiedzieć na to pytanie?

Napisz swoją odpowiedź, aby pomóc osobom z tym pytaniem.

Odpowiedzi (3)

  • Hello, please first confirm the following three situations and provide feedback on the results.
    1. Is the same graphic tested on different devices, and the results are as you reported, with one device having a problem and the other not?
    2. Switch the control cards of the two devices and test the same graphics again to see if the results are consistent.
    3. Provide the firmware version and model of the control card, as well as the version number of the RDWorks software, in order to investigate the reasons for different versions.

    1
    Odpowiedz
    • Hello, Thank you for your reply. We have compared the firmware versions of the two machines. The machine that works correctly is running firmware RDLC-V35.01.07. The machine that presents the problem is running firmware RDLC-V35.01.14. Because of this difference, we are beginning to suspect that the issue may be related to the firmware version. Before replacing the controller boards, could you please provide us with the RDLC-V35.01.07 firmware file so that we can install the same firmware version on the problematic controller and perform a comparison test? If there is a newer recommended firmware version for the RDC6445S, please let us know and provide the corresponding file as well. Thank you for your support. Since the controller with V35.01.07 operates normally and the controller with V35.01.14 shows the problem, we would like to rule out firmware differences before replacing hardware.

      0
      Odpowiedz
  • When the machine control panel is activated, the issue still occurs. Testing the same computer with another Ridder controller shows normal operation, indicating the problem may lie with this motherboard. Does the motherboard program displayed during reset match that of another functioning motherboard (are the interfaces on the panel identical at startup)? If they are identical, the issue is not with the motherboard program. If not, the motherboard program can be upgraded. The potential cause may be in the hardware of this motherboard. Another possible reason is the use of engraving, which is slower, potentially reducing the frequency of this issue. If your machine's dimensions and origin point are the same, you could try copying the RD file from this motherboard to another machine and run it to compare whether the issue lies with the software or parameters.

    1
    Odpowiedz
  • Hello,

    Thank you for your reply.

    We have compared the firmware versions of the two machines.

    The machine that works correctly is running firmware RDLC-V35.01.07.

    The machine that presents the problem is running firmware RDLC-V35.01.14.

    Because of this difference, we are beginning to suspect that the issue may be related to the firmware version.

    Before replacing the controller boards, could you please provide us with the RDLC-V35.01.07 firmware file so that we can install the same firmware version on the problematic controller and perform a comparison test?

    If there is a newer recommended firmware version for the RDC6445S, please let us know and provide the corresponding file as well.

    Thank you for your support.

     

    Since the controller with V35.01.07 operates normally and the controller with V35.01.14 shows the problem, we would like to rule out firmware differences before replacing hardware.

    0
    Odpowiedz
    • send-me please ilquemartins@gmail.com

      0
      Odpowiedz
Chanelink
Chanelink
Chinese 粤ICP备20068671号-3

Copyright © 2021 Shenzhen Chanelink Network Technology Co., Ltd. All Rights Reserved.