Servostar (S303631)issue

[banksviolette]

I'm hoping someone with personal experience, or simply a better handle on Kollmorgen's servostar set-ups than mine, will be able to help me out. I've got a S30361 that I'm trying to get working, but regardless of what I attempt, I'm stuck staring at the same "F04...F06" error message, blinking away at the front of the drive. The official doc's states that F04 is "cable break, short-circuit, short to ground" while F06 is"motor temp too high, or temp sensor defect". The drive is able to read several feedback signals, but I've been trying to set it up using it's primary feedback method, which is w a resolver. The drives gotta serial/DB9 male port that the resolver is meant to connect to, and it also uses that port for connecting the motor's temp sensor/thermistor, so it makes sense that those two error messages would show up together. I've tried connecting two different motors, gone through and checked whatever wiring I can but I can't identify the issue. Since it seems to be happening independent of the motor, my feelings that its an issue w the drive and I'm not connecting something correctly: if someone who has worked with these, or understands this all, could suggest a course of action I might take towards enabling this thing, I'd be forever grateful. Thanks in advance
Oh, and -just generally- if anyone would like to describe how its been working w the s300/s600 series of servostar drives, I'd really like to hear your experience. I'm just getting fully committed to using servo's, and -while I've bounced around different layouts- I'm kinda set on Kollmorgen and Delta Tau as the direction I'd like to go. Any info you'd care to share would be of tremendous help to me.
Again, thanks in advance

[mike_Kilroy]

F04 is telling u the resolver is not wired correctly; are u going into the right fdbk connector? there are 3 to choose from.... resolver is X2 is for resolver. if u dont have resistance (20-100 ohms say) between pins 4&8 and also 3&7 u will get F04 if resolver picked in software...

likewise if resistance is not close to 0 ohms between pins 2&6 for thermistat then you will get F06.

i strongly suspect u r plugged into X5 instead of X2... x2 is 2nd from BACK on top; x5 is second from FRONT.... also I bleieve x2 is female and x5 is male as u state....

s300/600 are good drives that work well but if u r starting out new for new equipment consider the new AKD drive instead; it will increase ur performance probably 30% over the older s300/600 series - which are still probably 15-30% higher performance than most other equivalent servo drives IMHO too. unless u r using the macro interface then u gotta use the s300/600/700(newer and higher performance than the s300) series. even so, consider using the new ethernet/IP delta tau output into the new akd for top of the line and probably lower cost performance.....

[banksviolette]

Ok,
I'm definitely feeling like an idiot: you were dead on w your assessment, and I had managed to switch feedback connector slots somewhere during this entire attempt. That said, I do remember clearly having started w this issue while trying to connect everything w the correct slots. etc: it was somewhere during my endless tries at clearing the "F04.." error that I bumped myself into a different feedback port. I just went through and re-checked everything, and tried to start up the drive and - once again - error "F04...F06". I tried your tip for reading resistance, and from 2 and 6 thermistat pins I got no perceptible resistance, after cycling through every resolution on the multimeter. On pins 4 and 8/ 3 and 7 I gotta approx. equal "143.0" w meter at 200 ohms res., so I'm back at square one. Really, I'm beyond frustrated at this point so PLEASE any additional pointers or cues for steps I'm over looking would be greatly appreciated. Ok, thats a wild understatement: I'd be unbelievably grateful for anything that'll make this make some sense.
Thanks in advance,
Banks
Oh, and thanks for the advice as well on drives: gonna try and process that info once I've let my frustration abate a little first...

[mike_Kilroy]

1) I tried your tip for reading resistance, and from 2 and 6 thermistat pins I got no perceptible resistance
2) pins 4 and 8/ 3 and 7 I gotta approx. equal "143.0"

u do know i meant to measure the resistance on those pins ON UR CONNECTOR not on the drive side, right? we r not testing the drive for problem but ur wiring....

1) typical resolvers have 20-30 ohm resistance coils for sin & cos windings....of course u need the reference wired up to... so what kind of motor/res u have that has so hi resolver winding resistance? perhaps it is so wierd it is not compatible? We just finished a product retrofit design for a major machine tool builder where we had to build a dual channel amplifier for their wierd resolver to make it compatible with their control...

