× Forum Header

Only Z axis is working / HP DC 7600 Tower

More
14 Nov 2020 21:35 #189380 by Jean NT76
Dear Community

I had a working Plasma cutter until I upgraded to 2.8. I wanted to integrate PlasmaC and the Proma THC150.
After the upgrade the hard disc made problems. Finally the latency when from under 12 500 to over 120 000. The HDD is onboard, not reasonably replaceable.

After having seen two HP DC7600 in the latency table with good values I bought one (Tower with the Intel 940) .

Debian with Linuxcnc 2.8 was installed. Most function in the Bios are deactivated, I do not have a lot of possibilities in the given Bios. No option about HT etc ...
Ram was increased from 1Gb to 2Gb, this had little impact on the max jitter.
The 25um max jitter is around 56 000 and the 1um is around 37 000. Has somebody an idea how to get it quicker?

Furthermore is it not possible to operate Linuxcnc with this values?

What also drives me nuts is that I only get the Z axis moved with the stepconf axis test (also with the laptop but with this it moved well down and poorly upwards). I thought it must come from the too short values for the stepper I tried different values which I found here in the forum but X and Y aren't moving. Only the value is changing in the display.
Furthermore I have now only one input for all homes and limits. And when engaging the machine I get an error message that the limit switches are triggered. I have checked the limit switches and they are working properly.

Is the stepconf working properly with 2.8 when having two motors on the Y axis? I read somewhere that this doesn't work.

May it be that the China BOB is dead?How to check this?

For over a month the machine is down and I need it for some jobs.
Your help will be highly appreciated.
Kind regards,
Jean

Please Log in or Create an account to join the conversation.

More
14 Nov 2020 21:53 #189384 by tommylight
Upload the hal and ini files.
China BOB might be dead, but it is for sure to slow.

Please Log in or Create an account to join the conversation.

More
15 Nov 2020 08:35 #189443 by Jean NT76
Morning,

I attached what I got by using the stepconf.

The ChinaBOB is very limited for sure but it did its job well over the last 4 years. And the speed of the steppers were higher than my machine was able to handle due to vibrations in the TR20x8 spindles.

Machine:
1 rev = 8mm
400steps/rev
2 limit switches per axis, no separat home.
Driver: DQ860MA
Motor: WT86STH118-6004A

Greetings,

File Attachment:

File Name: RamsesTHC.zip
File Size:6 KB
Attachments:

Please Log in or Create an account to join the conversation.

More
23 Nov 2020 10:16 #190104 by Jean NT76
Hello

For my plasma cutter I am using a HP Compaq DC7600 Convertible Minitower /09F0h.
It has the pentium D CPU 3,4GHz with 4Gb RAM and solid state hdd
SMI Fix is not recommended for the given version of chip set.

I have the following images running on it:
Debian 10 Buster LinuxCNC 2.9
Debian 7 Weezy LinuxCNC 2.7.15
Debian Stretch 13 LinuxCNC 2.8.0

Without playing in the around in the bios with exception of the energy saving settings, I got following latency results:

Buster without pushing the CPU 53000 / 34000 otherwise 55500 / 104700
Weezy with Office and Firefox starts 12500 / 28050
Stretch with Office and Firefox starts 28900 / 49050 Stretch has a strange behaviour, with 6 GB Ram the Latency goes down a few 1000 but only after being in operation for 10 to 15 Minutes. And it is quicker when energy saving is on in the bios.


Weezy is the best solution for this PC, unfortunately I am unable to get the twin motors working with 2.7.15. I will have to try 2.8 on this version if I don't find a solution.

The only LinuxCNC system I was able to get a least a starting hal and ini is 2.8. The stretch version is has poor latency values and is much slower to start. Some counters are running in the startup procedure. It seems to be an issue with the solid state disc.


The communication is over cheap DB25 China Bob wich served me well over the last 4 years. My key issue now is that the ALL HOMES and LMITES is not working. The pin signal has no effect. To check if it is not the Input pin itself, I tried different pins. Somehow the Input is not considered in the software.
With exception of the twin motors all motors are working correctly now in the stepconf.

Any ideas why the limit switch doesn't t work for homing?

File Attachment:

File Name: SuperBurniTHC.zip
File Size:6 KB
Attachments:

Please Log in or Create an account to join the conversation.

More
23 Nov 2020 17:07 - 23 Nov 2020 17:09 #190124 by Todd Zuercher
How do you have your limits wired up? Are they ordinary micro switches or are they prox switches? Do you have all of the voltage sources connected to the BOB? Most of those cheap Chinese BOBs require 12v be connected to the board to supply the power for the inputs.

Have you looked at the parallel port's input pins with HalMeter? Can you see the input pin change when you activate the switch?
Last edit: 23 Nov 2020 17:09 by Todd Zuercher.

Please Log in or Create an account to join the conversation.

More
23 Nov 2020 17:56 #190128 by Jean NT76
All limit switches are parallel connected and are normally open. Yes, they are mirco switches. The BOB is connected to a USB plug with 5V and with a 5V power supply. (This should protect to PC side as it is not directly connected to the CNC.) As mentioned it worked for for 4 years, only with one input pin per axis, thus Voltage should not be the issue.

This browser does not support PDFs. Please download the PDF to view it: Download PDF



I will check tomorrow morning how to use the HalMeter. I don't think that the signal is read, as I get no error message when switching the limit switch while the machine is on. I have connected also a new switch directly to the board with 20cm cables to check the function.
Attachments:

Please Log in or Create an account to join the conversation.

More
24 Nov 2020 14:52 #190202 by Todd Zuercher
Can you measure 5v between the input pin and GND on the BOB with a DVM?

Please Log in or Create an account to join the conversation.

More
26 Nov 2020 09:32 #190322 by Jean NT76
I have checked the signal in the HALmeter. joint.0.home-sw-in is FALSE and it does not change while pushing the microswitch.
The Input signals have all different in voltage on the BOB. They are between 5 an 8,8 Volt. The pin with the microswitch goes up from 6 to 12 Volt when pushed. I have tried this on pin 10 and pin 13. On pin 10, I had almost 13V when closing the switch.
The BOB supplies are 5,08 and 5,06 Volt and the polarity is correct.

Any idea if this is normal? How can I have 12V on the input pin when the supply is only 5V.
Yesterday I got a new BOB from China. If no new hint where to look, I will try the new BOB.

Please Log in or Create an account to join the conversation.

More
26 Nov 2020 09:41 #190323 by Aciera

How can I have 12V on the input pin when the supply is only 5V.


Exactly. So measure the supply voltage between +5V and GND on the terminals of the BOB. If that is not 5V disconnect the board and measure what voltage comes from the PC. If it is 5V without the board then its likely the board. If it is still not 5V then it's the cable or the PC.

Please Log in or Create an account to join the conversation.

More
26 Nov 2020 10:34 #190325 by tommylight

Jean NT76 wrote: Any idea if this is normal?

It is not, so power off everything and check and recheck the wiring, or just yank everything out and start from the beginning.
Proceeding like this will most probably end in tears.
And make sure you have proper grounding.

Please Log in or Create an account to join the conversation.

Time to create page: 0.251 seconds
Powered by Kunena Forum