Okay that was it!
It booted up and the errors were only with joint cfg. I even got the axis to rotate!
NOW I'll get back to the MOC. If anyone can give me a quicker way to update it without restoring, that would be awesome!
Okay that was it!
It booted up and the errors were only with joint cfg. I even got the axis to rotate!
NOW I'll get back to the MOC. If anyone can give me a quicker way to update it without restoring, that would be awesome!
you can just load the moc directly.
To be honest I don't know another way to load the MOC...
EDIT: Just found the utility/extaxis cfg files. I never installed the M7C1B1 file, which I'll do now. I have an SMB connected to X5 on connector board 1, and my ext axis is on Node 1 (X1 Y1 etc) in plug R2.SMB 1-2. Sound correct?
Now it won't even restore.. I select the backup, hit OK, and it beeps but nothing happens. Stays on the same screen.
EDIT: I took a break, I can fix this by reinstalling the system with its standard MOC. Maybe I should try a DC2 + GT setup again, as an m2000 type B. Kind of shooting in the dark at this point!
Does anybody have a overview drawing (not a block diagram) of how everything hooks together? Something like what I drew in the first post here would be awesome. Preferably with a DC2T rectifier. That would make me a happy man!
Okay, so I added back in the expansion board, axis board, and ran the SMB2 to port X5 on the expansion board. I have the ethernet cable originally plugged into connector board 1 X20 (Drive system 2), plugged into X20 on the expansion board.
At first I booted and only had a few errors, now when I reboot it's back to the same handful.
I'm super lost now! I'm going to try switching SMB ports now, using SMB 3-6 instead, copying motor axis 11 from Saaboholic's diagram. Would this be node 2?
Common log messages
1. 10045 Status: System restarted 0210 17:03.10
An already installed system
was restarted.
2. 10045 Status: System restarted 0210 17:03.29
An already installed system
was restarted.
3. 10211 Warning: Execution cancelled 0210 17:03.45
The restart will clear the execution
in task MAIN of a
STOP system event routine
4. 10008 Status: Program restarted 0210 17:03.45
The task MAIN has
restarted to execute.
The originator is
unknown.
5. 40223 Error: Execution error 0210 17:03.55
Task MAIN: Fatal runtime
error
6. 10005 Status: Program stopped 0210 17:03.56
The task MAIN has
stopped. The reason is that
an error has occurred.
7. 20187 Status: System dump file created 0210 17:04.3
A file was created with internal
debug info about the system.
File path:
/hd0a/Outshaped Machining 7Axis/SYSTEM/INFO/dump53_info.log
Operational log messages
1. 10045 Status: System restarted 0210 17:03.10
An already installed system
was restarted.
2. 10045 Status: System restarted 0210 17:03.29
An already installed system
was restarted.
3. 10211 Warning: Execution cancelled 0210 17:03.45
The restart will clear the execution
in task MAIN of a
STOP system event routine
4. 10008 Status: Program restarted 0210 17:03.45
The task MAIN has
restarted to execute.
The originator is
unknown.
5. 10005 Status: Program stopped 0210 17:03.56
The task MAIN has
stopped. The reason is that
an error has occurred.
System log messages
1. 20187 Status: System dump file created 0210 17:04.3
A file was created with internal
debug info about the system.
File path:
/hd0a/7Axis/SYSTEM/INFO/dump53_info.log
Hardware log messages
No message to show!
Motion log messages
No message to show!
Program log messages
1. 40223 Error: Execution error 0210 17:03.55
Task MAIN: Fatal runtime
error
Operator log messages
No message to show!
IO & Communication log messages
No message to show!
User log messages
No message to show!
Internal log messages
1. Error: rhaltts.c 314 os_sem_wait/safevt_rhalt failed 0210 17:03.44
rhaltts.c 314 os_sem_wait/safevt_rhalt failed
2. Error: puscfg.c 1323 Can't connect to the servo 0210 17:03.44
puscfg.c 1323 Can't connect to the servo
3. Error: puscfg.c 1344 Can't connect to the ipol 0210 17:03.44
puscfg.c 1344 Can't connect to the ipol
4. Error: puscfg.c 1323 Can't connect to the servo 0210 17:03.44
puscfg.c 1323 Can't connect to the servo
5. Error: puscfg.c 1344 Can't connect to the ipol 0210 17:03.44
puscfg.c 1344 Can't connect to the ipol
6. Error: mecsta.c 360 couldn't find 'any ipol instance' error -1 0210 17:03.44
mecsta.c 360 couldn't find 'any ipol instance' error -1
7. Error: mecsta.c 382 couldn't find 'any servo instance' error -1 0210 17:03.44
mecsta.c 382 couldn't find 'any servo instance' error -1
8. Error: mecsta.c 429 couldn't find 'man instance' error -2 0210 17:03.44
mecsta.c 429 couldn't find 'man instance' error -2
9. Error: mecsynpr.c 331 couldn't find 'any ipol instance' error -1 0210 17:03.44
mecsynpr.c 331 couldn't find 'any ipol instance' error -1
10. Error: cabsta.c 403 couldn't perform 'sys_get_stored_object' error -1 0210 17:03.44
cabsta.c 403 couldn't perform 'sys_get_stored_object' error -1
11. Error: cabts.c 2515 Cabsta init failed 0210 17:03.44
cabts.c 2515 Cabsta init failed
12. Error: ipol.c 9771 os_sem_wait failed 0210 17:03.45
ipol.c 9771 os_sem_wait failed
13. Error: tsksup.c 262 Assert: sem_wait_status == OK, file ipol.c, line 97
0210 17:03.45
tsksup.c 262 Assert: sem_wait_status == OK, file ipol.c, line 9771
14. Error: servots.c 1213 Not allowed if servo task not initialized OK 0210 17:03.45
servots.c 1213 Not allowed if servo task not initialized OK
15. Error: hpjts.c 917 sys_get_stored_object status:-1 0210 17:03.55
hpjts.c 917 sys_get_stored_object status:-1
16. Error: rlsset.c 4352 Not possible to get any stored object for IPOL 0210 17:03.55
rlsset.c 4352 Not possible to get any stored object for IPOL
17. Error: servo.c 432 servo: IPC send error -6, cmd = 19 0210 17:03.55
servo.c 432 servo: IPC send error -6, cmd = 19
18. Error: servots.c 1213 Not allowed if servo task not initialized OK 0210 17:03.56
servots.c 1213 Not allowed if servo task not initialized OK
19. Error: servots.c 1213 Not allowed if servo task not initialized OK 0210 17:03.56
servots.c 1213 Not allowed if servo task not initialized OK
20. Error: hijts.c 8886 sys_get_stored_object status:-1 0210 17:03.56
hijts.c 8886 sys_get_stored_object status:-1
Display More
Attached is a circuit diagram of the positioner interface for a 500C positioner (single axis), it shows you how the SMB is hooked up on the last slide/page.
EDIT - yes, X5
This is using A83, the expansion board. I was using only A82 (connector board 1)! I'll put the expansion board back in and see what happens.
none of the 2400's have two
Thanks for the reply.
They don't have two SMB's? Not sure what picture you're referring to.
EDIT: The motors ARE Elmo's, on this arm. I'm not sure what level of Frankenstein I'm at though, what with the 7 axis SMB in the base and the 6400 rectifier it came with
That's what I needed, thank you! I'm plugged into X5 now (board pos 2, node 2 in MOC) but both that and changing names give me the same servo.c / rlsset.c / hijts.c errors.
I'm currently going into R2.SMB 1-2, I'll make a plug to go into R2.SMB 3-6 and copy Motor Axis 11, I guess.
Whoa, do I just plug the smb2 into x5? Measurement system 2?
That makes sense, I'll try changing the names.
So to connect another SMB, I do essentially what I said before, flip the SDI/Os's, but do it in the controller? I guess I could break it at the connector board easier than splice in halfway.
Really wish the external axis manual had circuit diagrams in it, there's nothing laid out very clearly for this!
No luck today. I tried restarting with the bare bones MOC file, but as soon as I add "Mechanical Unit" I get the servots.c and IPOL type errors.
Maybe this means I can't use the 7th node on the SMB in the robot base?
I have another SMB, a dsqc 313, but I don't know how exactly to connect it to SMB1. Should I just splice into the cables in the robot base, flipping SDI and SDO around?
Appreciate the help
None during install, just when I'm editing the moc.cfg file.. if I remove that line everything's fine.
I also removed the axc_filter block, but no change. I'll keep playing with it in the meantime.
I'm close! Stuck on this line:
MECHANICAL_UNIT:
-name "TURNTABLE" -use_run_enable "" -use_activation_relay "" -use_brake_relay ""\
-use_single_0 "TURNTABLE" -stand_by_state
#
If I have this in the MOC file, I get a pile of errors like this:
Internal log messages
1. Error: rhaltts.c 314 os_sem_wait/safevt_rhalt failed 0208 22:57.15
rhaltts.c 314 os_sem_wait/safevt_rhalt failed
2. Error: puscfg.c 1323 Can't connect to the servo 0208 22:57.15
puscfg.c 1323 Can't connect to the servo
3. Error: puscfg.c 1344 Can't connect to the ipol 0208 22:57.15
puscfg.c 1344 Can't connect to the ipol
etc
Here's my MOC file and Log from the latest revision. Maybe my servo is still wired incorrrectly. Any ideas?
Which robot type are you booting as ?
That did it!
Robot is moving correctly now. I'll start updating the MOC file tomorrow and update this thread.
Thanks loads, Saab.
Giving it a whirl with the Type B, DC2T system. It doesn't have advanced motion, which was the reason I used my other system (not Type B)
Which robot type are you booting as ?
I originally had the robot running with the "6 axis system" attached, trying to install "7 axis system".
I just noticed that Type B is present in the 6 axis, not in the 7 axis. Is that what you're referring to?
Thanks again for all the diagrams
Thanks for all the input so far Saab. I've been playing with it this morning, right now I'm back to a pile of joint collision errors because of the different rectifier.
The controller works fine with the DC4 rectifier, but when I switch the the DC2T (and install corresponding system from robinstall) I can't move axes 3-6. This is without the 7th axis plugged in anywhere. I had the exact same issue with the DC2 + GT setup, the first time I try to rotate axis 6, but 4 & 5 will jump at the same time.
This is why I thought the X2 plugin must be different, in a previous post.
I should probably get the axes moving with the new resolver before I try to hook up the 7th. Any help with this? error log attached. I had to fiddle with the axis 1 cable to seat it, so log #50 is where I turn it on and start moving it (or attempting).
69. 50052 Error: Joint speed too high 0205 20:36.59
The speed of joint irb_5 is too high
relative the ordered speed.
81. 50056 Error: Joint collision 0205 20:37.6
Actual torque on joint irb_6 is
higher than ordered while at low
or zero speed. Might be caused by
jam error (the arm has got stuck)
or hardware error.
In the base of the robot I have a dsqc 562 SMB. According to the attached pdf (page 107), I can measure up to 7 axes.
Do I even need to daisy chain my two SMB's then? or just plug straight into this SMB?
Thanks Saab,
Confusing why they specify it's the X2 port, but I won't worry about it.
I think all I need to figure out then is the smb hookup, I'll write out my thought process here.
By this attached drawing ("SMB") I should have the two serial measurement boards, connected in series.
The external axis manual says: the output from SMB 1 is the input to SMB 2.
So the measurement cable comes from the controller to the robot SMB1, at port R2.SMB. The SDO and SDO-N from SMB1 (robot base), are flipped into SDI and SDI-N respectively on the external axis SMB2, both using port R2.SMB (on SMB Diagram photo).
I'm a little bit simple when it comes to following wiring diagrams.
Just windering if any one been able to add the 7th axis
I’ve spoken to ABB they told me it’s impossible it’s cheaper to buy a second robot control the axis 1 or axis 6 with IO boards
Abb support really loves saying the only way to do anything is to buy, don't they? I doubt them when they claim things are impossible, we've solved a couple of things that they've said we can't fix, like computer boards - I think the term for that type of support is replacement artist, haha.
Maybe 'cheaper' would be accurate just because parts are so expensive, I've had a lot of luck buying from factorysurplusdirect on ebay lately.
See attached diagram from an old positioner interface.
That's the X4 (which I'll need next!), could you snip the X2 plug on that same page?