Quote Originally Posted by Mr*Beaver View Post
I've posted a basic wiring diagram but the post is waiting to be approved.

The arduino is an analogue signal between 0-5v. The vfd takes this and sets the speed based on the voltage provided. Dcm and for need to be connected for the spindle to turn on.

Vd002 is set to 1, vd070 is currently set at 1. I did try using frontal controls and had no issue when using the start/stop button on the vfd.

The main change is the board I'm using, the shapoko board wasn't suitable for this build.

The vfd is earthed, so is the spindle and the arduino board.
Thanks for that.

Firstly - has this behaviour started when you connected the arduino and configured the VFD for 0-5V operation? Or did it start when you move the machine into the garage? (or did you big-bang both changes together?)

Particularly relevant to the problems being encountered during the move to the garage: I'd be inclined to examine your RCD and understand if it's a Type-A or a Type-B - the latter being recommended for frequency convertors (e.g. VFD). Google the two types to understand more if you want to pursue this.

If the problem was introduced by the Arduino - then, first-off you know the Arduino analogue/PWM outputs are not analogue outputs, but a digitally switched 0/5V PWM output?, I've not seen anything that gives me confidence that this would work directly connected to the ACM/VI input to the VFD. If it does, then it's likely more by luck than by design. Normally you connect a PWM output through some form of integrator to generate the analogue output (many cheap BoBs provide this functionality - and that might be an option to explore). My thoughts are around what the VFD may be trying to do with an VI input that alternates 0/5V a thousand times a second. One thought - flash the arduino to set the PWM output to ONLY 0% or 100% (and no-where in between!) - or better still remove any of the PWM initialisation and drive it as a discrete output - again, only 0 or 1. If that cures your problem then it's the PWM behaviour that's the problem and is resolvable. If you don't fancy changing the code, then pull a 5V supply from the arduino and drive that into the VI input, instead of the PWM drive - you'll only have on/off control, but it'll help isolate the problem.

If you try the above and the problem remains (with the VI connected only to 0V or 5V) then... try disconnecting whatever PSU you're using to drive the arduino - power it through the supply socket using a PP3 battery (it won't last long!) - if that cures the problem then I'd be inclined to dump the USB PSU that you're driving the ardy with (I'm thinking what can cause an earth-leakage the the RCD is picking up)