Mitsubishi VFD Modbus cant get it work

So the settings are as I specified or are you assuming if it works in mach3 it should work in linuxcnc?

db9 to an opto22 converter card.
maybe 6 months or so ago.

I use 2.9 and python3 now and it does have some problems.
I had to add the open, close, open command for some reason related to linux it seems.
and monitoring doesn't work right.

Chris

The blank debug statements indicate the VFD is not responding at all.
You can uncomment the print statements to see what commands are being sent.
Is the mach3 driver sources available? that might be interesting.

It would also be useful to know is the error LED lights up on the VFD after the driver is started -indicating the timeout has probably tripped, which you can change on the vfd for testing.

no mach3 driver is inside mach3....

i only write to 2 registers...

register 8 for fwd or stop and 13 for the freq.

do you know quick the parameter to set the error led?!

i think... when your vfd works... the problem is usb? but do you know a reason why on mach3 its no problem?

mach3 and linux on the same pc.. i quick change sata cable.. its on 2 different hdds

There are literally hundreds of reasons it does work with mach and not with linux.

The fact you don't answer my questions as I ask them makes the process longer.
It seems that you have programming experience - why not try debugging the driver?

i done debugging yesterday and i read with a terminal on my notebook parallel to rx and tx...

rx is dead and tx sends commands but the commands different between linux and mach. then i start building a rs485 to rs232 converter.

i use a ftdi232 and a max485.
same shit different day.. mach3 works but on linux i have no rx.

now i read manual.. where to set error led.

is saw on my manual that pr 119 0=1 stopbit and 1=2 stopbits.

could you tell me if its a failure from my manual or we have different vfds?!

That is an error in the info I posted - I will fix the docs thank you.
1 = 8 bit data, 2 stop bits

PR 123 sets the timeout time (which will set the error LED)
If you set it to 9999 it will never light the LED on a communication error.
Any other setting is the time in ms to wait for a response before setting an error.
This time out will not start until a connection is established.

So you can use those facts to imply whether the VFD started communicating and failed.
If you set a timeout and the LED never lights, then that implies the communication never even started. If it lights then the VFD a least recognised the communication try.

Then by setting it to 9999 and trying again to see if it's intermittent errors. (intermittent errors would allow the VFD to work somewhat)

It could be a linux serial driver problem. or the USB converter timing problem, or the python driver problem, or the VFD not set up as the python driver expects.