Advanced Search

The SSR outputs on the 7I96 or 7I96S are relatively slow so
probably best driven by software PWM (the pwmgen component)
Your  40A SSR may also be fairly slow.

At an update rate of 1 KHz its probably best to use the PDM mode
(PWM frequency set to 0) but a low PWM frequency (like 20 Hz with dither
enabled) may also work well.

If you need a high speed PWM, you could use a configuration with
PWM on the P1 expansion connector (7i96_5abob_d.bit for example)

  So I have a 7i96 non S version and I would like to use one of the general outputs 0-5 to send a pwm signal
to a dc to dc SSR capable of controlling 40 amps. The quick back ground is I am getting information together
for installing LinuxCNC on my 5 axis foam cutter and need a pwm for controlling duty cycle for the hot wire bow's
temperature. The reason for using the older 7i96 is because I have 2 in my inventory. So is it possible and if
so how much of a pain is it to do?

ok，thanks，may i should read code of the planner carefully~

so you suggest to update all ... linux kernel and ethercat ... and after reinstall all??

Did you also connect the input common?

Those look niceeeee!
Thank you.

Yeah i saw your description in another post and they look very similar. After seeing the discussion you had, i've already decided to do a minor change to the estop-button-circuit. The button itself have a NC and a NO connector, but i'm going to change the NO-contactor so i'm getting 2xNC instead and then put them in series and make that part redundant aswell... thanks for the inspiration

rodw wrote:

I also should have mentioned the estop-latch component allows you to build an estop chain in hal.

yes, i've studied that part, but i'm very unsure how to couple it with the hardware latch in the safety relay. My thoughts so far, see if it is clear and makes sense:

• The physical estop triggers, this sends estop-signal to LinuxCNC and automatically kills servos after set amount of time.
• The estop-signal sent to LinuxCNC triggers the estop-latch inside LinuxCNC and stops everything "on the software side" including estopping servers via EtherCAT.
• The physical reset-button is connected to IO-pin instead of directly to safety relay. When pushed it sends signal to LinuxCNC estop latch to "open" disabling software estop.
• When LinuxCNC estop goes into normal operation mode it sends a "oneshot" signal to the safety-relay to cause a reset of the physical latch

Does that make sense? As far as i can see i get "the best of both worlds", right? The only missing part is that i won't be able to trigger an estop from software, but i'm not sure i need that? It could be solved by a redundant relay in the physical estop chain, triggered by IO from LinuxCNC...but not sure if it is needed in any way...

/Thomas

A later deb in a repository will upgrade if you do apt install again. If you go to the 2.9.3 docs and find the Getting Linuxcnc doc,
Heading 7.1 has a script that sets up sources to the Linuxcnc repository 
You could try that.
 

There are a lot of things you can get wrong.
My video covers most of the bases for a mesa card

I also should have mentioned the estop-latch component allows you to build an estop chain in hal.

Looks Good
This is mine on a Mesa setup but also have the same on an Ethercat machine
 
Red Safety Relay, two force guided relays in front of it.

The only thing I can see a bit different is your estop does not have dual circuits. I bought new ones for these safety relays that did. Back of switch shown here. (Brand is Idem, same as relay)
 

On my ethercat machine, I drop power to the steppers but also use the disable signal on the motors.

Hello
I recently bought the Mesa 7i96s to upgrade my cnc machine.
I switched the jumper to change the ip address, powered it and connected it to my pc. I can ping it, and read the hostmot2 configuration with mesaflash, so far so good.
But then I realised that the end switches don't work. So I monitored the input pins under Hal configuration (LinuxCNC, axis 2.9.3) and then connected 5V from the board's power supply to the inputs, and no pin showed a response.
Is it me or the board that is at fault?

oh ... I check my past actions .... pakage manager is right ... so only 2.9.0 version is admitted .... but I've installed manually a deb package for 2.9.2 .... so now think need deb pacakge for 2.9.2 linuxcnc-uspace-dev ... where find it? ... sorry i'm not usual with forum and all update of Linuxcnc repositories ...

ŗdw my question is related to re-install deb package ... so can simply remove 2.9.2 linuxcnc istallation and than reinstall the correct version or need to remove ethercat too?

so now I have these situation in package manager (if note is quite clear because not possible install uspace-dev ... there is not 2.9.2 version):

 

plus in update manager have these one (can not update to 6.7 kernel ... not sure is rt-preempt one):

 

not know if can update without need to remake all again (mac adress, udev rules, 666 permission etc etc).

regards

re ethercat, We just install the sources.list settings for apt so no software is installed. (unless you do it). So there should not be any need to remove the sources entries

Installing the mate desktop on Debian is nice
 

Thanks for the explanation.

Result from apt-cache policy linuxcnc,

linuxcnc:
Installed: (none)
Candidate: (none)
Version table:

Which is strange as it is a fresh install of the current 2.9.3 iso.