Advanced Search

Ok I uninstalled and reinstall SheetCam and it seems to be working fine again. I looked at the Post Processor and there are many more line pass the above post screen shot. Maybe the post processor got corrupted some how.

Thanks rodw - I actually read that very post earlier.

I have not been able to do anything with a mulitmeter yet (kids) but I did notice a hint on the OEM wiring diagram - both the speed and the feed rotary switches are fed by  (or connected to) 'TB1-9' on the original wiring. It would also appear that TB1-9 is a DC COM, which would lead me to think that the other wires on the rotary switch are NOT DC COMs. 

Multimeter tomorrow.

 

7I96S configuration with PKTUART on the 7I96s and 7I74
(all sserial) on P1. Note that the P1 sserial  port changed to
to port 0 (was port 1)

 
 

7I96S firmware with P1 pinout for the common "Mach 5 Axis BOB"
2 additional step/dir channels (7 total) and 4 RCPWMgens on the BOB

 
 

PCW wrote:

Mesa firmware includes a specific PWMgen for RC servos: RCPWMGen.

This can be added to any Mesa FPGA card. Standard PWMgens tend
to have low resolution when used for RC servos as the full scale
duty cycle of RC servos is quite low ( a few %)
 

In my case even low res motion is better than stop to stop action. Out of curiosity what physical pins on a 7i96 would drive the RC servo. 

Mesa firmware includes a specific PWMgen for RC servos: RCPWMGen.

This can be added to any Mesa FPGA card. Standard PWMgens tend
to have low resolution when used for RC servos as the full scale
duty cycle of RC servos is quite low ( a few %)

I did send the screen shot to SheetCam no reply yet.
I did look at the post processor and saw this at the bottom of the edit screen.  Why there is anything about a round tool in a plasma post processor.
 

In Norway, order from www.eusurplus.com as it is in Portugal, so no import duties.
Or from www.welectron.com in Germany.
Both carry Mesa cards.

PCW wrote:

A 7I92TH/TF and a couple Mach 5 Axis BOBs could do this
(or even without the BOBs if you are careful...)
 

Crazy idea, what is the frequency of the spindle PWM signal on a 7i96 card?  Can I co-op that to drive a RC servo.  Or use a spare output and pulse at 50 Hz? Can the I/O handle that kind of duty cycle toggling?

You would not expect an error/thump running the motors open-loop
as the error seems to be encoder related (and the encoders are not
involved in open loop motion)

It might be wiring related ( intermittent open or short in the encoder
wiring that's ball screw position related

Are you sure you only get the error once per turn?

Another possible cause of the following error would be loss of the analog output
briefly but having this happen once per turn also suggests some kind of wiring
intermittent

Hi all, 
I am stuck and hope someone can help me to get my VFD working.
I had a Huanyang 1.5KW VFD working perfectly for years and I wanted to upgrade to a 4KW spindle. I bought what I thought was a at the time was another Huanyang but it turns out to be a knockoff and it will not run with my current Modbus setup.  The VFD Manual says it is a YL620-H It has a "Standard Modbus" and a "Non Standard Modbus" Modbus setting I assume that I should use the "Standard Modbus RTU" setting.  
My setting are as follows:
P0-02 = 2
P0-03 = 9
P0-10 =300
P0-12 = 300
P0-22 = 2
Pd-00 = 6 (19200BPS)
Pd-01 =3 (8 N 1)
Pd-02 = 1
Pd-03 = 5ms
Pd-04 = 0
Pd-05 = 1 (Standard Modbus RTU)
Pd-06 = 0 (current resolution 0.01a)
My Custom HAL is:

loadusr -W hy_vfd -t 1 -d /dev/ttyUSB0 -p none -r 19200

 setp hy_vfd.enable 1

 net spindle-vel-cmd-rpm => hy_vfd.speed-command 
 net spindle-cw spindle.0.forward => hy_vfd.spindle-forward
 net spindle-ccw spindle.0.reverse => hy_vfd.spindle-reverse
 
 net on spindle.0.on => hy_vfd.spindle-on

 net spindle-speed-fb => hy_vfd.spindle-speed-fb
 net spindle-current <= hy_vfd.OutA
 net spindle-comm-ok <= hy_vfd.hycomm-ok

 net spindle-at-speed <= hy_vfd.spindle-at-speed 

When I start LinuxCNC i do not get any errors but no VFD function.
any suggestions on how to see what is going on? 

the VFD manual is attached. 
Is there anyway to test to see where the issue is?  I did not change my USB to RS485 adaptor, and it appears to be working, at least communicating with the PC. 

 

A fix has been pushed for this. Sorry about the delay, we got a bit sidetracked...
 

PCW wrote:

Did you try

sudo apt-get install raspi-config

?

I'm not sure if it is compatible with our image. Some boot files are in subfolders

Ok, boot into another kernel on your system. then
sudo apt purge r8168-dkms
It should come back on a reboot
I suspect mint is the issue but I have had the same thing happen with Debian and re-imaged a few times until I tried this trick

Did you try