Mitsubishi VFD Modbus cant get it work

good morning chris!

today i have more time to make some tests.

first thing what i need to know...
do you have only set the parameters for modbus on your vfd?

my settings on the vfd:
pr79 1
pr117 1 (for 2 stop bits)
pr118 96
pr119 0
pr120 0
pr121 10
pr122 9999
pr123 9999 (now at 100)
pr124 0

do you done some changes in your mitsub_vfd (py2ver)?
i must add a line... why? i dont know... do you know the reason?
my changes in mitsub_vfd :

i add self.ser.close()

self.ser.close()
self.ser.open()
self.ser.isOpen()
except:



with pr123 set to 100 or another value i get no error.


what i try:
i have some arduino boards... original,fake... original are with ftdi232 .. fake with the ch340... i can send and recive to both.. fake and orignial... so i think the problem is in the area of the code and / or usb...

i have 100es of old hdds... and i have some old notebooks ( thinkpads from ibm) they have rs232 db9 connectors... a friend have a rs232 to rs485 adapter... if he is back from work i can go to him and test with original db9 rs232 to rs485... because.. i think... why i must add the line to your code to get the component work without error that it cant connct to the usb port?!

another thing.. back to the vfd Parameters....:
79 need set to 1 or 0, i set it to 0 BUT pr 340 need set correct..iset it to 1.............................WHAT HAVE YOU SET?
if we set parity to none then we need 2 stopbits.. all other settings should be not correct.

549 must set to 1 to use rtu strandart, if its set to 0 then its a mitsubishi protocoll, ................................WHAT HAVE YOU SET?!!


thanks chris! hope you answer me!!! from where are you? i am from germany

I thought I'd add the official docs for communication with the 720.
Then I hopefully won't make anymore errors.

my settings on the vfd:
pr79 1
pr117 1 (for 2 stop bits)
pr118 96
pr119 0
pr120 0
pr121 10
pr122 9999
pr123 9999 (now at 100)
pr124 0

117 is the station number not stop bits.
119 is stop bits and should be 1
122 sets the time out not 123 (sorry my bad)
123 should be 9999 (sorry my bad)

you might check pr 549 protocol select - I've never changed (even looked at) it on any of my vfds but would expect that 0 is the right setting.

Chris

I'm from Canada.
I have never set pr340

I'm using the computer link protocol - plugged into the PU (operator panel) receptacle.

hi chris... i doublecheck all and ... i cant get it work with the mitsub_vfd.py ... i dont know why..

with classicladder i can read the vfd and see all parameters...

now i found the vfdmod comp. it looks good..but... i am in struggle with all the registernumbers and functionnumbers........ i need only some registers in hex format.. but my brain overheat... i wrote to the vfdmod thread.. hope someone help me for the last or 3 steps..


a friend use a mitsubishi vfd with your comp over years without problems.. but he doesnt need change the line or do something... all works after linnuxcnc install.

i installed linuxcnc to a old notebook and check it with 2.7 and 2.8 ... doesnt work.

me again...


i played a little bit with classicladder.

if i change something with mach3 (seperate notebook)and plugged the usb rs485 into my linux pc.. and look to classicladder i can see the status.. run fwd/rev... freq... volt,amps,temp.

my programming is not perfect.. but.. is it possible to write the mitsub vfd plugin in c?

i think the problem is python and or python serial.....

wait wait wait... computerlink?!

give me please 5 minutes... i use rj45 connector.... i will load a picture one moment

chris... for the future..and all the idiota like me.... please please write BIG into your description that pr 549 must set to 0!!!!

pr 549 switch between rtu and computerlink....ITS NOT RTU

it works....

5 days... i am brain amputated..4 strokes...mentally retarded

YAY! I am so sorry we didn't get there sooner. I will add the info to the docs.

Older VFDs don't have builtin modbus capability.They all seem to allow computer link - as long as they have a PU connector.

Information for modbus connection would be good info too.

I don't know why the python interface needs to be closed then opened. I only noticed it in my 2.9 version, but I used Linux Mint while I use Debian in my 2.8 version.
I seems not to hurt to close then open so maybe I'll just add the code.

Any other improvements please bring to my attention - you (and apparently your friend) are the only ones that I know that have used it.

Chris

chris.. no problem

is it possible that you add 2 functions?

the scale of the feedback and the scale of the commanded rpm/hertz?

it would be great to get divide function for all scale function

and .... do you mean its hard to get it work as modbus rtu?


for me its not a problem to change pr549 between the use of mach3 and linuxcnc.. i think when all done i can forget mach3.

the last project is to get my turret work.... on mach3 it was no problem... but linux... ohohooh... but i learned much...


and my friend has set to the mitsubishi protocol.... thats why it works.. and this was the information i need...


which lathe you have??

i have a emco c5cnc from the junkyard... in never used optic and the emco f1..never used optic..from the junk yard.. i payed only the weight....

thanks for your time , your brain , thanks

There is scale pin for for amps, power, feedback and command.

Not sure what you mean be divide function.

I've never tried modbus - I just meant the info you have about using modbus on classicladder may be useful for someone else.

I have a 1980s vintage Okuma LH35 flat bed CNC lathe.
I also have an emco CNC mill.
I wish I had a junkyard like yours!

Linuxcnc has a steep learning curve but I think it's worth it most of the time.
Glad you stuck too it!

Chris