New VFD comms timeout -12

- hy_vfd component has an option for debug mode, which may help:
linuxcnc.org/docs/html/man/man1/hy_vfd.1.html
- make sure you have the vfd set up to accept serial communications (see doc above)
- it's important to share the _exact_ error message you get, otherwise it's just simply impossible to even try to find out where it is comming from.

Tried using -g in the loadusr command, told me invalid option for g. So not sure how to get into debug mode.

this seems to work for me:

I do not know how to see any errors from when I try to run it from within Axis. I assume there is the same error.

open a terminal and run:

This will bring up the config picker, pick your machine config and all debug messages will be printed to the terminal window.

This tells you the following:

1. The component is sending a request to the vfd starting with '[01] [01] ..'
ie it's calling device with address '01' and the function code '01' (ie read coil status) ....

2. In modbus protocol a response starts with echoing the device address ie '01' followed by the functionn code, ie also '01' in your case.

3. Note that the response does not start with [01],[01] but [01], [81]. The '81' tells you that the device has sent you an exception response to your 01 query. The next byte in the response, ie [02], is the exception code (which would indicate that you requested and illegal data address ).
www.simplymodbus.ca/exceptions.htm

Not sure but it seems a bit odd to me to read coil status [01] from address [03] [05] but then have the total number of coils [00] [00]
www.simplymodbus.ca/FC01.htm

 

MAYBE the actrual issue here is the register to say enable spindle is the incorrect register in my drive, so the response is illegal data address?

Note that it says that it is 'reading setup parameters:' which fails. Enabling the spindle would not be a read function.

Is it odd that there is only 6 bytes received then a time out occurs?

The component does not handle exception responses (which are only 5 bytes), I guess.

I'm afraid I cannot help much more as I have no information about the vfd or the setup values for the component.

Could I have some type of issue with the comms and data is getting corrupt?

No, modbus uses a crc checksum (ie the last two bytes of the messages). If your request got corrupted the crc would be wrong and the vfd would then ignore the request and you would not receive any response.