MSM does not do anything with DRO 39 (RPM) except place it on a screen (the run page). Maybe this would get mach to stop updating DRO 39 and thus let the vistaNC plug-in control it. If it is enabled and mapped to a parallel port & pin, disable it (as you are not feeding the PP with an index signal anyhow). Look in ports and pins and see if you have the index signal enabled. An interesting question to consider would be : Is there a simple way to get mach to not update DRO 39?ġ) startup your system, open the mach script editor and enter this line:ĭoes this convince mach to let the DRO be updated by the VistaCNC plug-in?Ģ) I don't know for sure, but I'd expect that mach only updates the RPM dro if it has an index signal configured as an enabled input. OK, let's go with the theory that both mach and the VistaCNC plug-in are trying to update DRO 39 and Mach wins. That would be the same change/solution that the Huyaung guys use.

I suspect that you will then see RPM values from the plug-in in dro 2222. If you want you can modify the MSM run page to display DRO 2222 instead of 39 (and set the vistaCNC plug-in to update 2222 instead of 39). The VistaCNC manual states that some versions of mach won't let it update DRO 39 - this is why they have a configuration option to have the plug-in update a user space DRO (2222). My best theory is that this is a plug-in coding issue. My suspicion is that there is a problem between the plug-in and mach - in that they both think they are updating the DRO - and since mach is not getting index pulses (as the pulses are only going to the vistaCNC hardware and hence to their plug-in), mach is setting the DRO 39 value to 0 (which is what mach sees as it's input signals).Īlas, I think this has to be referred to plug-in vendor for consideration as MSM does not use any plug-ins as part of it's implementation (a design decision made explicitly to avoid just this type of conflict). This infers to me that mach itself always sets the value of DRO 39 - unless this interface is called (or some equivalent interface from the plug-in level). Valid parameters are:ĭescription: RPMOverRide When this parameter is set to 1, the True Spindle Speed DRO (OEM DRO 39) is made writeable, over-riding Mach3s normal calculation of True Spindle Speed. The parameter whose name is given by ParamName is set to the value given by ParamVal.

Each Mach3 parameter is identified by name. This function allows a number of Mach3 internal parameters (not to be confused with Gcode parameters) to be set. Sub SetParam(ParamName As String, ParamVal As Double) Normally, the value of DRO 39 can't be updated by any entity other than mach - consider this excerpt from the Mach programmers ref manual: What DROs a plug-in updates is totally up to the plug-in - if a plug in attempts to 'take over' DRO 39, it has to cooperate with Mach to so so. Now then, plug-ins tap into a very low level of Mach.

Huanyang vfd plugin for mach3