I am trying to use a Masterdrives VC (6SE7026-0ED61) with an asynchronous motor (1PH7137-2HF00-0BA0) as input for a test-rig for a continuously variable transmission. I got both the motor and the drive from a previous installation that hadn't been used in several years. All the people that had experience with the drive are no longer available, and when I asked support they told me to re-parametrize the drive.

The process I tried to follow was:

P100 = 4; P060 = 5; P115 = 2, then P115 = 4 and finally P115 = 5.

However, after doing the P115 = 2, I get warning W080 before P115 = 4.

Afterwards, when trying to start the drive, I get fault F098. The manual is very cryptic about a possible counter-measure, and it mentions two parameters that are not on the list on DriveMonitor.

Any help with this matter would be more than appreciated.

Hello Graeme, and thanks for the response!

It took me a while to respond because I've finally found a way to make the motor run, although it's not optimal and not how I intend to do it. Allow me to explain it further.

Indeed I was oversimplifying a bit because I thought a lengthy entry would not be read. Yes, the drive and motor were paired about 10 years ago, and they were both used on a different test rig. They had been standing at the lab for around 8 years. As far as I can tell, the motor is selected correctly, and the encoder is correctly configured.

Customer support told me the easiest was to do a full reparametrization from factory settings, since it wasn't clear (and still isn't, to be honest), why the motor wasn't working properly. I have the idea that it has to do with the encoder. Either it's not properly connected electrically, or incorrectly setup, or it might even be mechanically faulty. If you have any ideas as to how I could test it, I would be really grateful. I checked the electrical connections and everything seems to be alright, but I'm not getting a signal out of it, apparently.

Yes, the drive had originally been configured with P100 = 4. I did a backup of the full drive, and then reset everything to factory settings. Then I did identification of the motor following P115 = 2,4 and 5. I set P100 = 3, and now the motor follows the setpoint given by DriveMonitor. I checked the actual speed against a handheld laser tachometer, and it is following the setpoint within a 0.2 rpm drift, which is more than acceptable.

My problem right now is that I'm trying to give a setpoint speed through the Analog Input 1 on strip X102 (pins 5 and 6), and this signal comes from a DSpace box. I already checked that there is actual voltage coming from the channel on DSpace, but the motor only moves if I give it a setpoint through DriveMonitor.

On the other hand, yeah, I think I'm lucky that after 10 years at standstill, the thing didn't explode. I did have a fire extinguisher at the ready, you never know :P

Regarding the parameters, yes, P130 does exist, and the other one was P151. The irony is that Siemens here in the Netherlands had no idea there was a typo in the manual, so good for them.

Hey there,

Well, I checked everything and P443 = 11, P151 = 1024, P130 = 11. I tried the cheating method of just spinning the motor by hand, but I got nothing on r002 and r015. r015 does show the value of the speed when the motor is rotating given a setpoint through DriveMonitor, though.

I also checked that the encoder had the appropriate voltage supply (it's 14.96V).

Finally, I rechecked my wiring with dSpace, and even spliced the cable with which I'm providing the analog input to see if I was actually putting a voltage in. I am. Even parameters r446, r447 and r637 show the actual percentage corresponding to the voltage I introduce through dSpace, however these are for some reason not being taken into account. Even when all three previously mentioned parameters are at, say, 30%, parameter r014 still shows a setpoint of 0 rpm.

Of course! Here it is.

I've gone through the manual and tried to change things but so far I've been completely unsuccessful in order to make the motor run through dSpace. I want that because I need that motor to follow a particular speed profile that I don´t know how to generate in DriveMonitor.

Hello again!

As mentioned, I changed P443 = 11, and removed the additional setpoints. It still doesn't take the analog signal. As I said, I'm sure it's getting it because it is shown in the previous parameters, but for some reason the Setpoint at r014 doesn't change at all. Moreover, when I try to start the drive with the buttons instead of with the computer with DriveMonitor, it doesn't work.

There is only one digital input being used, which is for P558 (SrcQSTOP). This is wired to an emergency button. The thing is that even when the motor is running with a setpoint through DriveMonitor, when I press the emergency stop button, nothing happens again.

I'm feeling tempted to once again restore the drive to factory settings, do the motor parametrization, and finally finding a way of setting it up for analog setpoint input. I really need to have this drive working through dSpace.

It seems to me (with my very limited knowledge on the drive), that even though the analog input is being received correctly, it is being overwritten or ignored by some other parameter. Moreover, I can't understand why the emergency button doesn't work.