Advanced Search

Hello, thank you for that, I added it but still the same result.

<masters>
<master idx="0" appTimePeriod="1000000" refClockSyncCycles="1">
<slave idx="0" type="generic" name="IS620N_ECAT_v2.6.8" vid="0x00100000" pid="0x000C0108" configPdos="true">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<syncManager idx="2" dir="out">
<pdo idx="1701">
<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="cia-controlword" halType="u32"/>
<pdoEntry idx="6060" subIdx="00" bitLen="8" halPin="OperationMode" halType="s32"/>
<pdoEntry idx="607A" subIdx="00" bitLen="32" halPin="TargetPosition" halType="s32"/>
<pdoEntry idx="60FF" subIdx="00" bitLen="32" halPin="TargetVelocity" halType="s32"/>
</pdo>
</syncManager>
<syncManager idx="3" dir="in">
<pdo idx="1b01">
<pdoEntry idx="6041" subIdx="00" bitLen="16" halPin="cia-statusword" halType="u32"/>
<pdoEntry idx="6064" subIdx="00" bitLen="32" halPin="ActualPosition" halType="s32"/>
<pdoEntry idx="6061" subIdx="00" bitLen="8" halPin="ActualOperationMode" halType="s32"/>
<pdoEntry idx="606C" subIdx="00" bitLen="32" halPin="ActualVelocity" halType="s32"/>
<pdoEntry idx="6077" subIdx="00" bitLen="32" halPin="ActualTorque" halType="s32"/>
</pdo>
</syncManager>
</slave>
</master>
</masters>

yes, you are right. I'll do it.

To close the loop here, this commit (to the Master branch) clarifies when the LASER and CAMERA buttons become visible:

github.com/LinuxCNC/linuxcnc/commit/ce1e...442d1e9b634e2eb8c5a7

Like I said it may be worth raising an issue on GitHub as the actual behaviour does not match the behaviour in the docs.

With your settings, I only receive 7 values. 

After removing the axes and joints that are not present on my milling machine, the result is the same - only 7 values are received. Sorry, I don't understand the principle of keys entries.

I have now shortened the list to 9 entries and am only using one key= statement. This allows me to transfer all 9 values.
loadusr -W mqtt-publisher \
--mqtt-broker=[MQTT]BROKER --mqtt-user=[MQTT]USERNAME \
--mqtt-password=[MQTT]PASSWORD \
keys=halui.axis.x.pos-relative,halui.axis.y.pos-relative,halui.axis.z.pos-relative,\
halui.joint.0.is-homed,halui.joint.1.is-homed,halui.joint.2.is-homed,\
halui.estop.is-activated,halui.machine.is-on,halui.program.is-running \

  
Peter

1. usually a good idea to post the files
2. start your config from a terminal ($ linuxcnc) and check output for clues
3. I would recommend using a simple texteditor to edit the files not a word processor like the one in your screen shot.

If you are on the US, mesaus has some.

if in the EU, eusurplus shows stock


We will have more 7I97T stock in 7-8 weeks

Right! Well, I was sure as I wrote this that the 7I83 also has encoder inputs as well!
7i97T here says it's out of stock though:

store.mesanet.com/index.php?route=produc...t_id=397&search=7i97

Do you know when are you going to have it back in stock?

Also, on the previous subject, if I decided to go the sserial route adding e.g. a 7I85, is one of the stock firmwares going to work without modifications?

Hello All,
I am currently driving my stepper motors via DMT556T's with a 48vdc source.

The motors are from Stepper-Online model 23HS45-4204S .
They can handle 4.2A based on the specs provided.

The current settings offered by the DMT556T are as follows:

 

My question, which Peak Current setting should I be using?

You would need an encoder interface as well (7I85,7I85S,7I89)

Might be simpler/cheaper to use a 7I97T
 

I'm looking at the Mesa cards available now for driving 3 servos with +/-10V and thinking to go with a 7I94T, one 7I83 for the servo drives and one 7I84U for various I/O like limits and buttons. Since I have not worked with this combination before, I would like your input if this is going to work. Are one of these ready made firmwares going to work, or I will need to create a new one (I have done it more than 10 years ago for creating a custom one for a 5i22, but not sure what I did back then  )

7i94t_16m_fallback.bin
7i94t_5abobd.bin
7i94t_7i74_ss_bissd.bin
7i94t_7i74_ss_bissd.pin
7i94t_7i74ssd.bin
7i94t_7i74ssd.pin
7i94t_7i76d.bin
7i94t_7i77d.bin
7i94t_7i85sd.bin
7i94t_7i89d.bin
7i94t_7i89d.pin
7i94t_bissd.bin
7i94tss_bissd.bin
7i94tss_bissd.pin
7i94t_ssd.bin
7i94t_ssid.bin

Hello again,
just a little update. On the repository i have added more information about current configuration but still a lot of work need to be done. Unlikely I have only one motor so i can't scale along 3 axes.

I have also updated a video on YouTube.



Next steps are:

• resolve joint 0 amplifier fault when toggle machine power. This seems to happen only one time after LinuxCNC opening.
• run and understand LinuxCNC / HAL Latency Test for a better configuration of LinuxCNC
• set machine configuration parameters like: encoder resolution, velocity, acceleration, pitch of leadscrew...
• implement PID control
• customizing using PyVCP

 

No ideas?

Thank you for the contact of the Eusurplus store. They responded instantly at any time of day, shipped quickly, and everything arrived quite fast — from Portugal to Bulgaria in just one day! Although people in Bulgaria aren’t the fastest, and local delivery took another three days, that’s a minor thing — plus there were weekends — still much faster than waiting for a shipment from the U.S. I’ve connected everything, and it’s all working now. I got a 7i95 board to replace my 7i97, so I can connect the motors directly in stepper mode. Now all that’s left is fine-tuning the machine’s logic.

The drive manual shows that the alarm output is an optocoupler
This can connect directly to the 7I76UE field inputs


+24V --> ALM+
ALM- --> 7I76EU field input