If you want those UI always to be TRUE or FALSE then use Rack 35 on I/O UOP In config.
Set SLOT 0 for FALSE, SLOT 1 for TRUE.
That may be dangerous tho. Make sure it is safe to do that.
It is just a quick fix.
If you want those UI always to be TRUE or FALSE then use Rack 35 on I/O UOP In config.
Set SLOT 0 for FALSE, SLOT 1 for TRUE.
That may be dangerous tho. Make sure it is safe to do that.
It is just a quick fix.
Yes, you can use NX to program ABB robots to do any kind of machining. You have to have corresponing licenses!
When you setup а common CAM operation in NX for a common CNC machine, you don't have to specify machine type. But in robot case you have to create your robot's kinematic model and setup some additional robot rules. In short, that is a difference between CNC machine and a robot in NX.
NX generates a tool path listing (preliminary) in it's internal language.
NX post-processor geneates output file for your machine or robot from generated internal tool path listing.
NX have a basic ABB robot (RAPID) post-processor.
Try SprutCAM Robot with Additive manufacturing. I heard they can provide a trial period license. Robot library in SprutCAM is poor but you can create your own scheme or you can paste some KUKA robot from library and ignore the fact that it is not your robot model if you are sure that there will be no collisions.
Is it suitable option for you to store up predefined strings at Robot? If so you can just read some number from a group input and then recall a corresponding string via TPWrite.
Or may be you want to develope a complete chat for Robot?
I had the same problem recently and eventually uploaded system via floppy drive. It is risky tho. Floppies are unreliable.