Advanced Search

Hallo,
I have used in my machine Mesa 7i96S -> 7i74 -> 7i87 I have flashed 7i96s_7i74d.bin and everything works. But I also need to control the driver for tin pump motor (will be used as spindle) Driver is controlled with something like modbus. So, my idea was to use serial port on 7i96S Unfortunatelly, in HALshow I see there sserial port only and not pktuart. I have tried to flash 7i96sd_pktv2.bin but then 7i74 and 7i87 doesn't work. Is it possible to have 7i74 connected to 7i96s 's P1 and use serial port on TB2 as pktuart?
Thanx a lot for your help.

I Decided to add a second THCad2 to perform ohmic sensing. In PNCconf what is the choice supposed to be on the encoder? seem only option available for plasma is Arc voltage, and under the other options I do not see one for OHMIC. I tried setting it to arc voltage but that doesn't seem right as i only get one option to configure which board is being used.

I have done a test without limit switches
and a failed linear scale resulted in a crash.
Ferror was 3/20mm but this didn't worked.
Ferror protects when encoder does not work
or works unreliable ?
Machine was a mill with analog speed servos
without encoders and position feedback send to linuxcnc by linear scales.
Can use this component to protect from this type runaway ?

I'd love to, but `raspi-config` was replaced with `menu-config` on this .iso and spi enable is no longer available. Currently have two flash drives (one from last year with 2.9.0pre0 which won't update to 2.9.1 or later, and the titled .iso.) Just want the 7C80 to work with something... anything.

Yes, pulling the SD card, should also work for me.
Thanks

Probably sending the PWM signale through timedelay or oneshot will work for M3, but that would also delay M5, so not good.
No idea if something could be done with remaping M3 and M5, but being LinuxCNC, i would venture a guess at yes.
Might also be possible without any of that,just in gcode, using M3 to turn on the relay then waiting for a sec or two with G04 P1 and following with another M3 with S value. To stop it, M3 S0, then G04 P1, then M5.
Hmmm, this might just work, granted the ini should be set for 0 spindle speed.

Yes, looks like this gcode solution will work to get me started, thanks! I would like to find a HAL or under-the-hood solution though because the machine will be shared at a maker space where people may forget to replace the spindle commands with the delayed version.

Maybe there's a way...

Done .... so now I have no ethernet connection at all ..... really interesting after:sudo apt-get install r8168-dkms

ethtool show me have no device running ....

www.makeuseof.com/tag/enable-spi-i2c-raspberry-pi/
 

Hmm, and there is no /dev/spidev0.0 and 0.1, so this .iso is unable to "see" the Mesa 7c80 card. Is there a way to enable it?

sonik wrote:

Thanks for the answer but this didn't help me. 
First of all, the gcode which lightburn generates is using M67. I then read thatNoteM67 will not function unless the appropriate motion.analog-out-nn pins are connected in your HAL file to outputs.
I don't have that in my hal-file generated by stepconf. So i probably need to connect that to some pins or signals or whatever and put it into the custom-hal. I just have no clue how to do that. 
I tried adding this : 
net analogout motion.analog-out-00 => pwmgen.0.value
net laserpwm pwmgen.0.pwm => parport.0.pin-01-out
but then linuxcnc is complaining about :
./custom.hal:3: Pin 'pwmgen.0.value' was already linked to signal 'spindle-cmd-rpm'
I attach my latest hal and ini files.

Stating it did not help and then using hal entries from the files you found there, is not polite.
You are on the right path, see PCW above and i would delete everything regarding the spindle and just adding the PWM parts from the files you got on the links above.
Also do copy the stuff about disabling the laser on stop, esc and pause.

If you have no motion, a common issue is too short step pulses
For initial testing I would set:

Step Length 5000
Step Space 5000
Dir Setup 20000
Dir Hold 20000

Latency issues:

Make sure you have all power saving, C1 states >C1, EIST, Turbo modes etc disabled in the BIOS.

If you have a Intel MAC make sure you have IRQ coalescing disabled (hm2_eth manual page)
(what does "lspci | grep -i eth" report)

Finally, using IsolCPUs  and pinning the Ethernet IRQ to the isolated CPU makes a big difference


 

Its not obvious, but 7i80hdt_svss6_8d.bin is a usable firmware file for a
7I80HDT and 7I48 (7I48 on P1)

 I would load the firmware into the 7I80HDT:

mesaflash --device 7i80hdt --addr 10.10.10.10 -- write 7i80hdt_svss6_8d.bin --reload

(assuming the suggested 10.10.10.10 ip address)

Then I would use pncconfs discovery option to  read the available card resources
to create the hal configuration.

Note that 7i80hdt_svss6_8d.bin firmware has 8 sserial channels on P3 so
I would use P2 for the 7I42TA (you can use p3 by specifically disabling
the sserial port in the hal file so the initial startup probe does not toggle any I/O bits.
 

Hello guys,

I'm not used to post here, I'm mostly using the mailing list but may be this way It can reach more people. 

Quick sum up. I have a 1997 Daewoo lathe with a Fanuc OT-C control that has problems more often that I can tolerate. It has the red cap Fanuc alpha servo motors. I'm attaching a picture of the Z axis servo motor, and also the encoder mounted on it. The X axis is similar although the power output of course is less. 

My idea is to do a quick retrofitting as soon as the control finally dies (or if I need to replace something that's too expensive) so I need to be prepared.

What I want to do is keep the original servo motors, but interface them with LCNC. From what I could read I may have to replace the encoders on the motors, wich is ok. Also I need to find  suitable drivers for the servo motors. I would like, if possible, to use a Yaskawa drive (wich I know can handle PM motors) or may be a chinesse generic servo drive to feed them (In that case I would need to replace the encoders for the ones the drive is ready to read). But I don't have too much time for experimentation. So what do you guys think? 

Thanks in advane for your help!

 

Once per turn issues may be mechanical (loose coupling)
or encoder problems (dirt on the code wheel)

If you look at the plot, it appears that the feedback data (from the encoder)
just stops at some point.

Do the axis lose position? That is, can you jog back and forth through the 'thump"
and end up in the same mechanical position?

If you want the PWM to be controlled by the M67 value
you would delete (or just comment-out) this line:

net spindle-cmd-rpm => pwmgen.0.value