I failed to mention that this configuration is for connection via RS485. The mitsub_vfd module does not use modbus; it uses the Mitsubishi Inverter Protocol.
> On Mar 1, 2024, at 12:55 PM, Thaddeus Waldner <thadw...@gmail.com> wrote: > > I recently set up a Mitsubishi D700 to work with Mitsub_vfd > > These inverters are highly flexible in how they are configured to respond to > control commands. I spent many hours of trial and error to get the correct > combination of parameters to even get it to respond to network commands. What > tripped me up initially was that the drive must be reset by cycling the power > to make any changes take effect. > > It has a handy list of all the non-default parameters. I have attached them > below. Everything appears to work, though there is some inconsistency in how > manual seed control works in gmoccapy. > > > The E500 could be a whole different animal but maybe this will help. > > > pr name value > 1 Maximum frequency 300 > 2 > Minimum frequency > 30 > 3 > Base frequency > 300 > 7 Acceleration time 2.5 > 8 > Deceleration time > 3 > 9 > Electronic thermal O/L relay > 9 > 13 Starting speed 20 > 18 High speed maximum frequency 300 > 19 > Base frequency voltage > 200 > 20 > Acceleration/deceleration reference frequency > 300 > 29 > Acceleration/deceleration pattern selection > 2 > 41 > RUN key rotation direction selection > 5 > 72 > PWM frequency selection > 15 > 77 Parameter write selection 2 > 82 Motor excitation current 80 > 84 > Rated motor frequency > 120 > 96 > Auto tuning setting/status > 21 > 117 > PU communication station number > 96 > 120 > PU communication parity check > 0 > 124 > PU communication CR/LF selection > 0 > 160 Extended function display selection 0 > 298 > Frequency search gain > 39 > 340 > Communication startup mode selection > 1 > 551 > PU mode operation command source selection > 4 > > Hope this helps!, > > Thaddeus > > > >> On Mar 1, 2024, at 7:34 AM, lloyd wilson <llwilso...@rochester.rr.com> wrote: >> >> I'm using a Mitsubishi E500 VFD for spindle drive on the VMC I'm >> retrofitting & can't get variable speed to cooperate. The mitsub_vfd program >> operates properly (I think)- run/stop behaves as expected, speed commands >> are generated and accepted by the VFD, but the motor speed stays the same. >> I hacked in a couple of debugging statements to show the dialogs (running in >> halcmd): >> >> setp sp.motor-cmd 50 >> halcmd: 01ED11388EF SENT: 0x5 0x30 0x31 0x45 0x44 0x31 0x31 0x33 0x38 0x38 >> 0x45 0x46 >> 7!DEBUG: ,0,1, 0x6 0x30 0x31 >> >> show pins >> >> ........ >> >> 4 float IN 50 sp.motor-cmd >> >> ....... >> >> then >> >> setp sp.motor-cmd 80 >> halcmd: 01ED11F40F6 SENT: 0x5 0x30 0x31 0x45 0x44 0x31 0x31 0x46 0x34 0x30 >> 0x46 0x36 >> 7!DEBUG: ,0,1, 0x6 0x30 0x31 >> >> show pins >> >> ........ >> >> 4 float IN 80 sp.motor-cmd >> >> ....... >> >> the messages are properly formatted per the Mitsub manual & replies show no >> errors >> >> --but the test motor keeps running at the same speed. >> >> Anyone have a clue where to look for the solution? >> >> as always, thanks >> >> -ldw >> >> >> >> _______________________________________________ >> Emc-users mailing list >> Emc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-users > _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