r u SURE u changed feedback type in drivegui.exe to resolver and not encoder or otherwise? that drive can use ttl encoder, sine encoder, endat, biss, stegman, resolver fdbks - u gotta pick the one u wil use and save it to eeprom memory and cycle power to use it.

2) easy one for now: forget the thermostat for now and just solder a jumper across those pins to eliminate the f06 error until u get control. u will ultimately have to have less than a few hundred ohms for this or a jumper.

[banksviolette]

Hi,
yeah, those were readings I took from the connector/motor side : I went back through and made absolutely certain the pinouts from the motor's connector's were correct and thats what my meter was giving back to me. I switched the meter's battery out to a new one just to be sure and thats what I got. I haven't been able to get my pc to register/recognize the drive yet, though I've gone through and made sure the correct com port/baud rate's been selected, so I didn't try selecting resolver in the drivegui's menu. I'll try all your suggestions again, and get back to you w my progress - again, I truly appreciate your help w this. Having that amount of money just sitting and blinking away at me is kinda driving me a little crazy, to be honest...
Banks

[banksviolette]

Oh, my apologies: forgot to mention motor type. I'm trying w a kollmorgen b series goldline servo, so thats what makes this all so doubly frustrating. I've also tried w a Pacific scientific r30, w the same ulcer-inducing results. Both motors are shipped out w resolver's as standard feedback, if I'm not mistaken, so they shouldn't be the source of the problem (I only tried reading ohm's offa the goldline - I'll try out yr suggestions, and swap in the pacsci, and see what the meter says w a different servo). Also, just to be clear, I've been using the bare minimum wiring set up that's sketched out in the s300 manual: random thought (and its not like theres much there to misinterpret) but sometimes euro schematics can throw me. Would there be anything that sorta-schematic that might be misinterpret-able (sorry for that: I'm apparently at the point where I gotta make up new words). Thanks in advance (again).

[banksviolette]

alright, slightly obsessive update, round who-the-hell's-counting: here's some supplemental info I haven't mentioned yet, thinking I was describing the relevant info and this was only tangentially related: when I switch the drive, after the 30 second-or-so lag that's supposed to happen, the first thing that appears on the display is "1.00". That will hold constant for a few seconds (maybe 15-30) then the decimal will switch to "100.", there'll be a brief blink as the LED's switch off, then the display will pop back w the "F04..."error. I did as you suggested, and placed a jumper btwn the thermostat leads, and that took care of the "F06" message, so that leaves me with this short-circuit issue. I've got resolver selected as the feedback method in the drivergui but no clue how I'm supposed to insure the drive's set for resolver if I can't get a connection btwn drive/pc.

[mike_Kilroy]

alright, slightly obsessive update, round who-the-hell's-counting: here's some supplemental info I haven't mentioned yet, thinking I was describing the relevant info and this was only tangentially related: when I switch the drive, after the 30 second-or-so lag that's supposed to happen, the first thing that appears on the display is "1.00". That will hold constant for a few seconds (maybe 15-30) then the decimal will switch to "100.", there'll be a brief blink as the LED's switch off, then the display will pop back w the "F04..."error. I did as you suggested, and placed a jumper btwn the thermostat leads, and that took care of the "F06" message, so that leaves me with this short-circuit issue. I've got resolver selected as the feedback method in the drivergui but no clue how I'm supposed to insure the drive's set for resolver if I can't get a connection btwn drive/pc.

- 1.00 is drive firmware display on power up so ok.
- how can u set resolver as fdbk type if u cannot communicate? u cant. just setting it in drivegui.exe program in ur pc doesnt tell drive of course. std on power up will prob be encoder so ur f04 is ok for now.
- to communicate is simple: pc db9 to drive db9 (front top). U GOTTA HAVE 3 WIRES ONLY - MORE AND IT WILL NOT WORK. 2<->3, 3<->2, 5<->5. thats all. then it will talk (iirc it goes at 32kb or something - doesnt matter, ur computer will set up to match every time - u dont set anything but right com port.
- bad news if ur ohms is right for the goldline motor: it has 30 ohm ref, 20 ohm sine and 20 ohm cosine. unless a VERY unique model; post complete part no if u want me to tell u for sure....

[banksviolette]

I've now tried absolutely everything, and still nothing. In fact, it seems like I've taken a step backwards: going by your suggestion I jumpered the two thermostat positions in order to at least remove the f06 error message from the equation. That worked for a short while but now its magically re-appeared even though theres actually zero physical connection btwn the drive and the motor's thermostat. In regards to the serial cable, I had been sure I was using a null modem throughout but I went back and checked every cable I've used and they were all null modem's. As my last attempt I wired up a db9/ serial connector w shielded cable only connected to 2,3, and 5 w 2, and 3 crossing over - any of the documentation I've got only specifies a null modem cable not one stripped down to a 3 wire connection, but I tried that just in case. Absolutely nothing I do seems to affect the drive displaying f04/f06. I did find out the drive originally had a devicenet expansion card connected as an after-market addition, which was removed when this unit was sold to me: could that possibly account for any of whats happening? Everything I've found online regarding expansion cards concerns installation: I haven't really read anything about what effect removing one might have. Is there maybe a forced reset/ method of clearing the drive's memore to reset it to its original setting? I'm completely at a loss here, and you're so far the only person connected w Kollmorgen I've gotten even half a response from. Anything else you could suggest would be beyond appreciated,
Oh, turned out something weird was happening w my multimeter: it was just coming up w random readings across the board. I opened it up and blew air to clean it, just in case, and put another set of batteries in it and now I'm getting the resistance you described for standard resolvers.
Banks

[mike_Kilroy]

sorry to hear still issues. do keep in mind that until u change the drives internal parameter to resolver feedback type it WILL give f04. so u gotta get communications.

perhaps ur 2,3,5 pins are bakwards from reality? it is VERY easy to count 1 from the wrong side of the db9 and so wire it wrong.......u need to find a db9 connector that has the numbers shown next to the pins maybe to be sure?

of course u could have a serial input that is blown but i have yet to see one and folks have wired them wrong over the years a lot....

if you have more than 3 wires in ur serial cable it will not work - this is just a fact and no amount of guessing why will change the fact. 2-3,3-2,5-5 and no shield hooked up. simple. this WILL work.

r u trying the wrong program?? waht is the program name u r trying to use? motionlink? motionlink plus? workbench? s600 drive.exe? none of these will work. no amount of trying or guessing will make them work. u gotta have the driveGUI.exe made specifically for the s300, freely available at kollmrogen.com

not sure why f06 is back unless the jumper came loose, but this is beside the point now; you gotta get communciations serially.

what r u using for cmputer? laptop? does it have a REAL serial port or usb adapter? some usb-serial adapters are so bad they will not work; most will.

r u using a computer set up to talk to ab PLC or some other serial device? if so, it will hog the seria port so u cannot share it for this - u gotta kill those other programs first.

hang in there u will get it!

[banksviolette]

I've tried w usb-to-serial adapter from my laptop, then w an older desktop thats got a serial port. The serial cable I'm using right now has only the three wires 2-3,3-2, 5-5 wired up. I've only had driveGUI installed: this last attempt, when the startup for driveGUI would deliver the "connect to a drive"? prompt, when I answer yes, I'll get an "invalid parameters" reply in response, w the drive still blinking its f04f06 error (even though the thermostat's still disconnected). I've checked and re-checked that my connections correspond to S4,S3, etc and they're all connected correctly. What you're saying about the serial cable is whats my real source of stress, since I haven't seen any mention of only connecting the three wires anywhere in any documentation from kollmorgen. That leaves me thinking there must be something else I'm just missing thats obvious, but just wasn't made clear in the manual. Would there be some sequence I'm supposed to be performing at setup that maybe I'm just missing? I cannot tell you how frustrating this has turned out to be, so whatever help you could provide would be amazing

[banksviolette]

Theres no way to setup the drive via the display/ two arrow keys? Maybe if there was a forced reset or something along those lines? I dunno, I'm just pretty desperate at this point and it doesn't seem that the straight forward method of connecting to the drive is getting me anywhere