If the .exe is in that folder it's the 32 bit version.
.exe files in the (x86) folder are always 32-bit.
Posts by Sergei Troizky
-
-
Verify the UOP Auto Assignment setup in the System Configuration.
If it is set to "Simple", the fault reset signal is merged with the program abort.
FAULT RESET and CSTOPI signals are separate in the "Full" assignment mode.
Be aware though, that switching to "Full" remaps the UOP signals, which must be reflected in wiring and/or network UOP signals.
-
Also, ensure the program is not running as BG Logic.
-
Where do you "go to end_edit"? On Remote iPendant?
- Are you able to do anything else on remote iPendant?
iPendant may be locked in SETUP>>Host Comm>>HTTP Authentication.
- In SELECT>>Program DETAIL, ensure the program is not write-protected.
- Check the system variables in #UI_CONFIG.$READONLY. All three must be FALSE.
-
Please know first of all that I am new to this world of robots.
Second, I'm confused. You said that I shouldn't use joint move and you would use linear move. So, if using joint move and linear move does not guarantee me that the robot will follow the same path with and without pause-resume, what's the point of saying "I would use linear motion"?
Well, I will formulate little differently.
- Linear motion should be used when the path (in general) is a concern, e.g. moving near or around an obstacle. The reason is the path and rotations will be predictable.
- Exact path may be not be resumed after restart from within terminated CNT curve. If this is a problem, reduce the CNT value or split the motion into smaller segments.
These are two separate statements.
-
Could be done with a dedicated option called Error Code Output (or sth like that), or by accessing robot registers via SNPX, or by creating a small KAREL program to copy a fault code to a GO...
"...or by accessing robot registers via SNPX, ..."
Which registers?
-
No, I clearly said: for linear, everything I said before remains true.
-
Yes, joint moves should not be used when the exact path is a concern, sInce joint move path and rotations are unpredictable (though repeatable).
I would use linear move, for which everything I said before remains true.
-
I would say it depends on several factors.
If the stop happens within the CNT curve, the path after restart will differ, and the difference will increase with any of the following:
- With higher value of CNT.
- With sharper angle between the motion segments.
- With the stop earlier on the CNT curve.
The point is that after the restart, the motion to P2 will start directly from the actual position, without finalizing the interrupted CNT curve.
-
And this includes DeviceNet Card, so the purchase will be expensive.
-
How do you connect to the remote site?
Is it possible their firewall is open only for certain PCs (e.g. by Mac address)?
-
PR[i,j] syntax is ok for BG Logic, PR[i] is not.
The error must be somewhere else.
The error message typically indicates the erroneous line number.
Is there a motion group assigned to the BG program? -
The current line is in the system variable $SHELL_WRK.$CURR_LINE
This may be passed to GO in background logic.
The selected program name is in $SHELL_WRK.$ROUT_NAME
I doubt the latter can be processed in TP syntax.
-
What does the explicit messaging have with the OP question?
His problem is not reading the data, but the impossibility to override these data in the robot. -
If your robot has background logic available, program it to adjust the speed override in real time.
-
This seemed to work, but I didn't want it ...
No comments.
-
What is the connecton between the robot and PLC?
If it is a network, what communication protocol?
-
To see all installed options, go to MENU>>STATUS>>CONFIG(F3).
Or open the robot Web-interface and proceed to robot status.
You cannot "modify" software options, only add (purchase) more.
-
Trying to speed up linear moves of M-410iB 140H with R-30iB Plus controller.
The moves definitely may be faster.
Increasing PARAM_GROUP[1].SPEEDLIM has no effect.
PARAM_GROUP[1].PROCESS_SPD and PARAM_GROUP[1].$PROC_SPDLIM are set to 2000.
On attempt to increase each, "Value out of range" is displayed.
Any ideas how to unlock them?
Or something else has to be changed in variables?
-
$UI_CONFIG.$ON_BRIGHT
It is at the end, line 70.
Set it to 10.
