Location:
Search - bit-set-r
Search list
Description: LightweightCTI是一套旨在帮助开发人员迅速构建语音相关应用的一套开放源代码的基础框架，目前你下载和使用的是构建于Pwin2000＋ + Delphi/C++Builder环境下的框架，所有的基础性代码使用Pascal语言完成。LightweightCTI的最终目标不是成为一套可在多种语音卡基础上使用的IVR软件（尽管目前其仅仅支持东进模拟卡的大部分功能），而是希望其成为语音应用开发的基础性框架，为此它当然需要有跨开发语言、跨语音板卡的能力。当然在写本文是我还只是做了一点点的基础性工作而矣，也希望通过它来促成LightweightCTI本身的发展，使其真正成为大家在开发语音应用时可用、能用的框架。通过本次重构其本身的架构已经基本定了下来，而且本人也居于它开发完成了公司的语音催缴与查询系统，所以其完全可应用于一般的应用开发中。同时，为了便于大家对LightweightCTI进行扩展，在接下来的时间我会为其写一套可插拨的插件容器，只要符合其接口规定的组件都可以成为LightweightCTI的一部分。-LightweightCTI is a set designed to help developers quickly build voice related applications Open source set the basic framework, Currently you download and use the building in Pwin2000 + Delphi / C Builder environment The framework, all the basic code using Pascal language completed. LightweightCTI the ultimate goal is not to become a voice in a variety of cards based on the use of IV R software (although its only support the East simulation into the most functional card), but his voice has become the basis for application development framework, for which it will need to cross-language development, - Voice Card capabilities. Of course, at this writing I have only done a little bit of infrastructure work and starts, It also hopes to push LightweightCTI own development. it really has become
Platform: |
Size: 628957 |
Author: LightweightCTI |
Hits:
Description: ************************************************************************ * * * * * THIS IS THE H Y P L A S 2.0 README FILE * * ----------------- * * * * HYPLAS is a finite element program for implicit small and large * * strain analisys of hyperelastic and elasto-plastic two-dimensional * * and axisymmetric solids * * * * HYPLAS v2.0 is the companion software to the textbook: * * EA de Souza Neto, D Peric & DRJ Owen. Computational Methods for * * Plasticity: Theory and Applications. Wiley, Chichester, 2008. * * (www.wiley.com/go/desouzaneto) * * * * Copyright (c) 1998-2008 EA de Souza Neto, D Peric, D.R.J. Owen * *----------------------------------------------------------------------* * File last updated: 18 October 2008 * * * * This file belongs in the directory ../HYPLAS_v2.0 * ************************************************************************ * * * I M P O R T A N T * * * * READ SECTIONS 0 TO 3 OF THIS FILE CAREFULLY BEFORE ATTEMPTING * * TO COMPILE AND RUN THE PROGRAM HYPLAS ON YOUR COMPUTER !! * * * * THE AUTHORS DO NOT GUARANTEE THAT ANY SUGGESTIONS/INSTRUCTIONS * * GIVEN IN THIS README FILE WILL WORK ON ANY PARTICULAR OPERATING * * SYSTEM. IF YOU DECIDE TO FOLLOW ANY SUGGESTIONS/INSTRUCTIONS * * GIVEN HERE YOU MUST DO SO AT YOUR OWN RISK. * * * * * * BUG REPORTS: Please send bug reports to * * * * hyplas_v2.0@live.co.uk * * * * Messages sent to the authors' personal email addresses * * will NOT be answered. * ************************************************************************ This file contains the following sections: 0. Copyright statement and disclaimer 0.(a) Copyright statement 0.(b) Disclaimer 0.(c) Conditions of use 1. Introduction 1.(a) Note on portability 2. Compiling and running HYPLAS 2.(a) Memory requirements 2.(b) Testing a newly compiled executable 3. The HYPLAS directory tree 4. Cross-referencing between the source code and the textbook 5. HYPLAS error messaging 6. Further remarks on HYPLAS ************************************************************************ 0. COPYRIGHT STATEMENT AND DISCLAIMER ================================== 0.(a) Copyright statement ------------------- You may only use this program for your own private purposes. You are not allowed, in any circumstances, to distribute this program (including its source code, executable and any other files related to it, either in their original version or any modifications introduced by you, the authors or any other party) in whole or in part, either freely or otherwise, in any medium, without the prior written consent of the copyright holders. 0.(b) Disclaimer ---------- This program (including its source code, executable and any other files related to it) is provided "as is" without warranty of any kind, either expressed or implied, including, but not limited to, any implied warranties of fitness for purpose. In particular, THIS PROGRAM IS BY NO MEANS GUARANTEED TO BE FREE FROM ERRORS. This program (or any modification incorporated to it by you, the authors or any other party) will run entirely at your risk. The results produced by this program are in no way guaranteed to be fit for any purpose. Under no circumstances will the authors/copyright holders be liable to anyone for damages, including any general, special, incidental or consequential damages arising from the use or inability to use the program (including, but not limited to, loss or corruption of data, failure of the program to operate in any particular way as well as damages arising from the use of any results produced by the program for any purpose). 0.(c) Conditions of use ----------------- You may only use this program if you fully understand and agree with the terms of the above disclaimer. You must not use this program if you do not agree with or do not understand (fully or in part) these conditions of use. 1. INTRODUCTION ============ HYPLAS is a finite element code for small and large strain analysis of hyperelastic and elasto-plastic solids. Most procedures implemented in HYPLAS are described in detail in its companion textbook: EA de Souza Neto, D Peric & DRJ Owen. Computational Methods for Plasticity: Theory and Applications. Wiley, Chichester, 2008 (www.wiley.com/go/desouzaneto). 1.(a) Note on Portability ------------------- HYPLAS has been written in standard ANSI FORTRAN 77. Currently, the only known (and deliberate) exceptions to the FORTRAN 77 ANSI standard are the instructions: INCLUDE '' used in many routines to include the HYPLAS database files (common blocks and global variables), and; CALL GETENV('HYPLASHOME',HYPLASHOME) used in subroutine "ERRPRT" (file ../HYPLAS_v2.0/src/GENERAL/errprt.f). This instruction inquires the name of the system environment variable HYPLASHOME and writes it on the character string HYPLASHOME. This instruction is NOT part of the ANSI FORTRAN 77 standard, but seems to work in most currently available FORTRAN 77 compilers. 2. COMPILING AND RUNNING H Y P L A S ================================== The HYPLAS source code is stored in directory ../HYPLAS_v2.0/src/ (../HYPLAS_v2.0/ being the current directory) and all its subdirectories. To generate an executable file, you just need to compile the FORTRAN source files: ../HYPLAS_v2.0/src/hyplas.f and ../HYPLAS_v2.0/src/*/*.f together. We recommend that the executable HYPLAS be stored in the directory ../HYPLAS_v2.0/bin to which the environment variable HYPLASHOME should be set (see below how to set a system environmental variable). WINDOWS (R) systems ------------------- On Microsoft Windows(R) systems, HYPLAS has been successfully compiled using Intel Visual Fortran Compiler(R) integrated with Microsoft Visual Studio(R). Here you only need to create a project that contains all Fortran source files mentioned above as well as the include files ..\HYPLAS_v2.0\src\*.INC On a Windows XP system, the system environment variable HYPLASHOME can be set as follows: 1. Open a File Manager 2. Right-click on the "My Computer" icon 3. Select "Properties" on the drop-down menu 4. A new window named "System Properties" will pop-up. Here select the "Advanced" tab. 5. On the "Advanced" tab, click the "Environment Variables" button. 6. A new window titled "Environment Variables" will pop-up. Here click the button "New" in the "System Variables" section of the window. 7. A new window will pop-up titled "New System Variable". Here you should fill the fields "Variable name" and "Variable Value", respectively, with HYPLASHOME and the path name (in full) of the directory ..\HYPLAS_v2.0\bin. 8. Press "OK" on the relevant pop-up windows. 9. The next time the computer is REBOOTED, this variable will be set to the correct path and HYPLAS should be able to find the error messages file ERROR.RUN if required. UNIX/LINUX systems ------------------ In a UNIX/LINUX operating system using a C-shell, for instance, the HYPLASHOME environment variable should be set with the command: setenv HYPLASHOME where here denotes the full path to the directory ../HYPLAS_v2.0/bin. To compile HYPLAS (from directory ../HYPLAS_v2.0/src) with a FORTRAN 77 compiler such as g77, you can use the command: g77 -o ../bin/hyplas hyplas.f */*.f Note that the executable file "hyplas" will be stored in the directory ../HYPLAS_2.0/bin (i.e. the directory set in the HYPLASHOME environment variable). Alternatively, you may use the Makefile provided (with suitable modifications, if needed) to create the HYPLAS executable. IMPORTANT: Before generating a HYPLAS executable, read Sections 2.(a) and 2.(b) below. 2.(a) Memory Requirements ------------------- HYPLAS memory requirements depend on the array dimensioning parameters set in files: ../HYPLAS_v2.0/src/ ELEMENTS.INC GLBDBASE.INC MATERIAL.INC MAXDIM.INC Files ELEMENTS.INC, GLBDBASE.INC and MATERIAL.INC contain parameters which are associated with the currently implemented finite elements and materials. DO NOT MODIFY THEM ! unless you are absolutely sure of what you are doing (only developers coding new elements or new material models/analysis types may need to modify them by changing the existing dimensioning parameters and/or including new parameters). The ONLY dimensioning file that can be safely modified by the average user is the file MAXDIM.INC This file contains the array dimensioning parameters related to the maximum permissible dimension of problems to be analysed by HYPLAS. These parameters include the maximum number of nodes, elements, element groups, etc. If necessary, CHANGE THESE PARAMETERS TO SUIT YOUR PROBLEM SIZE/MEMORY REQUIREMENTS before compiling HYPLAS. 2.(b) Testing a newly compiled executable ----------------------------------- After you have successfully compiled the HYPLAS source code and created an executable file, the next step is to run some tests to verify that HYPLAS is working well. To do this, proceed as follows: The directory ../HYPLAS_v2.0/book_examples/data_files contains a series of data files named .dat of benchmarked examples described in the companion textbook. The corresponding (benchmarked) result files are in the directory ../HYPLAS_v2.0/book_examples/result_files This directory contains a series of result files named .res generated with the current version of HYPLAS on a tested platform. All these files have been named such that their names start with the textbook section number where the corresponding example is described. For instance, files 14_9_2_tresca.dat and 14_9_2_tresca.res refer to a problem described in section 14.9.2 of the textbook, and so on. To check that HYPLAS is working well on your platform, after compiling HYPLAS, run the program HYPLAS for the examples of files .dat and compare the newly generated results .res with their benchmarked counterparts (of the same filename) in the result_files directory. To run an example, execute HYPLAS and use the keyboard to enter the name of the corresponding data file in full (including the extension .dat). To compare the benchmarked .res files against their newly generated you may proceed as follows: 1. On MICROSOFT WINDOWS systems - Here we have successfully used the software "ExamDiff" (the task was made particularly easy by selecting "View" and then the "Show Differences Only" option - this refers to version 1.8 of this software). 2. On UNIX/LINUX systems - Here we use the "diff" command from a shell window (and set the option to ignore blank spaces). A shell script may be used to perform this task automatically (including running HYPLAS and checking for result file differences) for all benchmarked examples provided. IMPORTANT: THE ONLY ACCEPTABLE DIFFERENCES BETWEEN A THE NEWLY GENERATED RESULT FILES AND THEIR BENCHMARKED COUNTERPARTS ARE THE DIMENSIONING PARAMETERS (FROM FILE MAXDIM.INC) USED TO COMPILE THE NEW EXECUTABLE (THESE PARAMETERS ARE PRINTED RIGHT AT THE BEGINNING OF THE RESULT FILES) AND NUMERICAL DIFFERENCES IN RESULTS DUE TO NUMERICAL "ROUNDING-OFF" (THESE ARE VERY SMALL DIFFERENCES THAT DEPEND ON THE PRECISION OF ARITHMETIC OPERATIONS IN THE PLATFORM USED). ALSO NOTE THAT THE EXAMPLES OF THE COMPANION TEXTBOOK DO NOT COVER ALL FEATURES OF HYPLAS. HENCE THIS TEST DOES NOT GUARANTEE THAT EVERYTHING IS WORKING PROPERLY. 3. THE H Y P L A S DIRECTORY TREE ================================ 3.(a) Summary ------- ../ HYPLAS_v2.0/ bin/ book_examples/ data_files/ result_files/ man/ html/ src/ CRYSTAL/ DAMAGE/ DAMAGED_ELASTIC/ DRUCKER_PRAGER/ ELASTIC/ ELEMENTS/ GENERAL/ MATERIALS/ MATHS/ MOHR_COULOMB/ OGDEN/ TRESCA/ VON_MISES/ VON_MISES_MIXED/ 3.(b) Description ----------- The HYPLAS program directory tree is organised as follows: ../HYPLAS_v2.0/ (this directory) This is the HYPLAS root directory, where the HYPLAS directory tree starts. ../HYPLAS_v2.0/bin/ This directory contains the file ERROR.RUN where most HYPLAS error/warning messages are. IMPORTANT: the environment variable HYPLASHOME should be set to this directory. Otherwise, HYPLAS will not find its error/warning messages when required. We also recommend that the EXECUTABLE of HYPLAS be stored in this directory. ../HYPLAS_v2.0/book_examples/ This directory has the following subdirectories: ../HYPLAS_v2.0/book_examples/data_files ../HYPLAS_v2.0/book_examples/result_files Refer to Section 2.(b) above for further details. ../HYPLAS_v2.0/man/ This is the HYPLAS documentation/manuals directory. It contains the following files: input_man.txt - A concise input data manual for HYPLAS in ASCII format; hyplas_calltree.txt - Contains a flowgraph (shows the call tree) of HYPLAS in ASCII-format. Note: calls to function subprograms are not included in this flowgraph; and the subdirectory: ../HYPLAS_v2.0/man/html This directory contains the hypertext (HTML) format Fortran source code and of manual pages of the entire HYPLAS program. Manual pages with descriptions of each function/subprogram including their argument list are linked to their corresponding HTML-format source code. This allows the user the navigate through the HYPLAS source code using a web browser. To start at the main program, use your web browser to open the file hyplas.html. This facility should be helpful to those trying to understand the flow of program HYPLAS. ../HYPLAS_v2.0/src/ This directory (and its subdirectories) contains the Fortran source code of HYPLAS. The files containing the sources are named following the standard practice: .f where is the name of the FORTRAN procedure (subroutine, function subprogram, etc.) whose source code is in file .f. The source code of the HYPLAS main program is in file hyplas.f and the HYPLAS database (COMMON blocks, array dimensioning parameters and other global parameters) is coded in the "include files" ELEMENTS.INC GLDBASE.INC MATERIAL.INC MAXDIM.INC in this directory. In addition, this directory contains a file named "Makefile" (UNIX-LINUX Release only) which may be used for compiling and linking HYPLAS in UNIX/LINUX systems. The subdirectories of ../HYPLAS_v2.0/src are as follows: ../HYPLAS_v2.0/src/CRYSTAL Contains the source code of all procedures related to the finite strain single crystal plasticity model implemented in HYPLAS. ../HYPLAS_v2.0/src/DAMAGE Source files of the procedures related to the Lemaitre ductile damage model implementation. ../HYPLAS_v2.0/src/DAMAGED_ELASTIC Source files of the procedures related to the damaged elasticity model with crack closure effect. ../HYPLAS_v2.0/src/DRUCKER_PRAGER Source files of the procedures related to the implemented Drucker-Prager plasticity model. ../HYPLAS_v2.0/src/ELASTIC Source files of the procedures related to the linear elasticity model (Hencky model under large strains) implemented. ../HYPLAS_v2.0/src/ELEMENTS Source files of the element interfaces and element-related procedures. ../HYPLAS_v2.0/src/GENERAL Source files of general procedures. ../HYPLAS_v2.0/src/MATERIALS Source files of the material interfaces. ../HYPLAS_v2.0/src/MATHS Source files of the mathematical procedures. ../HYPLAS_v2.0/src/MOHR_COULOMB Source files of the procedures related to the implemented Mohr-Coulomb plasticity model. ../HYPLAS_v2.0/src/OGDEN Source files of the procedures related to the implemented Ogden hyperelasticity model. ../HYPLAS_v2.0/src/TRESCA Source files of the procedures related to the implemented Tresca plasticity model. ../HYPLAS_v2.0/src/VON_MISES Source files of the procedures related to the implemented von Mises plasticity model with isotropic hardening. ../HYPLAS_v2.0/src/VON_MISES_MIXED Source files of the procedures related to the implemented von Mises plasticity model with mixed isotropic/kinematic hardening. 4. CROSS-REFERENCING BETWEEN THE SOURCE CODE AND THE TEXTBOOK ========================================================== Many references are made in the textbook to various subprograms of HYPLAS. These are usually made when a particular procedure described in the text is implemented in the program. The reader should refer to the textbook index. Also, a substantial number of comment lines have been added to the source code of HYPLAS with reference to sections, figures, boxes, etc of the textbook related to the part of the code in question. Such references are usually displayed after the word "REFERENCE:" (in capitals) on commented lines. Searching for this word will take you to the line of code where the particular routine has a reference to the textbook. NOTE: Occasional references to other textbooks/journal papers are also made following the word "REFERENCE:" on commented lines. 5. HYPLAS ERROR MESSAGING ====================== Most error/warning messages issued by HYPLAS are in the ASCII-format file ERROR.RUN (kept in the HYPLASHOME directory - ../HYPLAS_v2.0/bin). All such error/warning messages have an identification code (e.g. ED0015) which is printed both to the standard output (this is usually the computer screen) and to the relevant results file. If you wish to find where in the source code a particular message is being issued, then perform a search for the corresponding message identification code in the entire source code of HYPLAS. 6. FURTHER REMARKS ON HYPLAS ========================= 6.(a) Program efficiency THIS SECTION IS OF INTEREST ONLY TO THOSE WANTING TO MAKE HYPLAS RUN FASTER. It is particularly stressed in the textbook that this program has not been designed having efficiency in mind (refer to Section 5.1.2 of the textbook). Its structure has been designed mainly to illustrate in a relatively clear manner the computer implementation of the techniques and algorithms described in the text, with a particular view to the implementation of solid constitutive models and finite elements. For those who are especially interested in the speed of the code, there are a few tips that could help in this direction. Unfortunately, these involve modifications to the source code which is probably most appropriate to readers with a good level of experience in finite element programming. To those with this particular interest, we can suggest the following: (i) The use of faster linear solvers This is probably the change that would result in a greater gain in efficiency. The Frontal Method adopted in subroutine FRONT (file ../HYPLAS_v2.0/src/GENERAL/front.f) has been designed originally to save memory (back in the days when computer memory was severely limited). There are currently a vast number of methodologies which focus on speeding up the linear solution, in addition to reducing memory storage requirements (which is a particularly important issue in the solution of large scale problems). Some of these are extensions/refinements of the original Frontal solver. We remark that a number of such procedures (with their respective source codes) are available (conditions may apply) from the LAPACK (Linear Algebra PACKage - http://www.netlib.org/lapack) repository or from the HSL Library (http://www.cse.cse.scitech.ac.uk/nag/hsl). For the reader interested in gaining speed, we would recommend the replacement of the existing solver of FRONT by a faster one. We remark though that this is a substantial programming task. Another aspect here is the fact that computing times in FRONT are directly linked to the frontwidth of the system which, in the present version of HYPLAS is fixed and depends, for a given mesh, on how the degrees of freedom are numbered (node numbering). The incorporation of a frontwidth optimiser (which re-numbers the degrees of freedom in order to minimise the frontwidth) in FRONT could produce some good savings in computing times. Such savings become particularly noticeable in larger problems where the original node numbering produces an excessively large frontwidth. (ii) Material-specific computations The issues pointed out here affect only the computing times for specific material models and are expected to have a much lower impact in overall speed than the linear solver issue discussed above. Some of the material model-specific computations carried out in HYPLAS could be made a bit faster. For example, for isotropic models whose stress update is carried out in the principal stress space (such as the Tresca and Mohr-Coulomb models - see routines SUTR and SUMC, files ../HYPLAS_v2.0/src/TRESCA/sutr.f and ../HYPLAS_v2.0/MOHR_COULOMB/sumc.f, respectively) the spectral decomposition of the stress in carried out in the state update update routine and then repeated in the corresponding routine for computation of the consistent tangent operator (refer to files ../HYPLAS_v2.0/src/TRESCA/cttr.f and ../HYPLAS_v2.0/src/MOHR_COULOMB/ctmc.f, respectively, for the Tresca and Mohr-Coulomb plasticity models). Some savings in computing time can be achieved here by storing the stress eigenprojection tensors (these can be stored as state variables) during the execution of the state updating and then retrieving them later for use in the computation of the consistent tangent operator. This change can be incorporated to the code relatively easily. The computation of the exponential map and is derivative for the single crystal plasticity model (routines EXPMAP, file ../HYPLAS_v2.0/src/CRYSTAL/expmap.f and DEXPMP, file ../HYPLAS_v2.0/src/CRYSTAL/dexpmp.f) is carried out in three dimensions (these routines have been adapted from an earlier three-dimensional code). To improve efficiency, these can be adapted to work only in two-dimensional problems by removing the unnecessary operations related to the third dimension. 6.(b) Output of nodal averaged values The reader should be aware that the way in which nodal averaged values of stresses and other variables are calculated in HYPLAS is very basic (and rudimentary). This feature of the program is made available only to help those interested in producing contour plots, etc from results presented in HYPLAS result files and should be useful in many circumstances of interest. This facility has in fact been used in producing many of the figures presented in the textbook. But note, for example, that the values of incremental plastic multipliers for plasticity models may take (inadmissible) negative values when extrapolated from Gauss-point to nodes and averaged. We remark that more sophisticated and refined techniques of transferring Gauss point values of variables to nodal points and obtaining the corresponding smoothed field are available in the current literature. These fall outside the scope of the companion textbook of HYPLAS.
Platform: |
Size: 11008084 |
Author: gtcewli3 |
Hits:
Description: LightweightCTI是一套旨在帮助开发人员迅速构建语音相关应用的一套开放源代码的基础框架，目前你下载和使用的是构建于Pwin2000＋ + Delphi/C++Builder环境下的框架，所有的基础性代码使用Pascal语言完成。LightweightCTI的最终目标不是成为一套可在多种语音卡基础上使用的IVR软件（尽管目前其仅仅支持东进模拟卡的大部分功能），而是希望其成为语音应用开发的基础性框架，为此它当然需要有跨开发语言、跨语音板卡的能力。当然在写本文是我还只是做了一点点的基础性工作而矣，也希望通过它来促成LightweightCTI本身的发展，使其真正成为大家在开发语音应用时可用、能用的框架。通过本次重构其本身的架构已经基本定了下来，而且本人也居于它开发完成了公司的语音催缴与查询系统，所以其完全可应用于一般的应用开发中。同时，为了便于大家对LightweightCTI进行扩展，在接下来的时间我会为其写一套可插拨的插件容器，只要符合其接口规定的组件都可以成为LightweightCTI的一部分。-LightweightCTI is a set designed to help developers quickly build voice related applications Open source set the basic framework, Currently you download and use the building in Pwin2000+ Delphi/C Builder environment The framework, all the basic code using Pascal language completed. LightweightCTI the ultimate goal is not to become a voice in a variety of cards based on the use of IV R software (although its only support the East simulation into the most functional card), but his voice has become the basis for application development framework, for which it will need to cross-language development,- Voice Card capabilities. Of course, at this writing I have only done a little bit of infrastructure work and starts, It also hopes to push LightweightCTI own development. it really has become
Platform: |
Size: 628736 |
Author: LightweightCTI |
Hits:
Description: RS_latch using vhdl,
When using static gates as building blocks, the most fundamental latch is the simple SR latch, where S and R stand for set and reset. It can be constructed from a pair of cross-coupled NOR (Not OR) logic gates. The stored bit is present on the output marked Q.
Normally, in storage mode, the S and R inputs are both low, and feedback maintains the Q and Q outputs in a constant state, with Q the complement of Q. If S (Set) is pulsed high while R is held low, then the Q output is forced high, and stays high when S returns to low similarly, if R (Reset) is pulsed high while S is held low, then the Q output is forced low, and stays low when R returns to low.-RS_latch using vhdl,
When using static gates as building blocks, the most fundamental latch is the simple SR latch, where S and R stand for set and reset. It can be constructed from a pair of cross-coupled NOR (Not OR) logic gates. The stored bit is present on the output marked Q.
Normally, in storage mode, the S and R inputs are both low, and feedback maintains the Q and Q outputs in a constant state, with Q the complement of Q. If S (Set) is pulsed high while R is held low, then the Q output is forced high, and stays high when S returns to low similarly, if R (Reset) is pulsed high while S is held low, then the Q output is forced low, and stays low when R returns to low.
Platform: |
Size: 354304 |
Author: Seungyun |
Hits:
Description: hex code for controlling a TSA5511 phase locked loop chip using a PIC16F84
Also drives a standard 16x1 LCD display.
function 16F84(A) L.C.D. notes
0V 5 1, 5
+5 volt 4, 14 2, 3
Display enable 2 6
SCL 17 needs 10k pullup to +5V
SDA 18 needs 10k pullup to +5V
4MHz crystal 16
4 MHz crystal 15
display 10 4
display data 9 14
display data 6 11
display data 8 13
display data 7 12
switch input 11 ‘Down’ switch, normally 0V
switch input 12 ‘Set’ switch, normally 0V
switch input 13 ‘Up’ switch, normally 0V
TSA5511 needs a 3.2Mhz crystal
1 x 16 character display pinout:
1 = 0 Volt
2 = 5 Volt
3 = Supply Voltage LCD Driver
4 = RS, Register Select, Low=Instruction, High=Data
5 = R/W, Read/Write
6 = Enable
7 to 14 = DB0-DB7, Data Bus software selectable 4 or 8-bit mode
15 = LED + (Anode of LED Unit)
16 = LED - (Cathode of LED Unit)-hex code for controlling a TSA5511 phase locked loop chip using a PIC16F84
Also drives a standard 16x1 LCD display.
function 16F84(A) L.C.D. notes
0V 5 1, 5
+5 volt 4, 14 2, 3
Display enable 2 6
SCL 17 needs 10k pullup to+5V
SDA 18 needs 10k pullup to+5V
4MHz crystal 16
4 MHz crystal 15
display 10 4
display data 9 14
display data 6 11
display data 8 13
display data 7 12
switch input 11 ‘Down’ switch, normally 0V
switch input 12 ‘Set’ switch, normally 0V
switch input 13 ‘Up’ switch, normally 0V
TSA5511 needs a 3.2Mhz crystal
1 x 16 character display pinout:
1 = 0 Volt
2 = 5 Volt
3 = Supply Voltage LCD Driver
4 = RS, Register Select, Low=Instruction, High=Data
5 = R/W, Read/Write
6 = Enable
7 to 14 = DB0-DB7, Data Bus software selectable 4 or 8-bit mode
15 = LED+ (Anode of LED Unit)
16 = LED- (Cathode of LED Unit)
Platform: |
Size: 2048 |
Author: Nev |
Hits:
Description: 三菱FX系列PLC编程口通讯程序之置位复位(发布源码)-Mitsubishi FX Series PLC programming port communication procedures set bit reset (release source code)
Platform: |
Size: 26624 |
Author: hbgg |
Hits:
Description: 略简说下解密主要是靠加密后得前8个字节+密钥来运算
而前8个字节是根据随机数+启动时间运算而来
详细思路在大家看看代码应该能够看明白的
密钥任意设置 支持 中文、字母、数字、符号（可重复）
其实过程也并非复杂 看得懂的人应该感觉很简单的
运算主要利用 位异或（xor） 位取反（not）
相同内容 每次加密后的内容都不会相同 随机动态生成
加密后的内容需解密时需要保存完整字节
缺少任意位置字节都会导致解密错误（除非最尾的吧）
密钥（key）也要保持跟加密时一致
加密解密测试效果 CPU:（R）D 2.8
30000个字节（易语言升级历程.txt）
只是加密或解密中的一项的耗时
（加、解、耗时都很相邻）
密钥:abcdefg
长度:7
耗时: 0- 16 ms
密钥:abcdefghijklmnopqrhtuvwxyz1234567890~!@#$ ^&*()_+-=
长度:51
耗时: 78-125 ms
密钥越长 费时就多点 加解密key一个字符都不能错
也不会说密钥大概有部分对也能够解密部分信息
-Jane said, slightly under the encrypted decryption key is obtained through the first 8 bytes+ the key to computing
The first 8 bytes is based on random number+ start-up time from operation
For more ideas take a look at the code should be able to see to understand
Key set to support any Chinese, letters, numbers, symbols (repeatable)
In fact, the process is not complex and can read people should feel very simple
Operation mainly use bit different or (xor) bit to take anti-(not)
The same content each time the encrypted content is not dynamically generate the same random
Required to decrypt the encrypted contents of the byte when the need to preserve integrity
Bytes will result in a lack of anywhere to decrypt error (unless the end of it the most)
Key (key) must remain consistent with the encryption
Encryption and decryption test results CPU: (R) D 2.8
30,000 bytes (easy language upgrade process. Txt)
Only encrypted or decrypted in a time-consumin
Platform: |
Size: 16384 |
Author: 朱同德 |
Hits:
Description: 本模块的功能是验证实现和PC机进行基本的串口通信的功能。需要在PC机上安装一个串口调试工具来验证程序的功能。
程序实现了一个收发一帧10个bit（即无奇偶校验位）的串口控制器，10个bit是1位起始位，8个数据位，1个结束位。
串口的波特律由程序中定义的div_par参数决定，更改该参数可以实现相应的波特率。程序当前设定的div_par 的值
是0x104，对应的波特率是9600。用一个8倍波特率的时钟将发送或接受每一位bit的周期时间划分为8个时隙以使通
信同步.
程序的基本工作过程是，按动一个按键SW0，控制器向PC的串口发送“welcome"，
PC机接收后显示验证数据是否正确（串口调试工具设成按ASCII码接受方式）.
PC可随时向CPLD发送0-F的十六进制数据，CPLD接受后显示在7段数码管上.-The module s function is to verify the implementation and the basic PC, the serial communication function. Need PC,
Install a serial debugging tools to verify the functionality of the program.
Program implements a receive a 10 bit (ie no parity bit) of the serial controllers, 10
bit is a start bit, 8 data bits, 1 stop bit.
Serial Porter law defined by the program parameters div_par decision can change the parameters of the corresponding
Baud rate. Program the value of the current set div_par
Is 0x104, the corresponding baud rate is 9600. 8 times the baud rate with a clock will be sent or received per
A bit of the cycle time is divided into eight time slots in order to pass
Information synchronization.
The basic process is the work program, press a button SW0, the controller s serial port to the PC
"Welcome",
PC, after receiving the authentication data displayed is correct (serial debugging tool ASCII code set by the r
Platform: |
Size: 2048 |
Author: riversky |
Hits:
Description: 单周期16位CPU的设计,我们的计算机组成原理课设，可以实现R型、I型和J型指令，内有报告和指导书-Single-cycle 16-bit CPU design, our Principles of Computer Organization class set, you can achieve R-type, type I, and J-type instructions, reports and instructions
Platform: |
Size: 4185088 |
Author: 大空翼 |
Hits:
Description: This set of files describe how error detection and correction can be done using hamming code/parity-bit checker
Platform: |
Size: 76800 |
Author: Rishav Goel |
Hits:
Description: Set r is a 2^k binary number, and the following conditions are met:
(1) r at least 2^k of 2-bit binary number.
(2) as a 2^k binary number, except the last one, a r every strictly less than its adjacent one on the right.
(3) to convert r to 2 after the binary number q, the total does not exceed the number of digits w q.
-2^k binary number
Platform: |
Size: 1024 |
Author: liumang |
Hits:
Description: “ 人工蚂蚁” 生活在一个二维网格世界中， 它能沿已作标记的单元所组成的连续“信息素踪迹”(宽为一个单元)的运动。这个蚂蚁占一个单元，它可以面向东、南、西、北。它能做五个动作：前移一个单元(m)；在同一单元中向左转(l)；在同一单元中向右转(r)；设置状态位元“开”(on)；设置状态位元“关”(off)。蚂蚁感知它的正前方(即其面朝的方向)是否有信息素踪迹且其状态位元是否为“开”，若状态位元为“开”表示该单元已经走过（设状态位元起初为“关”）。-"Artificial ants world live in a two-dimensional grid, it can be marked along the unit has been composed of continuous" pheromone trail "(width of a cell) movement. The ants representing a unit, it can be facing east, south, west and north. It can do five actions: move forward one unit (m) switch (l) to the left in the same unit rpm (r) to the right in the same unit setting status bit to "On" (on) setting status bit "off" (off). Ants perceive it in front (ie, facing the direction of) whether pheromone trail and its status bit is "open", if the status bit is "open" means that the unit has gone through (initially set status bits "Off").
Platform: |
Size: 1014784 |
Author: 李玫 |
Hits: