never heard of it. do you have an example?
Posts by robotruler
-
-
the job must be created as a robot macro. Can not convert an existing job.
-
So what you are saying is that when in a R1 only job the COMARCON instruction is not available?
When you are collecting data do it on the positioner. This allows the system to measure data using the full grounding system.
As Roboprof stated. Put system in measure mode. Setup the weld with a weave. There should be no defects in the sample ie. undercut, roll over lack of fusion ext.
Make sure the weave is weaving in the correct direction (not stitching) Recommended single mode, HZ 3.0, Amp 2.5 for setting up. replace weave instruction with COMARCON. Set 197 =1. Run the weld with one plate missing. Set PC data in the appreciate SE parameter (Use the collected data).
Set 197=0 and run the same weld again. Register the Comarc condition. Change the L/R data to 0. Take the system out of measure mode and test. You can then adjust the L/R data by .5 amps at a time if the weld is not in the seam. If it completely tracks out start over.
-
If you don't mind the travel come to Ohio. The DX200 Maintenance class is very popular and fills up fast.
-
Hold Top Menu while turning power on
press Area
press Select
cursor down twice
press select
enter the password for management mode(99999999)
press enter
press top menu
cursor right twice
press select
press select
cursor down once
press select
cursor left
press select
when you can move the cursor up and down in the menu the file has loaded
Cycle power
-
This is not a bug in the system. When you are using coordinated weld paths you need to teach SREFP at every 90 deg. As you roll the torch the ref point 2 changes so the weave angle also changes.
-
Weirdest bug I've found is that if we're doing a coordinated weld path, when it rotates more than a relative 180° the wave will just, roll like 90° and weave up instead of out. Baffling stuff. -
Looks like there is a plug missing.
-
Without actually seeing the issue I really don't have any suggestions other than check the robot to station calibration.
-
Try setting the variable to Master Tool, then use the SSFTON Pxxx RB1. Use search job SR1-TOUCH.
MOVL robot is the master
SMOVL robot is the slave
-
When you are testing what frame is your variable set for?
BF is the frame of the base track.
RF is the frame of the robot.
MTF is the frame of the external axis.
Job BR1-TOUCH & R1-TOUCH for example sets the variable to base frame
Job SR1-TOUCH sets the data to MTF.
Does it shift correctly when the search job runs?
-
The SSFTON is the correct instruction.
-
How are you writing the data to the Pxxx Variable. What search program are you using.
-
As long as the controller is for a SV3 you should be OK with the serial # not matching.
The controller will need initialized. That requires a high level password. You will need to contact Motoman to have a technician come out and rebuild the controller CMOS. If you have a CMOS.BIN file tech support can sent you instructions on how to load it. All the menus will be in Japanese when you power it up.
-
It really depends on the Alarm that is generated. With a controller that old i would guess you have a failing Servopak or MSV01 board. It could also be a main harness in the robot.
-
You will need to use the SSHFTON instruction when you are using SMOVL or SMOVC moves. That is Master Tool Frame Shift. Z in MTF = Y in RF. X & Y in MTF become floating elements.
-
Sounds like you need to start from scratch with the setup. 0 for L/R and true current for U/D are not the correct settings.
Collect PC data and set the parameter defined.
Collect sensing data and register it to the COMARCON instruction.
ensure the travel speed is correct for the Hz and AMP in the weave.
Use the same grounding configuration for the setup and testing.
-
From what you have stated it sounds like it is shifting in Master Tool Frame. If your jobs are taught with the station master then your data for the shifts will be what you stated.
-
I have seen this same set of alarms on systems that were connected to the plant via Ethernet. Without some kind of switch at the controller to block other traffic on the Ethernet. The controller is getting overloaded with data better known as a data storm.
-
The DX100 does not have an option to expand the job memory. If you are having issues with memory try turning off the Trash Job List.
SETUP>Teaching conditions>trash job list invalid