[Grbl_Esp32 Issue#694] RS485 VFD not running set_speed_command on “M3 S1000” or “M4 S1000”

#3 - RootCNC 于 2020-12-06

PS sorry for the long post!

#4 - bdring 于 2020-12-06

I'll read that when I get some time. If you rewrite it as below, I might be able to get to it sooner.

gcode sent --- expected behavior --- actual behavior (be brief)

Note: I only have a Huanyang spindle.

#5 - RootCNC 于 2020-12-07

I'll test the Huanyang spindle type out tomorrow - I believe this exhibits the same issue

#6 - RootCNC 于 2020-12-07

Testing the Huanyang spindle type, as per the previous setup:

- [X] 1. Perform reset of GRBL and send "M3".
Code Sent:
M3
Expected:
01 03 01 01 + CRC
Got:
010301013188
Working as expected

- [x] 2. NO reset to GRBL send "M5".
Code Sent:
M5
Expected:
01 03 01 08 + CRC
Got:
01030108F18E
Working as expected

- [x] 3. NO reset to GRBL send "M4".
Code Sent:
M4
Expected:
01 03 01 11 + CRC
Got:
010301113044
Working as expected

- [x] 4. No reset to GRBL send "M3 S2000".
Code Sent:
M3 S2000
Expected:
``
01 05 02 ## ## + CRC
01 03 01 01 + CRC
`
Value dependant on the S### portion of the Gcode - we're not interested in the value, just that this line is sent
Got:
`
01050206823B0D
010301013188
`
Working as expected - This was the first time sending a spindle command with a speed parameter. this has been noted to work fine for the first run but not for subsequent commands with the spindle speed parameter.

- [ ] 5. No reset to GRBL send "M3 S4000".
Code Sent:
M3 S2000
Expected:
`
01 05 02 ## ## + CRC
`
Value dependant on the S### portion of the Gcode - we're not interested in the value, just that this line is sent
Got:
Error - No change in spindle speed observed in RS485 serial data.

- [ ] 6. No reset to GRBL send "M5" and then "M3 S6000" (new spindle setpoint).
Code Sent:
`
M5
M3 S6000
`
Expected:
`
01 03 01 08 + CRC
01 05 02 ## ## + CRC
01 03 01 01 + CRC
`
Got:
`
01030108F18E
010301013188
``
Error - Again no spindle setpoint was sent over the Modbus, I might be getting confused but I am expecting the spindle speed command to be sent when the spindle command with a S parameter to update the VFD?

Unless I'm missing something, this is identifying there is a common issues between the two spindle types.
Kind Regards Pete

#7 - KingMo5h 于 2020-12-08

I think you have the same problem as him: https://github.com/bdring/Grbl_Esp32/issues/689

#8 - scottbez1 于 2020-12-09

Can you share what the debug lines say when you issue your S#### command, with VFDDEBUGMODE enabled?

It will look something like [MSG:Setting spindle speed to 10000 rpm (8000, 24000)]

Looking at the code, the most obvious reason I see that a speed command would not be sent is if the (bounded) RPM is the same as the most recently set (bounded) RPM -- in other words, even if you command 2 different speeds via g-code, if those speeds are both outside the bounds of the defined min/max RPM configured in your grbl settings then the bounds checks would force them to the same value and it would be expected for the second speed command to not be sent at all. It would be helpful to rule out this possibility before digging further.

If that is not what's happening here, I think it could be helpful if you could include the actual full RX/TX data from one of the failing test cases (i.e. without removing the specific speed values or CRC values) along with the rest of the VFDDEBUGMODE messages, so it's easier to check the data against the expected protocol in case that gives any additional clues as to what might be happening. I was not able to reproduce this on my (Huanyang) machine, even if I occasionally detached the RO pin on the RS485 transceiver at various times, so any additional clues or data you can provide would be helpful.

#9 - bdring 于 2020-12-09

I finally got a chance to test this. It is a pain because I need to move it to my office, and I don't have the right voltage.

!20201209_084627

The VFD RS485 class is a basic implementation, but I think it executes your test from a performance standpoint.

Here is my setup...
VFD PD011 is 120 // min RPM

Boot messages
[MSG:Initializing RS485 VFD spindle]
[MSG:VFD RS485 Tx:GPIO(14) Rx:GPIO(15) RTS:GPIO(13)]

Relevant Grbl settings are...
$Spindle/Enable/OffWithSpeed=On
$GCode/MaxS=24000.000
$Spindle/Delay/SpinDown=8.000
$Spindle/Delay/SpinUp=8.000
$Spindle/Type=HUANYANG

Here is a sequence of commands

M3 ;enters M3 with no speed
ok
$G ; show gcode modes
[GC:G0 G54 G17 G21 G90 G94 M3 M9 T0 F0 S0]
ok

M5 ; enters M5 mode
ok
$G
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]

M4 ; enter M4 mode no speed
ok
$G
[GC:G0 G54 G17 G21 G90 G94 M4 M9 T0 F0 S0]
ok

M3S2000 ; M3 spindle spins in correct direction
ok
$G
[GC:G0 G54 G17 G21 G90 G94 M3 M9 T0 F0 S2000]

We welcome any improvements and pull requests, but it takes a few days to setup and test. Some devs do not have the capability to test. It is very expensive to keep this equipment around just for testing.

#10 - RootCNC 于 2020-12-09

@bdring @scottbez1

Well.... I feel like a numpty. The golden bullet was the $GCode/MaxS=24000.000 command to set the spindle max point. Once you said it, it sounded so obvious! Thank you for your help! I cannot protary how happy I am to finally have the spindle control working on this CNC controller! I really mean it - so happy.

I think I managed to delve too deep into commissioning this new hardware and missed some of the simple stuff off, with being new to GRBL and all that (I'm coming across from Marlin so some methods of configuration are done differently - im still learning)

Solution:
I think we can close this issue and anyone reading this thread should ensure the following settings have been set for the control of ANY VFD:
``
$Spindle/Enable/OffWithSpeed=On
$GCode/MaxS=24000.000
$Spindle/Delay/SpinDown=8.000
$Spindle/Delay/SpinUp=8.000
`

Side note - @bdring I can see the RX message is not being displayed in your terminal? I don't see a response either in my terminal with the #define VFDDEBUGMODE` set. All I see is an empty RX message. Now, because I've got the spindle control working, I'm happy to leave it there but I am guessing I should see the returned RS485 message in the terminal window? I did probe the pad of EPS32 and the RX message is definitely getting there... so I'm none the wiser atm. Does the GRBL firmware use the status of VFD? or does it just keep the watchdog happy on the VFD?

Again thank you for your help and this great project - I cannot wait to do more stuff with it.

#11 - bdring 于 2020-12-09

I'll look into the debug mode.