Advanced Search

forum.linuxcnc.org/18-computer/54368-pci...t-of-the-box?start=0

Nkbhvid wrote:

The 6 axis ranges from 9-11mv

The 6'th axis or all 6 axis?

The 6 axis ranges from 9-11mv

Failed communication connections are a software issue.


If you power the 7I97T (and not run LinuxCNC), do you read
near 0V on all analog outputs? (that is, less than 15 mV)

Moin,
mich würde interessieren wie du deine A6 getuned hast.
Ich hab noch immer leichtes fiepen an manchen Stellen und kriegs einfach nicht weg.

vikingj
Can you post your INI and hal files.

Hmmmm
as said: it has never left the office desk and has never been near a “large machine” in real life.
If damaged it can only be because of the failed attempts to connect to LinuxCNC.

Found this useful thread after posting:
forum.linuxcnc.org/qtvcp/39423-qtdragon-...a-manual-tool-change

Looks like someone wrote something similar and had it working for qtdragon and gmoccapy for 2.8.x. Will start here and update this thread.

Missing grounds between a large machine and the controller can easily damage
analog and encoder pins, that is, unless a permanent ground exists between
the machine and the control electronics. there can easily be enough potential
difference to damage electronic connections.

Hi everyone,
I’ve recently been trying to set up a IndraDrive from Bosch Rexroth with LinuxCNC, and I’ve run into some difficulties.
After quite a bit of research here on the forum, I’ve narrowed it down to two possible causes:

1. The IndraDrive supports EoE in addition to CoE. Could EoE be interfering with PDO configuration? Is there a recommended way to disable EoE on the drive? I’m using the latest LinuxCNC version and followed the EtherCAT tutorial from the forum.
2. I’ve seen that some people define initcmds in the Ethercat-conf.xml, and I believe those may include PDO configuration. What would be the best approach here? In my XML I already have configPDOs="true", so I assumed initcmds wouldn’t be necessary.

I can configure the PDOs exactly as I want using IO Engineering (Bosch’s equivalent to TwinCAT), but once I switch back to LinuxCNC, the PDOs are either missing or appear randomly most of the time. They are dynamically allocated from what I understand.

Any guidance would be greatly appreciated. Thanks!

I wonder how this could be damaged?
it has never been connected to anything else but 5 volt, Ethernet, one encoder and one analog out? It has never been installed and has never left the table.

MRx, nice! what hardware are you using?

and i'm still working on the new platform, also with an ethernet interface... now i can have all supported mitsubishi protocols running simultaneously on a single zynq 7010 core ok, 5 of them - parallel bus (MR-S), 2 copper serial (SSCNET I, II, MELDAS 5/6), 2 fiber (SSCNET III, III/H, MELDAS 7, 8). as all of them share the same multiple-of-222us cycle time...

still have the second processor core and a spare PTPv2-capable 1Gb ethernet port to try the CC-Link IE/TSN thing to complete the picture...

If you set all PID values to 0 and you still get 1V outputs  from the 7I97T analog outputs
,the 7I97T is likely damaged

Sorry, mismatch between advertised clock and real clock
so the baud rates were all off...

 Denser configurations like this have a slower clock to meet timing
and this is the first time I have made on of these configs, and I had
not quite gotten al the ducks in a row...

This _should_ be better

 
 

Hi PCW,Thanks for that. There's a problem with the sserial port; with the previous firmware (attached), the system as it's currently wired inc. the hal line:
loadrt hm2_eth board_ip="10.10.10.10" config="num_encoders=6 num_pwmgens=6 sserial_port_0=0000000" works and allows us to reference the 7i84 e.g.: hm2_7i97.0.7i84.0.3.output-00

Changing only the firmware to the one you posted above, lcnc fails to start with error:
twopass: Error in file ./morb01_IO_7i84.hal:
    Pin 'hm2_7i97.0.7i84.0.3.output-00' does not exist

this is with all wiring identical. close checking of the readhmid output and manuals suggests that the sserial port settings should remain the same - is this expected?