Posts by beanluke

Seemed to just be a Roboguide bug. Joint moves worked on a real robot.

Note: Joint moves are only allowed with "Rail" tracking.

I guess I thought safe zone is the DCS zone, but that must be the "unsafe zone"

Depends whether you have the DCS CPC zone set-up as safe inside or safe outside.

safe inside = safe when robot is completely within the zone

Safe outside = safe when robot is completely outside of the zone

When you set the stopping distance value to be greater than the actual stopping distance, the robot will stop in the safe zone."

Heres how I interpret this:

The robot is moving at 1000mm/s and the robots actual stopping distance is 75mm at 1000mm/s. If the stopping distance value entered is 100mm then the the robot will begin to stop ~100 before it hits the dcs boundary. Since its actual stopping distance is 75mm it will end up coming to a complete stop 25mm before it actually hits the DCS boundary.

Not sure this will work as changing your Z height requires you to reset your reference position in the vision process

Try this:

Line[1] ON

WAIT DI[x] (the DI tied to your part detect switch)

LINECOUNT[1] R[3]

SETTRIG LINESCHED [1] R[3]

I'm a little late but this is probably the issue. You need to change some variables to get the 16bit card to work correctly.

There are two ways to set up the rail. As "external axis" or "integrated rail". Depending on the setup the DCS will stay relative to the rail or Robot. I can't remember for sure but I think DCS zones stay relative to the rail with the "integrated rail" option. This is configured in Controlled start<Menu<Maintenance<extended axis control

Do you need the GPM tool? When ever I have used circle finder it is by itself, not as a child to the GPM. If you need the GPM maybe just temporarily move Circle finder up a level so it isn't a "child", do the trouble shooting, make adjustments, then make it the "child" again.

I think I had this same thing happen to me a few weeks ago. There was another error in the history that came with it, I forget the code. In the remedy for it there was mention of this error coming up if line tracking encoder is enabled with no encoder/board plugged in.

Yes I do

Hello, I am creating a line tracking cell in roboguide. The robot is on a rail controlled with extended axis. I have the tracking schedule set up as rail tracking. I can get everything to work using linear moves but it is not allowing me to use joint moves.(TRAK-001)

According to the manual you should be able to use joint moves when rail tracking. What am I missing? Anyone have any experience with this?

Thanks

Unfortunately the warning can not be disabled when using line tracking.

Panasonic.

They pretty much just make welding robots so they are optimized for just that, everything is done with welding in mind. (like buying a multipurpose manual welder vs a dedicated tig welder... if all your doing is TIG then the dedicated machine will be the better choice) They use their own power source and waveforms which I found to be good. I don't know for sure but i think they are fairly reasonable price wise too.

They also make their own positioners that interface nicely with the robot.

I have used ABB, Fanuc and Motoman. If it came down to specifically welding I'd take a Panasonic over the others.

Has anyone had to set a payload for a robot as below? the eoat is attached to a kind of "lift assist" arm. I not sure what the best way to do the payload in this situation is. When its stationary it would see the weight of the eaot as 0 but when it starts to move the weight will have an effect. any ideas?

Hello

I'm having a problem with a couple spot welding robots my company is integrating.

When we run the cell in "WELD MODE" everything is fine, PLC gets weld completes from the Bosch timer so I know the BG logic I'm using for the weld completes is correct.

When we try to dry cycle the robot in "NO WELD MODE" some of the robots get "SPOT-008 Weld Complete Timeout Fault".

We noticed if we enable "sim weld IO" under the "TEST CYCLE>SPOT WELD" the robot will continue but this creates another problem. When we enable "sim weld IO" the PLC no longer sees the weld complete signals and puts a hold on the robot because it thinks its missing welds.

We have quite a few other robots in the same cell that don't have this problem. They can run in "NO WELD MODE" with "Sim weld IO" disabled and the PLC gets the weld completes. I have compared everything everything I can think of between the two robots (weld interface, io interconnects, cell interface, spot config, spot equipment, BG logic,) and nothing seems to be different.

Any one ever experienced this or have any ideas on something i might be missing? Any help is appreciated

Thanks

Lucas

V9 Rev,H

Hello

Does anyone know how to export large roboguide cells into a format that can be used in solidworks? I noticed under file>export there is a option to export the cell to iges however whenever I try this the loading bar pops up then a few minutes later roboguide will crash and close the cell.

Anybody know any tricks to do this?

I'm trying to do this so our designers can easily make a layout. Right now we use the "Export Object Position to CSV" option. This works but is tedious and leaves room for error.

Thanks

Are you changing user/tool frames for every program? This may be where the pause is coming from.

https://www.robot-forum.com/robotforum/fan…ooluser-frames/

Have you set the mount angle variable to 45?

$PARAM_GROUP[1].$MOUNT_ANGLE

I have this same problem.