Please e-mail a question or bug report to Support@PrecastEngineer.com or call 505-260-1460 to ask a question, make a suggestion, or request a change.
Please report any suspected (or obvious) bugs to the support address. Please include a description of the problem and attach a copy of the problem file (e.g. *.bem, *.lt3) that displays the bug.
Select a category: All Programs | Bcan | Beam | Compmem | Lateral3 | Shearwal | Studs | Licensing
NOTE: Many of the bugs reported here have been fixed in the latest releases of the programs. Please see the Release Notes (on each product's page) for current status of any bugs.
A: The current versions and their release dates are:
| Bcan V3.0.4 | November 2007 |
| Beam V3.2.1 | May 2011 |
| Compmem V3.1.1 | September 2008 |
| Lateral3 V4.2.1 | March 2009 |
| Shearwal V3.1.0 | February 2007 |
| Studs V4.2.1 | December 2008 |
A: Click the Print Preview icon instead; then click the Print icon on the Print Preview page. That will bring up a printer dialog that will allow you to print a selected range of pages.
Workaround: Steps as follows:
Once the components are registered, you will need to run the program as an administrator to complete the installation. Open C:\Program Files\STI\<program> (that will be C:\Program Files (x86)\STI\<program> if you have a 64-bit system) and right-click on <program>.exe. Select "Run as administrator". After that first run, you should be able to run <program> as a standard user without any problems.
Workaround: All of our programs released before 2010 (all but Beam V3.2) save the history list and program state in files kept in the installation folder. It's writing to these files that causes the error under a restricted account. The only solution is to give the user write permission to <program>.hst and <program>.ini in the installation folder.
Workaround: None.
Workaround: None. You must use <drive>:\<folder>\<file> style paths.
Workaround: None. Just remember to be brief when entering descriptions.
Workaround: Use only two decimal places for distance values for distributed loads, concentrated loads, and joint locations.
Workaround: Close Bcan and restart it; open the file you were just working with. Everything will be back to normal. Often just reloading the current problem from the list of recent files on the File menu will fix the display.
Workaround: None. You'll just have to close and reopen the file.
Workaround: None. You'll just have to select the input page you want to work with.
Workaround: None. It's best to get in the habit of saving the problem file before running the calculations. That makes recovering easier.
Fixed in Build 5, i.e. V3.0.4.5, which was released 5/23/07. If you downloaded Bcan before this time, please download a fresh copy and install it. To find the build number, right-click the Bcan.exe file, select Properties, and then the Version tab.
Workaround: None really. You'll have to do
some work to find out what component is the other half of the
conflict and eliminate that from your system.
An article on the SevenForums web site offers some guidelines
for troubleshooting this kind of conflict. See http://www.sevenforums.com/tutorials/179159-troubleshoot-application-conflicts-performing-clean-startup.html
Another possibility is a corrupted system file. If you are
using Windows 7 or Vista, you can use Microsoft's System File
Checker to check for corrupted files. See http://support.microsoft.com/kb/929833
If you can identify a conflict, please report it to STI.
Workaround: A fresh restart of Beam doesn't have the problem. If Avcw is zero for all locations and Avci < 0.040 in2/ft but the note isn't showing, save your problem, then select it from the recent files list on the File menu and reload your problem. The note will appear in the report if the Avci and Avcw values are right.
Workaround: This seems to be a problem with re-initialization of some value in the shear calculations between calls to the calculation/report generation routines. Usually if you save the problem to a file and then reload the problem from the recent files list in the File menu, the problem will be temporarily fixed.
Workaround: None. As a temporary solution, you can send the problem file (*.bem) to Support@PrecastEngineer.com and we will return the file in V3.2 format.
Workaround: None. Using the shorter value for the strand length results in slightly lower strand development for a specific location along the development length but once the strand is fully developed, the calculated capacity is the same.
Update to V3.2.1 to fix this problem.
Workaround: None. Another example of why it's good to look at the full report before turning off sections for the final printout. Please update to V3.2.1.
Workaround: None. Always when using Intelliprint, check the full report for any problems while you are developing the solution and only use Intelliprint for the final printout of the report. Please update to V3.2.1.
Workaround: None really. You can make two runs. Add the stripping load to the member self weight and use only the Initial Stress values from that run. Then remove that load and use all the other results. Please update to V3.2.1.
Workaround: None. If your problem has the conditions described above, be aware of the possible problem with Vcw.
Workaround: None. A vertical component of prestress force almost always increases the Vcw value, so neglecting it usually is conservative (though you may use more shear reinforcing than required). For the random value that occasionally appears, if a value just doesn't fit with its neighbors, use a linear interpolation to get a reasonable value. Please update to V3.2.1.
Workaround: None. It will use either of the two possible values when it should always use the smaller. This results in some unconservative strength estimates. Please update to V3.2.1.
Workaround: None. Please update to V3.2.1.
Workaround: The problem occurs when 1/20th of the span equals 1/2 of the member height; so changing either of these slightly (±0.01) will get the values reported with only a small change in the results.
Workaround: The window location saved in
the Beam.ini file has been corrupted. Right-click on the Beam tab in the task bar and select
Maximize from the pop-up menu. This should bring Beam back into your window. Now exit
Beam to save new location data in
the Beam.ini file. When you restart Beam,
you can restore the window to whatever size and location you
like.
If that didn't work, exit Beam, delete the Beam.ini file, and
restart Beam. The program will
recreate the Beam.ini file with default values and you will
see the window again.
On Windows 7, the Beam.ini file is usually found in
"C:\Users\<acct>\AppData\<type>\STI"
On Windows XP, it is usually found in
"C:\Documents and Settings\<acct>\Application Data\STI"
where <acct> is the account you are logged into Windows with (i.e. your user name) and <type> is Roaming for a network account.
If you don't find Beam.ini at the path given above, open a command window and type
echo %APPDATA%
This will give the path to the AppData folder for your account. Beam.ini will be in the STI subfolder below the AppData path.
Workaround: None. Please update your version to V3.2.1 to fix the problem.
Workaround: None. For 5 ksi concrete, the limit for compressive stress is 0.85 * φ * f'c = 2.76 ksi and 85% of that is 2.35 ksi. The code prohibits factored bearing stress that exceeds the first value and you should avoid stresses above the second value. The program allows factored bearing stress up to 2.53 ksi before it prints a note advising a special study. Please update to V3.2.1.
Workaround: None. You can adjust NCDL to compensate but that won't help Initial Stresses. Please update to V3.2.1.
Work-around: None. The old equation is very similar to the minimum value for the new code (which, in practice, is often the required value).
Work-around: None. If you want the loads included in the factored loads, be sure to select a load case that includes them. If you don't want the loads included in the working loads, remove them from the Distributed and Concentrated Loads pages.
That number is Stc(tpg) = Ic / ytpg / (Etpg / Epc). You were probably expecting just Ic / ytpg.
Workaround: V3.2.0 prevents you from running a problem with a full-width opening. If your section allows, you should use the variable flange thickness with the thickness set to 0.01 in. where the full-width opening occurs.
Workaround: Split the load into two loads at the zero crossing.
Workaround: None. It's best to run the report once with all sections enabled before you commit to a design to be sure this problem doesn't apply to your choice of report options.
Workaround: None. You must clearly understand the basic assumptions of the program. The program provides assistance with code compliance but you must be the final authority of "Does this design make sense?"
Workaround: If you have a negative moment case that needs to be checked, you must run it separately from the positive moment case. That is, you must remove the positive moment case from the selected load cases on the Serviceability page.
Workaround: Use a very small value instead of zero, e.g. 0.001.
Work-around: Enter loads, distribution length, etc. on the Ledge Design page that are appropriate for your problem. When the program calculates hanger steel based solely on concentrated loads (from the Concentrated Loads page), it reports the total area of hanger steel required for the highest load without any attempt to distribute the steel over the distance between loads.
Workaround: None. You'll have to choose one option or the other in the current version of Beam.
Work-around: None. Check the moment capacity with a longer piece first. If the moment capacity at any location goes up when the shorter piece is used, use the lower calculated capacity.
Work-around: Nothing really effective. You can change the "Factor Applied to Develop. Length" on the "Strand Info" page. But one number is not correct for all cases. See Eqn. 12-2 in ACI 318-02.
A: The bug in version 3.0.4 and earlier (also sold as version 3.04 by J&A) occurs when compression steel is used to increase the moment capacity of an otherwise over-reinforced member. It over estimates the strength gained from compression steel and is NOT CONSERVATIVE! It's best to avoid over-reinforced designs if you continue to use those versions of the software.
Workaround: None. If you suspect this condition applies to your column design, you will have to make the adjustment manually.
Work-around: None. Please download and install the update V3.1.1.
Work-around: You must check Pu against the "Max design axial load strength" reported below the table.
Work-around: None. Don't enter negative values for Pu. We will change the next version to calculate the correct moment and limit for negative Pu.
Work-around: None. This will be fixed in the next update. The problem is the calculations are expecting Allowable Tension to be a negative number but the UI won't allow negative numbers to be entered.
Workaround: None. You shouldn't use Lateral3 V4.2.1 for this case.
Workaround: You can do this by checking the Torsional Irregularities box on the Building Parameters page and the program will generate a multiplier for the eccentricity if the structure is irregular. If the structure is not irregular and this box is checked, the multiplier will be 1.0.
Work-around: The problem is with the Period Calculation selection on the Seismic Parameters I page. If you leave the default selection for the approximate period, Eq. 12.8-7, the file doesn't get initialized correctly before it is saved. To work around this, select the Alternate period (Eq. 12.8-9) then switch the selection back to the Approximate period (Eq. 12.8-7). That gets the file set correctly so that it won't crash next time you open it.
A: No. Version 4.2.0 was released before Supplement No. 2 was published. You'll have to check the lower bound manually and, if the Cs being used by Lateral3 is less than the minimum from Supplement No.2, proportion results by (Cs,min/Cs,calc) where Cs,min is the value specified by Supplement No. 2 and Cs,calc is the value specified by ASCE 7-05, that is, the value calculated by Lateral3.
A: Yes. The forces won't be calculated correctly if it is anywhere else.
Work-around: None. Please be patient while we get these old, lower priority bugs worked out.
A: Well, there could be several causes for this. But a common problem is that Spectral Response parameters Ss and S1 must be entered as a percent of g (%g) not as decimal values. So, for example, to use 50% of g, enter 50.0 not 0.50.
Workaround: None. Check the requirements in ACI 318 Sect. 14.3.2 for minimal reinforcement cases and Sect. 11.10 for other cases to be sure your design complies.
A: The presentation of the factored loads
equation in this section is misleading. The equation, as it is
presented, is not used directly. The Mu
value shown there is only the moment resulting from the
horizontal wind or seismic load, the same number you entered
on the Lateral & Vertical Loads page with the appropriate
load factor applied.
The effect of any non-symmetric vertical dead and live loads
is included in the φMn value that is
calculated for each load case. So, the φMn
value represents the capacity available
in the wall with the given
vertical loads to resist the specific horizontal wind
or seismic load. If you compare the φMn
for positive moment (in the OUTPUT section of the report) to φMn
for negative moment (in the MOMENT REVERSAL section of the
report) you will see the effect of non-symmetric dead and live
vertical loads on the capacity of the wall to resist the
specified wind or seismic horizontal load.
Workaround: None. We'll improve the Help in future releases.
Workaround: None. Save the problem with the fix in place, quit Shearwal, restart Shearwal and reload the problem to eliminate the message.
Workaround: Select a different bldg. code on the User Info page then re-select the IBC 2006 code. That will reset the load factor to the correct value, 1.6.
Work-around: You will have to manage intersecting loads manually by removing them from the compression region, running an analysis for one direction, then adding or removing intersecting loads for the other direction and running another analysis.
Work-around: None. Please check the load factors for any problem files that you open.
Work-around: None. Please check the φ factors for any problem files that you open.
Workaround: None. Save the problem with the corrections, quit Shearwal, then restart Shearwal and reload the problem.
Workaround: After you've killed the Studs session, use an editor such as
Notepad to delete the garbage rows that were added to the
library file.
Adding anchors to the library by editing the library file
directly is not a recommended practice because the values are
not labeled in the file making it easy to get them in the
wrong order. That's why the edit dialog is provided. But if
you can't get the editor to work, add the values using Notepad
(or similar) then use the built-in Suds library editor to
check and correct if necessary the values you entered with
Notepad.
Workaround: You should use the [Reset Defaults] button to get the correct values to display in the boxes. If the button is inactive, changing any of the φ values will activate it.
A: Yes, that should be k-in. Work-around: None. You'll have to make the correction on the report yourself. This will be fixed in the next release.
Workaround: None. You can send the file to STI. We will convert it to V4.2.x format and send it back.
Workaround: None. The value reported for Vco3 is correct even when the value reported for Cc3 is wrong.
Workaround: None. This only happens if the anchor used in the problem file is not in the library. So it's only a potential problem if you share problem files with others who use a different PIA library.
Work-around: None but the update is free. Click here to get the instructions for downloading a copy. If you are a licensed user, you will have to re-install your license file after installing the update.
Work-around: When you first select "Cracking at Service Load Level", the button for "No Edge Reinforcement" is selected but that selection doesn't get reflected in the output. You must change the selection, that is, select one of the other buttons (#4 Min....) and select "No Edge Reinforcement" again before the program will recognize the selection and change the output.
A: The license says you can use a program on one CPU only. The hardware key forces you to use it on one CPU at a time. Other than that, the security isn't sophisticated enough to know the difference. So you can load it on both and take the key home with you at night. We won't come to your house and check.
A: Sorry, we have no network license options at this time. Let us know you would be interested in a network license option and that will help move it to the top of the priority list.
A: If you paid a deposit on the key, you can get a refund. However, we will not pay a refund for keys lost in the mail during return. You must package the key so it will pass through the USPS mail handling equipment without getting separated from the package. We will not pay a refund for a torn, empty envelope.
E-mail
a question to Support@PrecastEngineer.com
or call 505-260-1460 to ask a question.