Advanced Search

I kind of think that "Unmatched messages", that many, are related to the real-time performance, jitter, of that particular system.
If possible, it would be interesting to duplicate the good system's complete disk and run that on the bad system.

Hello Oliver

1.  So I removed all of the Rio folder and openFPGALoader, openocd etc..  I noticed you had updated the installer (Thankyou)  I then did a new git pull and installed a fresh.  With th default config for Tangobob loaded in UI setup tool all went smooth.  A flash got me the following output.  Led on Tangnano blinking:-Generate

---

Resources | Usage

---

Logic | 2226/8640 26%
--LUT,ALU,ROM16 | 2202(1634 LUT, 568 ALU, 0 ROM16)
--SSRAM(RAM16) | 4
Register | 2774/6693 42%
--Logic Register as Latch | 0/6480 0%
--Logic Register as FF | 2764/6480 43%
--I/O Register as Latch | 0/213 0%
--I/O Register as FF | 10/213 5%
CLS | 2206/4320 52%
I/O Port | 28
I/O Buf | 28
--Input Buf | 8
--Output Buf | 19
--Inout Buf | 1
IOLOGIC | 0%
BSRAM | 0%
DSP | 0%
PLL | 0/2 0%
DCS | 0/8 0%
DQCE | 0/24 0%
OSC | 0/1 0%
User Flash | 0/1 0%
CLKDIV | 0/8 0%
DLLDLY | 0/8 0%
DHCEN | 0/8 0%
DHCENC | 0/4 0%
======================

Flash
openFPGALoader -b tangnano9k impl/pnr/project.fs -f
empty
write to flash
Jtag frequency : requested 6.00MHz -> real 6.00MHz
Parse file Parse impl/pnr/project.fs:
Done
DONE
Jtag frequency : requested 2.50MHz -> real 2.00MHz
Erase SRAM DONE
Erase FLASH DONE

Erasing FLASH: [==================================================] 100.00%
Done

write Flash: [========= ] 16.12%
write Flash: [================= ] 32.44%
write Flash: [========================= ] 48.76%
write Flash: [================================= ] 65.28%
write Flash: [========================================= ] 81.60%
write Flash: [================================================= ] 97.82%
write Flash: [==================================================] 100.00%
Done
CRC check: Success
cp -v hash_new.txt hash_flashed.txt
'hash_new.txt' -> 'hash_flashed.txt'

On W5500 there is a tiny led under the lan port and is a faint red when the bob is powered. I cannot conect with Lan, can some one give me a tcp 4 setting for the host pc so I can ping the bob on 192.168.10.194.

Thanks for the guidance regarding the pin assignment. Great work

Thanks Ollie and the team

Alfred is still coming. Probably about 24 hours away but on track to take a direct hit on a town of 4 million people... We are south of the estimated crossing point but apparently all the wind and rain  is on the south side.

 

Tomorrow will be interesting...

i see. cause i tried ~/dev and it says no such folder

I think you are in the /dev folder, not ~/dev
note the ~ for home folder.
 

thats after this line
git clone github.com/dbraun1981/hal-cia402

not sure on what program?

thanks

now i get
fatal: could not create work tree dir 'hal-cia402': Permission denied

also you may need
sudo apt install git

try 
sudo apt install linuxcnc-uspace-dev

halcompile is part of the dev package.

So now I'm stuck at this step. it says git command not found....

---

If you are using cia402 compatible drives:

cd ~/dev
git clone github.com/dbraun1981/hal-cia402
cd hal-cia402
sudo halcompile --install cia402.comp

unknown wrote:

Been reading this for while, I think you need to reassess what you think you know compared to what you actually know.
Usually the stepper drivers are pretty hardy, the ones I have in my mill are about 15 years old and haven't missed a beat.
I've never heard of anyone having to make modifications.
Some of the early TB6600 drivers weren't as reliable as they should have been, no experience with them myself but many reports of them being that way.
So just settle down, do things the recommended way and don't try to modify things that don't require modification. And if you still insist of doing board level mods consult the data sheets for the components that will be affected. I'm sure this would have resolved the issue of "no flyback diodes".

 
I bought two 2nd hand machines with stepper system. They were pre configured for 4 axis, so I had some spares to kill. Out of the 8 drivers two or three are still working. (so I would say occasional death happens)
At least one or two I probably finished by creating a short when I was "repairing" the machines long time ago.
My guess is that the drivers were running at their limit for a long time and were a little undersized for the motors. (or can something age inside?)
The last year drivers started quitting service one by one. First by making some humming noises during machine start, then eventually stopped working.
Given the prices of new ones, not worth investigating. (but we are still talking 10-15 years, before failure)

If you have no space you can mount a Kuka robot on the seiling.


But I think plasma makes some mess, so a big feature is the water tray.
I skipped any ideas of laser or plasma. Laser I find too expensive for my hobby. $$$ and a plasma has to compete with the local laser company that cuts things for a small fee.

I am using LinuxCNC+EtherCAT to retrofit an old NC controller in Japan. I am not good at English, so I am posting on the forum using Google Translate.

I apologize if it is difficult to read.

I am currently using an old torque-controlled servo amplifier controlled by Beckhoff's EL5101+EL4132.

The problem is that in Homing, Index-enable is connected to jioint, PID, and Encoder, but when it is moving at the HOME_LATCH_VEL speed, when it seems to detect the C phase of the Encoder, it goes into a runaway state for a moment and immediately goes to the HOME_FINAL_VEL speed.

After Homing ends, the same phenomenon does not occur when Homing is performed again. It only occurs during Homing immediately after powering on.

When I made it with EM7004 before, I was told that I did not connect Index-enable to PID, but this time I am having trouble resolving the problem.

I cannot increase the PID gain because it goes out of control.

I am attaching the INI and HAL. Please let me know if there are any mistakes.

I am using LinuxCNC 2.9.4. The EM7004 system was created with 2.3.2 and has not been upgraded.

I have asked a question on "General LinuxCNC Questions" about whether there is a problem with the PID, but I was unable to find a solution.

Thank you in advance.

 

looking good!