Benderlink for Chiyoda FAQ
|
Where can I find brochures? |
You can download datasheets from our Knowledge Base page for Benderlink for Chiyoda: http://advancedtubular.com/wiki/index.php?title=Benderlink_for_Chiyoda |
What is learned with On-Site Training? |
We train on how to use the Benderlink software and how to perform corrections loops. We will lead your team through the software, then finish the training with actual corrections loops. |
</tr>
Can Benderlink be installed on a ROMER measuring-center computer? |
Yes - provided it is the correct version of Windows | </tr>
Is there a potential bottle-neck for user use if it is installed this way? |
While performing corrections loops, the ROMER software will require the attention of Benderlink. However, if transferring stored data to/from a Chiyoda, then the operations are performed at Benderlink. If a part is measured offline at the ROMER (not communicating) while someone is attempting to send data to the Chiyoda, then they would have to share the same computer screen at the same time - and this would become a bottle-neck. If this is a problem, then we recommend that you set aside a separate computer next to the Romer exclusively for Benderlink. These two computers must be networked together for Benderlink to respond to commands from the measuring center. If you find that one method of installation does not meet your needs, then we recommend that you modify the setup (switching from one computers to two computers) after you've used it a bit. |
</tr>
- Can we download and upload BLOCKS of data?
For the newer touch-screen version of the Chiyoda benders, you can upload and download entire blocks of data (20 channels. Or you can download a single channel at a time. The older style bender allows for a single channel save/load. Please note that a block of data requires about 5 minutes to RECALL from the bender to Benderlink. (15 seconds per part x 20 channels)
- How do we manage the Benderlink database?
The initial setup of the benders can be performed by sending ROMER data to the bender. However, the actual storage of the bender setup is best stored in the Benderlink file. Here is why:
- - Benderlink data files contain all the setup data for a bender. The ROMER data file does not.
- - Benderlink data files are used to remember the complete setup of a bender (unlike the ROMER data) in a file on the disk (or anywhere on the network).
- - Benderlink data files can be setup and established at an Engineers desk (before ROMER or the factory floor) if your engineers are given a license of Benderlink OFFLINE ($750 per seat).
- - Benderlink can also receive conversion data that is converted from our SolidWorks, Solid Edge, or AutoCAD converters. These kinds of converters are normally placed at engineer's workstations to work with Benderlink Offline.
If you want to keep part data that is already established in the Chiyoda control, the initial update will require that each part in the Chiyoda benders eventually be uploaded to a Benderlink file through communications. This takes about 15 seconds part part to perform the actual communication.
- How is data stored in the bender cell?
Generally the process involves a parallel set of data files. A ROMER master file is established (at the ROMER) to control the shape of the part. A BENDERLINK data file is established to remember the bender setup. When the file is run again in the future, the operator will load the MASTER file into DOCS, and load the BENDERLINK file into the Chiyoda control. Then the bender is ready to bend (providing the tools have been installed on the bender).
- What if my application is unique?
We've been installing this software since 1993. We have performed hundreds of installations of this software and have seen scores of unique ways to implement the system. If we install the software on-site (optional service), then we can personally observe your methods and help you determine the best way to use the system. A lot of these answers come during training. It is very normal for a customer to receive training, then completely rework how the software is used.
