Advanced Search

I have a hard time seeing that this could be intentional design as randomly changing the behavior of MDI commands without any hint at all to the user can be very dangerous.

An MDI move command in G90 can yield very different results compared to one in G91.

@scotta it would be really helpful if you can post sample config files. Or if I need to completely erase skr3 and reflash using stm32cube programmer?

I didn't ever say thanks for your reply PCW so a belated thank you! Yes, the 7i96s. The above is working with the VFD set in 'pull-up' logic which is great. I still need to connect the VFD digital outputs (ST1 & STR) to the 7i96 inputs to signal when the motor is running at the commanded speed and when there is a fault. I also initially forgot to configure the PWM signal in pncconf initially.

A few more questions:

1) My VFD programming has the following setup:

• Minimum frequency of the motor: 100Hz (6000 RPM)
• Maximum frequency of the motor: 300Hz (18000 RPM)
  
  
  In pncconf I set the max spindle speed to 18000 which I can see in the machine.ini file:

  [SPINDLE_0]
  ...
  MAX_OUTPUT = 18000.0
  OUTPUT_SCALE = 36000
  OUTPUT_MIN_LIMIT = 0
  OUTPUT_MAX_LIMIT = 18000

   
  However, in the same file, I see the qtdragon display section with the following:
  

  [DISPLAY]
  DISPLAY = qtvcp qtdragon
  ...
  MAX_SPINDLE_0_OVERRIDE = 1.000000
  MIN_SPINDLE_0_OVERRIDE = 0.500000
  DEFAULT_SPINDLE_0_SPEED = 500
  MIN_SPINDLE_0_SPEED = 100
  MAX_SPINDLE_0_SPEED = 2500
  ...

  
  When I select FWD/REV in the gui, I am seeing the spindle spin in the correct direction and the VFD is correctly driving at 100Hz (i.e. the minimum safe speed for the spindle set in the VFD programming). Do I need to manually change DEFAULT_SPINDLE_0_SPEED, MIN_SPINDLE_0_SPEED, MIN_SPINDLE_0_SPEED? in the QtDragon [DISPLAY] settings in my .ini file or should pncconf be sorting this out?