text:
Cookbook talk:Papadam (Black Gram Flatbread)

* (cur) (last) 02:29, 15 May 2006 Dizzynaz (→Recipe) * (cur) (last) 16:34, 8 May 2006 Thryduulf m (Reverted edits by 66.171.229.131 (talk) to last version by Thryduulf) * (cur) (last) 15:07, 8 May 2006 66.171.229.131 (→External links) * (cur) (last) 02:46, 4 May 2006 Thryduulf (→Recipe - tweak template to show its the section that needs to be moved, not the whole page) * (cur) (last) 02:46, 4 May 2006 Thryduulf (→Recipe - this section should be moved to wikibooks) * (cur) (last) 02:40, 4 May 2006 Thryduulf m (Reverted edits by 24.201.135.180 (talk) to last version by OrphanBot) * (cur) (last) 08:47, 2 May 2006 24.201.135.180 * (cur) (last) 03:37, 17 April 2006 OrphanBot (Removing image with no copyright information. Such images that are older than seven days may be deleted at any time.) * (cur) (last) 11:54, 12 April 2006 Sutharshan1 * (cur) (last) 11:53, 12 April 2006 Sutharshan1 * (cur) (last) 11:45, 12 April 2006 12.146.183.19 (→Recipe) * (cur) (last) 08:38, 12 April 2006 Dr.frog m (categories) * (cur) (last) 00:41, 30 March 2006 84.177.50.105 * (cur) (last) 04:45, 8 March 2006 212.219.231.1 (also poppadom) * (cur) (last) 11:19, 18 February 2006 Ish ishwar (+link) * (cur) (last) 15:03, 7 January 2006 Mceder m (disambiguation link repair (You can help!): salsa) * (cur) (last) 19:19, 3 December 2005 128.220.43.245 * (cur) (last) 15:46, 3 December 2005 68.165.61.175 * (cur) (last) 11:20, 20 November 2005 67.168.196.51 (→Recipe) * (cur) (last) 19:52, 7 October 2005 Dforest ("papadim" fails the google test) * (cur) (last) 18:55, 7 October 2005 Kittynboi * (cur) (last) 19:33, 27 September 2005 Dforest m (rm strange character) * (cur) (last) 18:08, 27 September 2005 203.26.206.130 * (cur) (last) 18:04, 27 September 2005 203.26.206.130 * (cur) (last) 05:37, 6 September 2005 Dforest m   * (cur) (last) 05:33, 6 September 2005 Dforest m    * (cur) (last) 05:30, 6 September 2005 Dforest m    * (cur) (last) 05:28, 6 September 2005 Dforest m (black pepper) * (cur) (last) 05:22, 6 September 2005 Dforest (cleanup) * (cur) (last) 05:09, 6 September 2005 Dforest (dab) * (cur) (last) 05:07, 6 September 2005 Dforest * (cur) (last) 05:06, 6 September 2005 Dforest (rm redundency) * (cur) (last) 05:04, 6 September 2005 Dforest (syntax) * (cur) (last) 05:04, 6 September 2005 Dforest (merged with [pappad]) * (cur) (last) 06:10, 22 August 2005 Limhes * (cur) (last) 00:26, 20 August 2005 Iustinus * (cur) (last) 12:43, 11 August 2005 12.28.177.129 * (cur) (last) 12:42, 11 August 2005 12.28.177.129 * (cur) (last) 05:05, 22 May 2005 144.133.220.253 * (cur) (last) 04:59, 22 May 2005 144.133.220.253
 * (cur) (last) 02:30, 15 May 2006 Dizzynaz (→Recipe) [rollback] [proxycheck]


text:
Transwiki:Paper model tutorials

For people interested in learning techniques on how to create paper models, here is a list of tutorials that others have created, with a description of each and reviews of some. If you know of others, feel free to add them to the list below.

There are many tools and approaches to creating paper models. Often, a 3D modeler program is used to create an electronic version of the object, then imported into a 3D model "unfolding" program (such as Pepakura) that lays the design out flat, ready to be printed.

 * Modeling for FMS with Metasequoia - This doesn't strictly address paper modeling, but it's a useful tutorial on using Metasequoia (a free 3D modeling tool from a Japanese developer)

 * Using PaintShop PRO 6.0 and Microsoft Word to make and color paper models

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Transwiki:Paper model tutorials


text:
Transwiki talk:Paper model tutorials

* (cur) (last) 07:56, 5 May 2006 DBatesx m   * (cur) (last) 07:51, 5 May 2006 DBatesx (Start of tutorial list)
 * (cur) (last) 11:22, 5 May 2006 RHaworth (move to Wikibooks) [rollback] [proxycheck]

title: Transwiki talk:Paper model tutorials


text:
Cookbook:Tipitapa Fish Topped with Salsa (Pescado a la Tipitapa)

 * Fish

Although the tipitapa recipe is a secret, this is the most common substitute to it.

Salsa

 * 1–2 tbsp virgin olive oil
 * ½ ea. onion (vidalia onions are okay, purple or white onions are also acceptable), chopped
 * 3 oz (85 g) tomato, sliced in rings
 * Vinegar
 * Brown sugar
 * Salt
 * Lemon

Fish

 * 5 tbsp virgin olive oil
 * ½–1 lb (225–450 g) whole fresh carp, fully cleaned and scaled
 * Salt

Procedure

 * 1) Heat the oil in a pan over medium heat. Add onions, and cook until translucent.
 * 2) When the onion is translucent, add tomato slices. Cook for 5 minutes, then add a drop or two of vinegar and a pinch of brown sugar. Season to taste with salt. Let it cook for a few more minutes, and set to the side.
 * 3) Heat the 5 tbsp oil in a pan over medium heat. Add the fish to the pan, and fry until the skin is crispy (approximately 7 minutes per side).
 * 4) Place a rack in a baking pan. Transfer the fish to the rack, and bake about 15 minutes at 350°F (175°C).
 * 5) Let the fish cool, then salt to taste and return to its pan. Fry again over low heat for 3 minutes each side while re-heating the salsa.
 * 6) Add the salsa on top of the fish, and serve.


text:
Cookbook talk:Tipitapa Fish Topped with Salsa (Pescado a la Tipitapa)

* (cur) (last) 10:48, 12 March 2006 DMG413 * (cur) (last) 10:46, 12 March 2006 Ana Ruiz * (cur) (last) 10:46, 12 March 2006 Ana Ruiz
 * (cur) (last) 01:20, 13 May 2006 Dogaroon [rollback] [proxycheck]


text:
Body Piercing/Piercing Aftercare

General/Body Piercing Aftercare
'LITHA (Leave it the hell alone)' – This method is exactly what it sounds like. After you get the piercing you leave it alone. Some people hold very strongly to the LITHA method and don’t do any type of cleaning during healing, though many people using this method will clean the piercing with them in the shower. 'SSS (Sea Salt Soaks)' – With this method, you soak your piercing in a warm salt mixture. The appropriate ratio for the mixture is ¼ a teaspoon of non-iodized salt in 8oz or 1 cup of water. For this method, you would do one to two soaks a day for five to ten minutes. During the soak the piercing needs to be completely submerged in the sea salt mixture. After the soak simply rinse your piercing with warm water and pat dry. This method works with your body’s natural salinity to push out any bacteria inside your piercing. For this reason, it’s very important to mix the solution in the right proportions. This is also the recommended aftercare method presented by APP. The APP also recommends the use of anti-microbial soap. Satin and Provon are good, gentle soaps to use in conjunction with sea salt soaks.

'Chamomile Presses' – This is a method similar to sea salt soaks, but better suited for some piercings. The navel, for example, would be difficult to soak. With this method you steep a plain chamomile tea bag in a mixture of ¼ teaspoon of non-iodized salt and 8oz of water. After about five minutes you remove the tea bag and place it over your piercing, applying only enough pressure to hold it in place. For things such a navel it might be easier to simply lie down and avoid unneeded pressure being put on your piercing. For this method, you leave the tea bag resting on the piercing for five to ten minutes before rinsing with warm water and patting dry with a clean paper towel.

Oral Piercing Aftercare
All of the methods above can and should be used to heal oral piercings however there are other things that need to be done for oral piercings specifically.

'Rinsing' – During the course of healing it’s important to rinse your mouth after eating, drinking or smoking. Rinsing out with mouthwash is unnecessary and will likely lead to over cleaning unless you use alcohol-free mouthwash. Instead, warm water or a salt mixture should be used. Mouthwash can be used in the morning and at night if desired.

It’s important while healing an oral piercing to avoid using a mouthwash with alcohol in it. There are a few options. Crest Pro-Health, Tech 200, Biotene, and Listerine Zero are all mouthwashes that don’t contain alcohol.

Cartilage Piercing Aftercare
While there is little that needs to be done specifically for cartilage piercings, a note on patience is prudent. These piercings are notoriously fussy and healing is long. Stress bumps are very common with cartilage piercings. The best means to deal with these bumps is to find the cause and try and avoid it. Other than that, in time they will go away as the piercing heals. So, the most important thing to remember is BE PATIENT.Don't twist the piercing this only sets back the healing process about a few weeks. Doing 1-2 sea salt soaks a day is also very helpful for the aftercare and will help to speed up the healing process. You can do this by using one cup of water and 1/4 teaspoon of sea salt. Do not use more salt than the recommended amount otherwise it could dry out your piercing. Soak your ear in this solution for 3-5 minutes once or twice a day and you should be safe.

General Notes
Never touch a healing piercing with dirty hands.

Do as much research on aftercare as you can BEFORE you get pierced.

title: Body Piercing/Piercing Aftercare


text:
Talk:Body Piercing/Piercing Aftercare

* (cur) (last) 11:46, 10 March 2006 RHaworth [rollback] [proxycheck] * (cur) (last) 11:45, 10 March 2006 RHaworth m (moved Piercing Aftercare to Piercing aftercare) * (cur) (last) 01:22, 10 March 2006 Anguissette

title: Talk:Body Piercing/Piercing Aftercare


text:
Transwiki:Programming problems

This page gives a list of programming problems. These are useful for anyone who wants to learn programming quickly. Each problem has a problem statement and the required output along with multiple solutions (including flawed and ill-performing solutions).

3n + 1 problem
 * Hello world - Write a program to display “Hello world”

 * Addition of 2 numbers - Write a program to add two numbers

 * Greatest of 3 numbers - Find the greatest of three numbers

 * Greatest of N numbers - Find the greatest of N numbers where N is any arbitrary natural number

 * Factorial or Product of N numbers - Given N as input find N! Example: N = 4; output is 24 because 1 x 2 x 3 x 4 = 24

 * Average of N numbers - Find the average of N numbers

 * Generate prime numbers - Write a program to generate N prime numbers

 * Prime or not - Determine whether given number N is prime or not

 * Generate Fibonacci series - Write a program to generate the Fibonacci series which goes like this 1, 1, 2, 3, 5, 8, 13, 21..

 * Factorization - Break down a number into its prime factors

 * Lowest common divisor - Write a program to determine the lowest common divisor for two numbers

 * Lowest common divisor for N numbers - Write a program to determine the lowest common divisor for N numbers

 * Highest common factor - Find the highest common factor for the two given numbers

 * Highest common factor for N numbers - Find the highest common factor for the N given numbers

 * Quadratic roots - Find the roots of a quadratic equation Ax2 + Bx + C = 0 given the coefficients A, B, C

i)	Circle ii)	Square iii)	Rectangle iv)	Cuboid v)	Sphere vi)	Cone vii)	Cylinder
 * Area and volume - Write a program to determine the areas and/or volumes of the following geometric entities

Arithmetic •	1, 2, 3, 4, ... •	1, 3, 5, 7, 9, ... •	2, 4, 6, 8, … •	10, 15, 20, 25 …
 * Number Series generation -

Geometric •	2, 4, 8, 16 … •	10, 100, 1000, 10000, … •	3, 27, 243, …

 * Evaluate cos(x), sin(x) - Write a program to determine the sine and cosine value of given input x.

Ask the user to guess a number between 1 and 100. Try to guess it using the following logic. Say user has chosen number 80 Prog: Is number 50? User: G (My number is greater than that) Prog: Is number 75? User: G Prog: Is number 87? User: L (My number is lesser than that) Prog: Is number 81? User: L (My number is lesser than that) Prog: Is number 78? User: G Prog: Is number 79? User: G Prog: Is number 80? User: Y
 * Guess the number -

Example: Input N is 4219 (say) Output should be 4, 2, 1, 9
 * Digits of a Number - Write a program to display the digits of a number.

Example: The given digits are 4, 2, 1, 9 Output should be 4219
 * Number from digits - Write a program to generate the number given the digits

Example: Output should be 9124 given 4219
 * Reverse a number - Write a program to reverse a number

Input: 7331 (is super prime) Input: 4550 (is not super prime) Hint: 7331 is super-prime because, 7331, 733, 73 and 7 are primes
 * Super-prime - Write a program to find whether N is a super-prime or not

Hint: A number is Armstrong if the sum of cubes of its digits is equal to the number itself Input: 371 (is Armstrong) Input: 456 (is not Armstrong)
 * Armstrong number - Write a program to determine whether a number is Armstrong number or not

 * Generate list of random numbers - Write a program to use an inbuilt library function to generate a list of random numbers. Also try as an added exercise to write a pseudo-random number generator

 * Print ASCII table - Write a program to print the ASCII code and the corresponding character in the form of a table

 * Matrix addition

 * Matrix Multiplication

 * Palindrome

 * Printing practice (Stars and numbers)

 * String manipulation (String concatenation, sub string, remove spaces)

 * Search and replace in strings

 * Time and date display

 * Date difference

 * Eight queens solution checking

 * Eight queens recursive solution

 * Eight queens non-recursive solution

 * Permutations

 * Combinations

 * Anagram checking

 * Anagram generation

 * Number system conversion

 * Travelling salesman problem

 * Bin-Packing problem

 * Sort N numbers

 * Sort strings in array

 * Linear search

 * Binary search

 * Hashing

 * Indexing

 * Binary trees

 * B+ trees

 * Linked list

 * Adaptive multiple choice quiz

 * Telephone directory

 * Expression solving

 * Caesar encryption

 * XOR encryption

 * Random name generation

 * Copy and move files

 * List all directories using recursion and without

 * Spawn a shell process

 * Run two threads

 * Calculator

 * Stack

 * Queues

 * Curve fitting

 * Line fitting

 * Solution of Linear equations

 * Minimax search

 * Preprocessor for C

 * Expression evaluation

 * Sorting in Files

 * Leap year

 * Calendar generation

 * Arithmetic encoding

 * LZW text compression

 * RSA encryption

 * DES encryption

 * Polyalphabetic and Monoalphabetic encryption

title: Transwiki:Programming problems


text:
Transwiki talk:Programming problems

wp hist
* (cur) (last) 06:36, 3 May 2006 139.179.22.13 [rollback] [proxycheck] * (cur) (last) 08:11, 29 April 2006 203.200.95.130 * (cur) (last) 17:50, 20 March 2006 Alba m (I think expand and wikibooks covers it) * (cur) (last) 17:46, 20 March 2006 Alba (wrong template name) * (cur) (last) 16:59, 20 March 2006 Alba (Transwiki to wikibooks) * (cur) (last) 16:22, 4 December 2005 Matt Crypto m (prepare for DES becoming a disambig page) * (cur) (last) 09:17, 25 August 2005 Pearle m (Changing to ) * (cur) (last) 01:16, 14 June 2005 61.246.61.96 * (cur) (last) 07:15, 26 May 2005 UkPaolo (tidied up formatting - node still needs more content though!) * (cur) (last) 10:59, 24 May 2005 Rebrane (Stubsensor cleanup project. Please see conflict resolution if you wish to revert.) * (cur) (last) 20:17, 17 May 2005 Prashanthellina m   * (cur) (last) 00:20, 3 May 2005 Prashanthellina * (cur) (last) 00:07, 3 May 2005 Prashanthellina * (cur) (last) 00:06, 3 May 2005 Prashanthellina m   * (cur) (last) 17:03, 30 April 2005 Crisófilax * (cur) (last) 15:39, 22 April 2005 TheParanoidOne m * (cur) (last) 15:38, 22 April 2005 TheParanoidOne m (Stub-sorting. You can help!) * (cur) (last) 02:38, 17 April 2005 Prashanthellina * (cur) (last) 02:25, 17 April 2005 Prashanthellina * (cur) (last) 02:21, 17 April 2005 Prashanthellina (Created page, requires more content) big Subscript text

title: Transwiki talk:Programming problems


text:
Horticulture/Cactus

Cacti are usually pretty easy to grow. Almost all cacti are able to handle neglect and will soon grow with a little care. Cacti adapt very easily to the dry conditions found in the home. Some cacti can grow to be only a few inches tall but others can grow so big that they will eventually outgrow your home. Some may grow to stand upright, or others may only grow to form a big ball, cacti are generally limited by how big their container is, these containers being hanging baskets or ornamental balls. Cacti grow slowly as houseplants, typically only a few inches a year, the cacti will grow quickest during the months of March and September.

You should water your cacti according to the location they are in. If they are in a place that gets very hot, you need to water them once a week. If they are in a place that is milder then watering them once a month would be fine. When you do water, do so in the morning and be sure that the cacti is positioned to get a little morning sun after watering. The cacti cannot ever be permitted to sit in water. Soil that has been waterlogged will rot the roots of the cacti. Cacti plants do best in a rich soil, but only if it is free-draining. Commercial cacti potting soils can be used, or if you can make your own by putting together equal parts of a peat-based potting soil and sand or grit. http://www.cactofilia.com/Growing-Cactus-Fat-plants/Soil

Cacti usually prefer to be planted in a pot and should only be repotted as needed. April is the best time to repot the cacti. When you do repot you need to wear heavy gloves or wrap the cacti in newspaper. Put the cacti in a container that is only a little larger than the previous container. After you repot the cacti, you should wait several days before watering. Use a low nitrogen fertilizer once a month from June to September. You should never fertilize repotted plants during the winter.

When you get your cacti home you will want to place it in a well lit position in your home. It needs to be able to get some direct sunlight throughout the day. Cacti will do best in a temperature that is anywhere from 65 to 85 degrees Fahrenheit during the growing season. Dormant cacti plants will do best in temperatures between 45 and 55 degrees Fahrenheit in winter. The best place for cacti in winter is a sunny cool room or next to a window where it is cooler. During the summer cacti can be moved outside and will adapt very well to the change of climates. For the first weeks, place them in partial shade so they can have a chance to adjust to the brighter light.

A few types of Arid Climate Cacti are:

Star Cactus-this is easy to grow. This is a green spineless cactus and has white flakes on the outside of the ribs.

Golden Barrel Cactus-sits upright and has a green body that is covered with gold-yellow spines. The flowers are also gold. This cactus would be good for beginners.

A few things to remember when caring for your cacti, if your not sure whether to water the cacti or not, then you should probably wait until the next week. The cacti will be able to handle the neglect better than the over watering. Don’t put the cacti too close to the glass on the window, if the temperature raises above the 86 degree mark, then this could burn your cacti. Enjoy your cacti!!!

Culture des Cactus

title: Horticulture/Cactus


text:
Talk:Horticulture/Cactus

* (cur) (last) 13:42, 16 March 2006 RHaworth (transwiki tag) * (cur) (last) 13:33, 16 March 2006 Eknudsen * (cur) (last) 13:29, 16 March 2006 Eknudsen * (cur) (last) 13:28, 16 March 2006 TheKoG (Looks like it might be original research.) * (cur) (last) 13:25, 16 March 2006 Eknudsen * (cur) (last) 13:22, 16 March 2006 Eknudsen
 * (cur) (last) 19:15, 21 April 2006 12.221.50.17 [rollback] [proxycheck]

title: Talk:Horticulture/Cactus


text:
Wine/Storage

Proper wine storage is a very important thing. When one typically purchases large quantities of assorted wines, it is natural that among all other reasons, future consumption is the key. Proper wine storage can lead to a great many years of future enjoyment. Wine storage also provides time for immature vintages to develop into something special. Correct wine storage provides the wine lover the ability to collect and store large qualities of there favorite wines to be enjoyed for years to come.

When considering a large investment in wine, the wine lover must consider the method in which he stores his wine. Improper storage can damage wine and thus diminish the possibility of enjoyment.

Chiefly, the purchaser will consider where he will store his or her wine. Here, he has options. Either he might store it at home or hire an outside service to store the wine for him. The wine lover must protect the wine from the elements.

While 90% of all wine is meant to be consumed within one year, a true connoisseur and collector may wish to consider an additional investment in a wine cellar. Significant thought and planning should go into this process. These are the things that should be considered in this process.

 * Location of the wine cellar

 * Temperature of the wine cellar

 * Humidity and ventilation of the area

 * Composition of the floor

 * Lighting of the space

The location of the wine cellar is very important. When underground, it is best that it’s a room that is facing to the north. This is necessary as this wall receives the minimum amount of solar radiation during the day thus causing less retention of heat. The northern part of the perimeter of this room must not be adjacent to a road nor railway and made of stone or brick. The wine cellar must not be subject to unnecessary movement or vibrations. Vibrations can disturb and damage wine.

The wine ideally, must be stored at temperatures between 10°-14° Celsius. The wine must be kept cool. This is done by keeping the wine underground and minimizing exposure to solar radiation.

Humidity must be controlled in order to keep the cork moist and functioning. A functioning cork maintains the integrity of the wine. The humidity should be between 70-75%. This level of humidity would cause mold to form in a normal house.

A floor of earth or sand is important, as this also helps to reduce the level of vibrations in the room.

Lastly, the lighting must originate from unscented candles. Neon or fluorescent lighting cannot be considered as they kill wine. The candles used must be unscented as a scented candle will foul the wine. Once these 5 considerations are undertaken, a new problem emerges. That is, what to stock the wine cellar with. While this question is beyond the scope of this paper, it is sincerely wished that everyone stock their cellars with all sorts of wine that they enjoy. This is certainly the intention of the entire effort.

title: Wine/Storage


text:
Talk:Wine/Storage

wp hist
* (cur) (last) 07:42, 8 May 2006 That Guy, From That Show! (typo/grammar patrolling ( WP:Typo and WP:Grammar you can help!)) [rollback] [proxycheck] * (cur) (last) 06:13, 21 April 2006 150.101.106.153 * (cur) (last) 06:10, 21 April 2006 150.101.106.153 * (cur) (last) 10:30, 30 January 2006 Melaen * (cur) (last) 23:36, 29 November 2005 Pearle m (Changing to ) * (cur) (last) 20:30, 28 November 2005 Jossi (merge to) * (cur) (last) 20:28, 28 November 2005 Jesuit27

title: Talk:Wine/Storage


text:
Physical Activity/Pulldown Exercise

The lat pulldown is an excellent exercise for working the Lattissimus Dorsi. When doing this exercise there are several things to focus on.

 * Begin by sitting in an upright position with the thigh pad set snug against the thighs.
 * Next, the grip of the bar should be outside shoulder width (wide grip).
 * Now grip the bar with palms pronated (facing away from you).
 * Once you have the proper grip, slightly recline while maintaining the arch in your back. This allows for a better angle and better clearance during the ROM (range of motion).
 * The important factor here is to maintain this angle by keeping proper posture. NO SWINGING OF THE BODY - to help think of pulling your belly button towards your spine and continue keeping your core contracted.   This is your starting point.
 * Now the most important factor when working the lats:
 * Your first motion should begin by pulling the scapula (shoulder blade) down without bending the elbows. This first motion is so important because the movement is being initiated by the lats and  not the biceps. The biceps are only an assistant muscle during this and other back exercises.  Keep in mind  this is a very small movement - only about an inch.  You should immediately feel the lats contract  right below the arm pit area.
 * Continue pulling till the bar reaches the top of the chest. Keeping your posture, slowly raise the bar back to the beginning position and repeat.

This may take a few times before getting familiar with the first movement occurring at the shoulder. The reason for this is that it's natural for the body to want the elbows to bend first which recruits the biceps much more than needed. There is no way to eliminate the biceps; what you are trying to negotiate is the degree of assistance. You may have experienced with using too much biceps after finishing a set and feeling the arms being fatigued and nothing in the lats. Please keep in mind this is not always the case, however, it's much more common than not. So once again the two main factors to focus on are: 1. Keep your body position slightly reclined, not allowing any movement at any time; and 2. Initiate the movement with the shoulders not the elbows.

title: Physical Activity/Pulldown Exercise


text:
Talk:Physical Activity/Pulldown Exercise

* (cur) (last) 01:32, 13 April 2006 RHaworth (it is Wikibooks for how-to's)   * (cur) (last) 17:41, 12 April 2006 DMG413 (move to wikisource) * (cur) (last) 17:39, 12 April 2006 Jeremary
 * (cur) (last) 01:32, 13 April 2006 RHaworth m (moved Pulldown exercice to Pulldown exercise) [rollback] [proxycheck]


text:
Cookbook:Qabuli (Central Asian Rice Pilaf)

South Asian cuisines

Ingredients

 * 500 g dry chickpeas
 * Salt
 * Red pepper
 * ½ tsp ginger garlic paste
 * 1 kg rice
 * Shortening
 * 3 onions, chopped
 * Chile powder
 * Tomato paste
 * ¼ tsp turmeric powder
 * ½ cup chopped cilantro
 * 4–5 green chiles, cut in half

Procedure

 * 1) Soak the chickpeas for half an hour.
 * 2) Boil the chickpeas with salt, red pepper, and ginger garlic paste. Be mindful that after the chickpeas have been cooked, there should not be any water remaining.
 * 3) If there is water remaining, continue cooking until the water has been mostly absorbed.
 * 4) In the meantime, bring the rice to a full boil. Reduce heat to a minimum and cover. Allow to cook for 8–10 minutes, then turn off the heat and allow to rest for a similar amount of time.
 * 5) Also, in the meantime, heat some shortening in a pan. Fry the onions until they are light brown, then add tomato paste, salt, red chile powder, and turmeric powder.
 * 6) Arrange the fried onion with the spices, boiled chickpeas, and rice in a large serving dish pot.
 * 7) Garnish with chopped cilantro and green chillies and serve hot.


text:
Cookbook talk:Qabuli (Central Asian Rice Pilaf)

* (cur) (last) 13:56, 8 May 2006 Naconkantari m (Reverted edits by 24.206.75.127 (talk) to last version by Salmaakbar) * (cur) (last) 13:56, 8 May 2006 24.206.75.127 * (cur) (last) 13:28, 8 May 2006 Salmaakbar * (cur) (last) 19:49, 7 May 2006 Bayyoc * (cur) (last) 19:46, 7 May 2006 Salmaakbar
 * (cur) (last) 20:05, 14 May 2006 Salmaakbar [rollback] [proxycheck]


text:
RC Airplane/RCAP

Description
The RCAP v.3 is a Remote Control Autopilot for model airplanes and cars. The autopilot function can be switched off or on during flight with the flick of a switch. It requires a GPS antenna, and a computer to upload the waypoint coordinates to the WPS (Waypoint Sequencer. The navigation board, connects directly to the waypoint sequencer and to the GPS antenna/module (OEM GPS).

Please come back for an updated project an information on the RCAP v.3

Description
The RCAP2 is a Remote Control AutoPilot for model airplanes, cars and boats. The autopilot function can be switched off or on during flight with the flick of a switch. For it to function, a NMEA capable GPS (with either an OEM GPS for new firmware being developed rcgroups thread, or with programmable goto/waypoints functions) must be connected to the serial input port of the RCAP2.

This Wikipedia article describes what the RCAP2 is, what you can do with it, how it works and how to install it. The article is not meant to be a how-to for the RCAP2. For that information you should visit the manufacturer website of the RCAP2.

The original RCAP was conceived by Mike Pawlowski. Mike wrote the firmware v1.1 for the RCAP, which this RCAP2 is based on. He also designed the original RCAP board, which this RCAP2 is based on. Many thanks to Mike for publishing his work as open source. His website and source code can be found on sourceforge. The RCAP2 is pin for pin compatible to the original RCAP. Some additional headers and servo ports have been added for future use. You will find them described below.

The RCAP2 is available from Scale Robotics in 2 flavours:
 * 1. Pre-built and soldered RCAP2 GPS waypoint tracking (some items need to be added by customer, see below)
 * 2. RCAP2 PCB kit & parts for gps waypoint tracking

Software/Firmware can be found here, and servo.inc and other original firmware for can be found here. The source code for this project was programmed using PicBasic Pro. This software is available from MELabs. PicBasic Pro is only necessary if you wish to customize the program of the RCAP2.

The version that is currently being sold (Nov 2007) contains bootloader functionality which makes it possible to upload new firmware to your RCAP2 by connecting the it to the serial port of your computer through a null-modem cable.

How does it work
Very soon I will be adding more information on how the RCAP works.

Before buying
Before you jump into buying the RCAP2, you have to realize that to make your UAV system complete, there are a few other items that you need to have/buy to get started. Also there are things that need to be considered before taking the plunge into RCAP2:
 * Airplane / boat / car) in which you are going to use the RCAP2
 * a GPS device that is can store waypoints/routes
 * Read Use and Limited Liability paragraph

Installation
Before you can actually use the RCAP2 there is some minor work to do. This includes soldering to the board. If you don't feel comfortable with soldering, then find someone that can help you with this.

Power

To power the board, I suggest you to choose a connector that mates with the connector on your powersupply (ie. batterypack). The connector can be attached to the board through wires. Soldering has to be done for powering the board and in some cases for connecting the RCAP2 to your receiver.

Solder the red wire (positive lead) coming from the connector to the pad marked with a + sign and the black wire (negative lead) to the pad marked with the '-' sign. These pads are a little hard to find. If you look at the image above, you will see 2 blue capacitors, just next to the DB9 connector. The pads can be found below the capacitor nearest to the edge of the board. You probably have to bend away the capacitor to have access to the pads. Be careful not to bend the legs of the capacitors to often or it will break and cause your board not to work anymore.

Receiver connection

In the image above you see jumper J3 (enable channel) and J4 (RCAP2 to Rudder on receiver). To save weight -crucial for airborne models- some boards are sold without the jumper. If you received your board without thes jumpers you have to solder servo extension wires to the board. The servo extension cord should have a female connector on 1 side (for connecting it to, in most cases, the landing gear/flaps channel and rudder channel of your receiver). The pads that you connect ground to is the pad closest to the edge of the board. Slide the servo wire into the board from the upside and solder it on the backside of the board.

Rudder

In most cases you want to use your rudder for steering from one waypoint to another. Connect your rudder servo to jumper J2 on the RCAP2 board.

Also connect the servo wire coming from J4 to the rudder channel of your receiver

First use
Before using the RCAP2 for the first time, be assured that you have the latest firmware version.

Your RCAP2 board contains a PIC Microcontroller (type 16F876A) that contains the software that takes care of sending your model to pre-programmed waypoints. On the microcontroller you will find a label with the firmware version that is in the chip. New firmwares can be downloaded from the RCAP2 RCAP2 website, follow the link to firmware and download the latest HEX file. You also need the software to upload the HEX file to the RCAP2 board that you find on the same page.

After downloading the firmware, use the null-modem cable to connect the RCAP2 to your computer (note: Notebooks don't work in most cases since the power they can supply through the serial ports is too low). Follow the instructions on the firmware page on how to upload the firmware to the RCAP2.

Be sure to set your GPS data transfer settings to NMEA/NMEA at 4800 baud. A new firmware has come available (2006-05-03) which makes it possible to work on 9600 baud, go to the firmware website to download this new version

Now follow the procedure below for first use.
 * 1. Connect the wire coming from J3 to your receiver's landing gear or flaps channel (please take note of correct polarity) and J4 to the rudder channel on your receiver.
 * 2. Connect the rudder servo to jumper J2 (check polarity)
 * 3. Switch off landing gear (or flaps) channel of your transmitter
 * 4. Program a route into your GPS device by adding waypoints, when finished, switch of the GPS device
 * 5. Connect your GPS device through a cable to the RCAP2
 * 6. Switch on your transmitter
 * 7. Switch on your GPS device
 * 8. Select the goto function of your GPS device and select a waypoint.
 * 8. Power up your receiver (by connecting the battery to your Electronic Speed Control)
 * 9. Connect the RCAP2 to the powersupply

No smoke? great! You did well. Now, when the RCAP is first powered, it samples the transmitters rudder stick for neutral position. In versions previous to 1.6, it also samples the rudder position (and assumes it to be neutral) each time the autopilot is enabled. This means that you must be in neutral rudder position each time you flip to autopilot if you are using versions previous to 1.6. This is important for the autopilot to function properly. During power up, you will see the LED light for the first 6 or so seconds after you apply power to the RCAP.

Now verify if all controls on your model work as they are supposed to do. If something doesn't work as it is supposed to do, then check your connections and see if you followed all steps of the procedure above. Maybe you forgot something.

If everything works correctly, you are ready to flip the landing gear (or flaps) switch on your transmitter to switch on the RCAP2 autopilot function. The LED should start to blink every 2 seconds or so. This indicates that your RCAP2 has autopilot enabled, and valid GPS data is being received through the serial port. If the LED is not blinking, then check if all the following conditions are met:
 * The GPS device is receiving good data and plugged in correctly to the RCAP2
 * The GPS is set to output NMEA in/out at 4800 baud (or 9600 baud with latest firmware - see above)
 * A waypoint selected and in goto mode
 * All connections between receiver, and RCAP made properly
 * Autopilot enabled with transmitter

Testing your RCAP2
Comming soon...

Recommendations
It is suggested that the RCAP2 be used only on high wing trainer type aircraft. The original RCAP website suggests that it only be used with a FMA Co-pilot type device, in order to keep your plane stable. It is unknown whether an inherently stable aircraft could be flown successfully with the RCAP2 without a flight stabilization system. The original RCAP site shows a FMA Copilot being connected to the elevator and ailerons, while the RCAP is connected to the rudder.

Configuring the RCAP2
There are 3 variables to set to the RCAP2 and have it work the way you want, those are Travel, Gain and Servo direction.

Travel Max Servo Travel (Variable resistor R2) allows you to set a maximum end point that you will allow a servo to travel. This is especially important when installing the RCAP into an aircraft. I recommend starting with a minimal setting and increasing it slowly. For your information a max setting of travel is attained when the pot is set fully counter clockwise.The position of this pot will be looked at each time autopilot is selected.

Gain Course Correction Gain (Variable resistor R3) allows you to adjust how aggressively you want to RCAP to remain on course. A low setting means that the RCAP will slowly turn toward the current course. A high setting will have the turns perform much quicker. The amount of correction used is also proportional to the amount off course the vehicle is, the greater the amount off course, the greater the correction is. I would recommend starting with a minimal setting and increasing it slowly. For your information, a max setting of gain is attained when the pot is set fully counter-clockwise.

Servo direction Servo direction simply allows you to reverse the direction a servo turns while the RCAP autopilot mode is selected. While in radio controlled flight (autopilot off), your transmitter takes care of servo direction. The transmitter uses the settings you have done in the radio. When autopilot is on, you give control to the RCAP2 and it is not aware of any transiter settings. Before actually putting the RCAP into your vehicle your have to make sure it matches the expected response. You must test this with the GPS attached, waypoint selected, passing a waypoint position one side or the other while looking at the rudder to ensure that it is turning the proper direction to turn toward the waypoint. This switch position is looked at every time the autopilot mode is selected.

Custom programming
Programming or modifying your own code is possible as the PIC16F876A chip can be reprogrammed about 100,000 times. The RCAP2 currently comes with version 1.6B programmed in. This version includes a small bootloader code in the firmware that allows the chip to be programed easily through the serial port. With version 1.6B no programmer will be required. If you are interested in a programmer, there are many programmers out there. Many will need a separate adapter to program a 28 pin chip. PicBasicPro was the software tool used to  create  Main.bas  (ver 1.1 RCAP code), as well as each successive version. This program makes it relatively easy to program a PIC chip using code similar to the Parallax Basic Stamp code. PicBasic Pro is made by MELabs, and can be found on their website.

If you think you have designed a useful piece of code, then we would love to hear from you about it. Please contact Scale Robotics and let us know what you have made. We might consider to use your code in feature releases of our firmware.

Debugging Debug is a tool you can use to get information out of your PIC chip. You can use the provided code debug-main.hex to help you understand what is going on inside the RCAP2. This is not going to be available, unless you program the chip that way. it is easiest to work with the debugging port, J7. This gives you the following status while you have turned on autopilot mode.

Use and Limited Liability
You should always fly your model within visual range. Also it's very important to stay keep your model within your transmitter's range. Never fly near the limits of your range. You may not be able to switch it out of autopilot mode, should it become necessary. The RCAP2 may generate extra electronic noise that reduces the range of your transmitter. You should fully bench test and range test your setup with a friend thoroughly before your first flights are attempted. Be sure to meet all regulations that are made by the local authorities/model assocations in your country (id. AMA, FAA and/or others). Scale Robotics Inc. shall not be held responsible for any incidental, consequential or direct damages or expenses associated with the use or misuse of its products.

Technical information
A glance at the board. Specifications and a description of the connectors, jumpers, etc... you will find on the board. Some jumpers are for future use, for example, altitude-hold through a pressure sensor is being worked on. Furthermore a list of all components on the RACP2 board.

Unlabeled 6 pin header above J5:   This header is made up of spare pins from the board that are currently unused by the RCAP. Pins from left to right: PortC,4 PortA,1 PortA,2 PortC,0 PortC,2 PortC,3

User tests/stories/testimonials
In this paragraph you will find stories or links to stories from RCAP2 customers. You will see how they have come to their setup, what obstacles they have run into, etc...

After some start up troubles, kd7ost reported about his first successful flights:
 * RCAP unit test flown

 * Well, we didn't get much of a break but it was enough. The winds settled down to 15 mph. Jeff had the Telemaster 40 ready to go with the RCAP on its own power source. He managed to fit the Garmin geko 201 above the fuel tank so we gave it a go late in the day.

 * Jeff had also worked his FS8 receiver into the project so would have a failsafe unit to further test with. Set location as a waypoint and performed a “goto”. Fueled up and into the air, climb out to a safe altitude and first got the roll and pitch control working to satisfaction. Next, flew down wind and back towards us to engage the RCAP while observing results. We were standing at the waypoint. The plane got overhead and as soon as it passed the waypoint it started a gentle right hand turn. We watch as it slowly came around, went back down wind a fair ways and finished the turn heading right back at us. Over head again and it repeated. It was loitering at the waypoint. Jeff had the gain set to about 50 percent and that was a little light for the Telemaster. We brought it in and tweaked the gain up to about 100 percent deflection.

 * Back up and set it again. It kept in a little tighter this time. We continued to fly and were so happy watching and evaluating it that we let the fuel run out. Dead sticked in, re-fueled and back up for more. Jeff flew it off in the distance till it was a spec in the distance and shut of the transmitter to fully test the failsafe and return. Within a few minutes it was obediently overhead back into the loiter pattern. As a long time PDC-10¹ user I can say this performs just like the now retired PDC-10. Several more test’s were done trying various directions, down wind, (still up at 15 mph) up wind, cross wind etc and it came back over head every time.

 * Due to not having the time to plot a course we didn’t send it out on an autonomous flight. But that’s a function of the GPS and I know this RCAP would have flown the route and returned to loiter overhead.

 * Congratulations to Scale Robotics. You got a winner. We're still waiting for decent weather but I know there will be many flights to come with the unit.

¹) The PDC-10 is an obsolete UAV product from Unav.

The story above originates from this thread on the RC Groups forums. In that thread the initial problems with getting the RCAP2 working correctly with a GPS device were discussed.

title: RC Airplane/RCAP


text:
Talk:RC Airplane/RCAP

* (cur) (last) 02:02, 3 May 2006 Jandirks (→First use) [rollback] [proxycheck] * (cur) (last) 08:10, 26 April 2006 JoeBot m (typo fix: "usefull" to "useful" using AWB) * (cur) (last) 09:16, 24 April 2006 JoeBot m (typo fix: "sucessful/sucessfull/successfull" to "successful" using AWB) * (cur) (last) 12:12, 22 April 2006 JoeBot m (typo fix: the word "receive" and its derivatives using AWB) * (cur) (last) 09:49, 17 April 2006 82.172.248.70 (→First use) * (cur) (last) 09:48, 17 April 2006 82.172.248.70 (→First use) * (cur) (last) 09:46, 17 April 2006 82.172.248.70 (→Installation) * (cur) (last) 09:43, 17 April 2006 82.172.248.70 (→Installation) * (cur) (last) 09:42, 17 April 2006 82.172.248.70 (→Installation) * (cur) (last) 09:41, 17 April 2006 82.172.248.70 (→Installation) * (cur) (last) 22:40, 14 April 2006 71.116.75.93 (→User tests/stories/testimonials) * (cur) (last) 00:52, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:52, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:51, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:50, 13 April 2006 Scm83x m (Propose Transwiki move. Move to Wikibooks) * (cur) (last) 00:50, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:49, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:49, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:49, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:48, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:48, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:48, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:47, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:47, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:45, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:44, 13 April 2006 193.172.178.198 (→Technical information) * (cur) (last) 00:43, 13 April 2006 193.172.178.198 (→Use and Limited Liability) * (cur) (last) 00:37, 13 April 2006 193.172.178.198 (→Custom programming) * (cur) (last) 00:36, 13 April 2006 193.172.178.198 (→Custom programming) * (cur) (last) 00:36, 13 April 2006 193.172.178.198 (→Use and Limited Liability) * (cur) (last) 00:35, 13 April 2006 193.172.178.198 (→Use and Limited Liability) * (cur) (last) 00:34, 13 April 2006 193.172.178.198 (→Use and Limited Liability) * (cur) (last) 00:33, 13 April 2006 193.172.178.198 (→Use and Limited Liability) * (cur) (last) 00:33, 13 April 2006 193.172.178.198 (→Use and Limited Liability) * (cur) (last) 00:28, 13 April 2006 193.172.178.198 * (cur) (last) 00:28, 13 April 2006 193.172.178.198 * (cur) (last) 00:28, 13 April 2006 193.172.178.198 * (cur) (last) 00:27, 13 April 2006 193.172.178.198 * (cur) (last) 00:16, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:16, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 00:15, 13 April 2006 193.172.178.198 (→User tests/stories/testimonials) * (cur) (last) 07:31, 12 April 2006 Jandirks (→User stories/testimonials) * (cur) (last) 07:27, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:26, 12 April 2006 Jandirks (→User stories/testimonials) * (cur) (last) 07:26, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:25, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:24, 12 April 2006 Jandirks (→Testing your RCAP2) * (cur) (last) 07:24, 12 April 2006 Jandirks (→Testing your RCAP2) * (cur) (last) 07:23, 12 April 2006 Jandirks (→Recommendations) * (cur) (last) 07:22, 12 April 2006 Jandirks (→Before buying) * (cur) (last) 07:21, 12 April 2006 Jandirks (→Before buying) * (cur) (last) 07:19, 12 April 2006 Jandirks (→Use & limited liability=) * (cur) (last) 07:18, 12 April 2006 Jandirks (→Custom programming) * (cur) (last) 07:14, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:14, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:13, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:13, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:12, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:11, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:10, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:10, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:09, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:09, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 07:04, 12 April 2006 Jandirks (→Custom programming) * (cur) (last) 07:03, 12 April 2006 Jandirks (→Custom programming) * (cur) (last) 06:57, 12 April 2006 Jandirks (→Custom programming) * (cur) (last) 06:54, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 06:44, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 06:43, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 06:42, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 06:40, 12 April 2006 Jandirks (→Technical information) * (cur) (last) 06:20, 12 April 2006 Jandirks (→Configuring the RCAP2) * (cur) (last) 23:17, 10 April 2006 Jandirks (→RCAP2 Remote Control Auto Pilot) * (cur) (last) 10:37, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 10:36, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 10:35, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 10:32, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 10:24, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 10:23, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 10:21, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 10:18, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 10:16, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 08:28, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 08:28, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 08:27, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 08:22, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 08:21, 10 April 2006 82.172.248.70 (→Technical information) * (cur) (last) 08:17, 10 April 2006 82.172.248.70 * (cur) (last) 08:15, 10 April 2006 82.172.248.70 (→Configure the RCAP2) * (cur) (last) 08:14, 10 April 2006 82.172.248.70 (→Configure the RCAP2) * (cur) (last) 08:13, 10 April 2006 82.172.248.70 (→Configure the RCAP2) * (cur) (last) 08:12, 10 April 2006 82.172.248.70 (→Before buying) * (cur) (last) 08:11, 10 April 2006 82.172.248.70 * (cur) (last) 07:59, 10 April 2006 82.172.248.70 (→First use) * (cur) (last) 07:58, 10 April 2006 82.172.248.70 (→First use) * (cur) (last) 07:46, 10 April 2006 82.172.248.70 * (cur) (last) 06:02, 8 April 2006 71.116.75.93 (→Description) * (cur) (last) 06:01, 8 April 2006 71.116.75.93 (→Description) * (cur) (last) 10:28, 7 April 2006 RHaworth (move to Wikibooks) * (cur) (last) 10:04, 7 April 2006 Scalerobotics m (→Description) * (cur) (last) 10:03, 7 April 2006 Scalerobotics (→Description) * (cur) (last) 10:00, 7 April 2006 Scalerobotics (→Description) * (cur) (last) 09:58, 7 April 2006 Scalerobotics (→Description) * (cur) (last) 07:35, 7 April 2006 Jandirks (→Description) * (cur) (last) 07:18, 7 April 2006 Jandirks (→Description) * (cur) (last) 07:17, 7 April 2006 Jandirks (→Description) * (cur) (last) 07:17, 7 April 2006 Jandirks (→Description) * (cur) (last) 07:16, 7 April 2006 Jandirks (→First use) * (cur) (last) 07:13, 7 April 2006 193.172.178.198 (→First use) * (cur) (last) 07:09, 7 April 2006 193.172.178.198 (→First use) * (cur) (last) 06:59, 7 April 2006 Jandirks * (cur) (last) 06:57, 7 April 2006 Jandirks * (cur) (last) 06:52, 7 April 2006 Jandirks (→Installation) * (cur) (last) 06:51, 7 April 2006 Jandirks (→Description) * (cur) (last) 06:50, 7 April 2006 Jandirks (→Description) * (cur) (last) 06:49, 7 April 2006 Jandirks (→Installation) * (cur) (last) 06:49, 7 April 2006 Jandirks (→Installation) * (cur) (last) 06:48, 7 April 2006 Jandirks (→Installation) * (cur) (last) 06:48, 7 April 2006 Jandirks (→Installation) * (cur) (last) 06:47, 7 April 2006 Jandirks (→Installation) * (cur) (last) 06:47, 7 April 2006 Jandirks (→Installation) * (cur) (last) 06:46, 7 April 2006 Jandirks (→Description) * (cur) (last) 06:46, 7 April 2006 Jandirks (→Installation) * (cur) (last) 06:45, 7 April 2006 Jandirks (→Installation) * (cur) (last) 06:45, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:45, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:44, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:44, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:44, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:43, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:42, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:42, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:39, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:39, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:37, 7 April 2006 Skysmith (no category) * (cur) (last) 06:37, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:36, 7 April 2006 Jandirks (→First use) * (cur) (last) 06:36, 7 April 2006 Jandirks

title: Talk:RC Airplane/RCAP


text:
Spanish/Hacer

../Verbs/

=Hacer=

"Hacer" is an irregular verb that means  "to make or to do".

 * Infinitive: hacer
 * Present participle: haciendo
 * Past participle: hecho

Present

 * Yo hago
 * tú haces
 * él/ella/usted hace
 * nosotros hacemos
 * (vosotros hacéis)
 * ellos/ustedes hacen

../Imperfect/

 * Yo hacía
 * tú hacías
 * él/ella/usted hacía
 * nosotros hacíamos
 * (vosotros hacíais)
 * ellos/ustedes hacían

../Preterite/

 * Yo hice
 * tú hiciste
 * él/ella/usted hizo
 * nosotros hicimos
 * (vosotros hicisteis)
 * ellos/ustedes hicieron

../Future/

 * Yo haré
 * tú harás
 * él/ella/usted hará
 * nosotros haremos
 * (vosotros haréis)
 * ellos/ustedes harán

— or —

 * Yo voy a hacer
 * tú vas a hacer
 * él/ella/usted va a hacer
 * nosotros vamos a hacer
 * (vosotros vais a hacer)
 * ellos/ustedes van a hacer

../Subjunctive/

 * Yo haga
 * tú hagas
 * él/ella/usted haga
 * nosotros hagamos
 * (vosotros hagáis)
 * ellos/ustedes hagan

../Imperfect Subjunctive/

 * Yo hiciera
 * tú hicieras
 * él/ella/usted hiciera
 * nosotros hiciéramos
 * (vosotros hicierais)
 * ellos/ustedes hicieran

— or —

 * Yo hiciese
 * tú hicieses
 * él/ella/usted hiciese
 * nosotros hiciésemos
 * (vosotros hicieseis)
 * ellos/ustedes hiciesen

Present perfect subjunctive

 * Yo haya hecho
 * tú hayas hecho
 * él/ella/usted haya hecho
 * nosotros hayamos hecho
 * (vosotros hayáis hecho)
 * ellos/ustedes hayan hecho

Pluperfect subjunctive

 * Yo hubiera hecho
 * tú hubieras hecho
 * él/ella/usted hubiera hecho
 * nosotros hubiéramos hecho
 * (vosotros hubierais hecho)
 * ellos/ustedes hubieran hecho

— or —

 * Yo hubiese hecho
 * tú hubieses hecho
 * él/ella/usted hubiese hecho
 * nosotros hubiésemos hecho
 * (vosotros hubieseis hecho)
 * ellos/ustedes hubiesen hecho

../Conditional/

 * Yo haría
 * tú harías
 * él/ella/usted haría
 * nosotros haríamos
 * (vosotros haríais)
 * ellos/ustedes harían

../Imperative/

 * Yo ---
 * tú haz; no hagas
 * él/ella/usted haga
 * nosotros hagamos
 * (vosotros haced; no hagáis)
 * ellos/ustedes hagan

Compound tenses
These tenses are combinations of the above tenses.

../Present Progressive/

 * Yo estoy haciendo
 * tú estás haciendo
 * él/ella/usted está haciendo
 * nosotros estamos haciendo
 * (vosotros estáis haciendo)
 * ellos/ustedes están haciendo

../Imperfect Progressive/

 * Yo estaba haciendo
 * tú estabas haciendo
 * él/ella/usted estaba haciendo
 * nosotros estábamos haciendo
 * (vosotros estabáis haciendo)
 * ellos/ustedes estaban haciendo

../Preterite Progressive/

 * Yo estuve haciendo
 * tú estuviste haciendo
 * él/ella/usted estuvo haciendo
 * nosotros estuvimos haciendo
 * (vosotros estuvisteis haciendo)
 * ellos/ustedes estuvieron haciendo

../Present Perfect/

 * Yo he hecho
 * tú has hecho
 * él/ella/usted ha hecho
 * nosotros hemos hecho
 * (vosotros habéis hecho)
 * ellos/ustedes han hecho

../Present Perfect Progressive/

 * Yo he estado haciendo
 * tú has estado haciendo
 * él/ella/usted ha estado haciendo
 * nosotros hemos estado haciendo
 * (vosotros habéis estado haciendo)
 * ellos/ustedes  han estado haciendo

../Pluperfect/

 * Yo había hecho
 * tú habías hecho
 * él/ella/usted había hecho
 * nosotros habíamos hecho
 * (vosotros habíais hecho)
 * ellos/ustedes habían hecho

../Preterite Perfect/

 * Yo hube hecho
 * tú hubiste hecho
 * él/ella/usted hubo hecho
 * nosotros hubimos hecho
 * (vosotros hubisteis hecho)
 * ellos/ustedes hubieron hecho

../Future Perfect/

 * Yo habré hecho
 * tú habrás hecho
 * él/ella/usted habrá hecho
 * nosotros habremos hecho
 * (vosotros habréis hecho)
 * ellos/ustedes habrán hecho

../Perfect Conditional/

 * Yo habría hecho
 * tú habrías hecho
 * él/ella/usted habría hecho
 * nosotros habríamos hecho
 * (vosotros habríais hecho)
 * ellos/ustedes habrían hecho

title: Spanish/Hacer


text:
Spanish/Expressions/Hacer

=Expressions using the verb hacer=

Weather

 * hace frío It's cold.
 * hace calor It's warm.

Time
Hace + tiempo + que + verb - To have been (verb in present participle) for (amount of time)

[Literally means, it makes it (amount of time) that -]

Por Ejemplos

Hace tres semanas que me duele la mano - My hand has been hurting me for three weeks.

Other

 * hacer caso to pay attention

title: Spanish/Expressions/Hacer


text:
Talk:Chinese (Mandarin)/Greetings

幸会 Nice to meet you! <>

(Note: I edited the post above by marking up the language using appropriate XHTML code.)

Untitled
I edited the article by adding  and   attributes to mark the Chinese.

The article also needs some other adjustments: Reversed (talk) 10:46, 28 January 2009 (UTC)
 * The ideographic text can be further clarified by defining the ISO 15924 script codes  (Simplified Chinese) or   (Traditional Chinese).
 * QUOTATION MARK (") characters should be switched to LEFT DOUBLE QUOTATION MARK (”) and RIGHT DOUBLE QUOTATION MARK (”) characters.
 * The article needs to be organized into something more resembling dictionary form. That is, the Chinese and commentary need to be clearly and consistently separated.
 * The article needs to use actual sentences.

title: Talk:Chinese (Mandarin)/Greetings


text:
User:Whiteknight/PIC Assembly

This outline will serve to implement a book about PIC Assembly. --Whiteknight (talk) (projects) 00:47, 30 May 2006 (UTC)

Preface
This page is going to discuss programming PIC microcontrollers using the PIC assembly language.

Table of Contents

 * Introduction

Section 1: PIC Introduction

 * PIC Architecture
 * PIC Family
 * PIC Details

Section 2: PIC Instruction Set

 * PIC Instructions
 * Arithmetic Instructions
 * Memory Instructions
 * Control Flow Instructions

Section 3: PIC Programming

 * PIC Assemblers
 * PIC Emulators
 * Macros
 * PIC Programming in C

Section 4: Advanced PIC

 * Interrupts
 * PIC I/O
 * Watchdog Timer
 * Interrupt Timers (prescalers)
 * Configuration (OPTION register, configuration registers)

Section 5: Additional Material

 * Sleep Mode
 * System Clock
 * ADC converters
 * DAC converters
 * Serial I/O

title: User:Whiteknight/PIC Assembly


text:
Spanish/Vocabulary/Outdoors

= Accidentes geográficos (Landforms) =
 *  el acantilado  :  cliff
 *  el archipiélago  :  archipelago
 *  la bahía  :  bay
 *  el cabo  :  cape
 *  la cordillera  :  mountain range
 *  la cuesta  :  cuesta (hill/ridge)
 *  el desfiladero  :  defile (gorge/pass)
 *  la ensenada  :  cove
 *  el estrecho  :  strait
 *  el estuario  :  river estuary
 *  el golfo  :  gulf
 *  la isla  :  island
 *  el istmo  :  isthmus
 *  el lago  :  lake
 *  la llanura  :  prairie
 *  el macizo  :  mountain mass
 *  el mar  :  sea
 *  la mesa  :  mesa (tableland)
 *  la meseta  :  plateau
 *  el océano  :  ocean
 *  la península  :  peninsula
 *  el piedemonte  :  foothill
 *  la planicie  :  plain
 *  el río  :  river
 *  el valle  :  valley

El Césped (The Lawn)

 * el árbol - the tree
 * el arbusto - the bush; the shrub
 * el césped - the grass
 * la cortadora de césped - the lawn mower
 * cortar la hierba/el césped - to mow; to cut the grass
 * la hoja - the leaf
 * la piedra - the stone

El Jardín (The Garden)

 * la flor - the flower
 * la hierba - the herb
 * la planta - the plant

Las flores (The Flowers)

 * el tulipán - the tulip
 * el pensamiento - the pansy
 * la rosa - the rose

El Cielo (The Sky)

 * el asteroide - the asteroid
 * el cometa - the comet
 * la estrella - the star
 * la luna - the moon
 * la nube - the cloud
 * el satélite - the satellite

El Lago (The Lake)

 * el agua - the water
 * el barco - the boat
 * la costa - the coast
 * la paleta - the paddle
 * el pez - the fish

title: Spanish/Vocabulary/Outdoors


text:
MIPS Assembly/Subroutines

This page is going to talk about using subroutine structures in MIPS Assembly. Also, this page will talk about some of the common methods by which higher-level language constructs and subroutines are translated into MIPS assembly code.

Subroutine Mechanics
In MIPS, the general purpose registers are typically taken to be the function parameters and the function variables, as needed. Previous values of the general purpose registers are stored on the stack. At the end of a subroutine, the values of all registers stored in this manner are restored from the stack.

MIPS uses the stack to preserve these registers. The stack pointer points to the bottom of the stack, but the frame pointer points to the top of the local frame. Offsetting from the stack or frame pointers can retrieve the various saved values and function parameters, as needed.

Stem and Leaf
In the function hierarchy, a function that calls other functions is known as a stem function. A function which calls no other functions is known as a leaf function. Stem functions must save the value of $ra on the stack, so that its content is preserved across the other function calls, and so the called function can return to the calling function, or its parent function.

It is important to note that a leaf function does not need to preserve the value of the $ra register because it does not call any other child function and hence its return address is preserved in $ra.

Stack Frame
A function may set up a stack frame, with the $sp register pointing to the bottom of the stack, and the $fp register pointing to the top of the stack at the start of the subroutine. In this manner, $fp will be pointing to the function's input arguments (if any are on the stack), and $sp will be pointing to the local variables for the function.

The value of $fp needs to be preserved across function calls, and stem functions need to save the value of $fp before calling a child function, and restore it from the stack after calling the child function.

The value of $sp does not need to be stored on the stack, but functions need to take care to return $sp to the value it had at the beginning of the function, before the function returns. This means that at the beginning of a subroutine, values can be pushed onto the stack, and at the end of the subroutine, all those values need to be popped right back off the stack. If this is not done correctly, it will destroy the stack frame of the parent function, and possibly cause the computer to crash.

Saved Registers
There are a number of registers that must be preserved across a subroutine call. This means that if the subroutine wants to use those registers, it must save the previous values onto the stack (or some other place), and then reload those values at the end of the function. The $tx registers are all temporary registers and do not need to be saved. Likewise, the $ax registers are all function arguments, and do not need to be saved. Thr $v0 and $v1 registers are both function return values, and do not need to be saved.

The following registers do need to be preserved across a function call, and should be saved by the function if they are going to be used in the function:
 * $sx:The "Saved Temporary" registers

title: MIPS Assembly/Subroutines


text:
MIPS Assembly/Programming Style

This page is going to talk about programming style and code formatting techniques in MIPS Assembly. Programming style is an arbitrary construct that is dependent on the individual programmer, but this page will show some common styles anyway.

Good, consistent programming style for assembly languages in general is arguably more important than for higher-level languages, as you don't have the luxury of abstracting even the simplest of operations away. For that reason, comments are even more important than in higher-level languages! The necessity of dealing with the nitty-gritty means your program will grow in lines of code very quickly, and someone's going to have to read it. Why not make their life easier?

There are several styles and conventions one may adhere to. Doesn't matter too much which one you use, but be consistent!

title: MIPS Assembly/Programming Style


text:
Template:SPARC Assembly/Page

 SPARC Assembly

title: Template:SPARC Assembly/Page


text:
SPARC Assembly/SPARC Architecture

SPARC History
The first version of the architecture, SPARCv7 (for Scalable Processor Architecture, version 7), was originally developed by Sun Microsystems in 1986 ; the first implementation became available in 1987. In 1989, SPARC International, an independent, non-profit organization, was created to promote the SPARC and provide conformance testing. Implementations of the original 32-bit SPARC architecture were initially designed and used for Sun's workstation and server systems, replacing their earlier Sun-3 systems based on the  family of processors. Later, SPARC processors were used in SMP servers produced by Sun Microsystems, Solbourne and Fujitsu, among others.

A new version, SPARCv8, was released in 1990. It added integer multiply and divide instructions, which weren't previously available, and quad-precision floating point numbers, encoded on 128 bits.

The specification of the first 64-bit version of the SPARC, SPARCv9, was published in 1994, and Sun and Fujitsu both started shipping SPARCv9 processors at the end of 1995.

SPARC International (http://sparc.org) was formed in 1989 to open up the SPARC architecture to make a larger ecosystem for the design. The architecture is freely licensable for a nominal fee. SPARC processors have been designed and produced by several manufacturers, including Texas Instruments, Atmel, Cypress Semiconductor, and Fujitsu. As a result of SPARC International, the SPARC architecture is fully open and non-proprietary.

SPARC Architecture
The SPARC is of the Reduced Instruction Set Computing (RISC) architecture. The theory is that having the bare minimum of instructions needed to complete a job, the resulting architecture is faster, as most instructions take only one clock cycle to decode, leading to rapid execution. This is in contrast to CISC machines, which have specialized variable length instructions, and can take multiple clock cycles to decode and execute.

The SPARC architecture also prefetches instructions, having the next instruction fetched while the current one is executed. This has implication for branch instructions, as the next instruction might not be executed if the branch is taken, and this must be dealt with accordingly.

Why SPARC?
Being a RISC architecture, SPARC assembly is very clean and simple, while still being powerful. This makes it easy to learn, and a good choice before learning more complicated assembly languages if needed. Furthermore, it provides a closer look of what is going on "under the hood" of higher-level programming languages, and at the very least should foster an appreciation of the large amount of work being done by compilers when compiling such languages. If you don't have a SPARC computer, you can use a SPARC emulator.

title: SPARC Assembly/SPARC Architecture


text:
SPARC Assembly/SPARC Processors

This page is going to list, and discuss some of the computer systems in the SPARC processor family.

title: SPARC Assembly/SPARC Processors


text:
SPARC Assembly/SPARC Details

Registers
SPARC processors have 32 integer registers. These registers are broken down into 4 basic categories: globals, locals, inputs, and outputs. The table below shows the general breakdown:

Dispersed throughout these categories are several special purpose registers:

As you can see from the above tables, each register has at least two names, and some of the special purpose registers have three. Any of the available names for a given register is perfectly acceptable regardless of the usage context, and it is up to the programmer to choose which names to use at any particular time. Additionally, using the stack and frame pointer registers in a way other than which they were intended is not recommended and can cause severe functionality issues within a program.

SPARC processors also contain an array of floating-point registers and a small number of special-purpose registers. (further description needed here)

Delayed Branch
SPARC processors are pipelined, and branching is accomplished through a technique called Delayed Branch Execution. Control Transfer Intructions (CTI) are any instruction that changes the current program counter. For instance, a jmp or call instruction are CTI instructions.

In SPARC, when a CTI instruction is executed, the jump is not handled immediately. Instead, there is a one cycle delay before the branch is executed. This means that the first instruction after the jump instruction is actually handled before the jump takes place. Here is an example:

add %r3, %r2, %r5 jmp SetR5ToZero add %r4, %r5, %r2

Notice that the last instruction executes before the jump takes place, not after the subroutine returns. This first instruction after a jump is called a delay slot. It is common practice to fill the delay slot with a special operation that performs no task, called a no-operation, or nop.

This instruction performs no action, and therefore we don't need to worry about what order it acts in. However, if we put a nop after every branch instruction, we will waste a lot of processor cycles. Therefore, if you can, it is always good practice to try to squeeze additional instructions into the delay slot, so that we don't waste any processor cycles.

title: SPARC Assembly/SPARC Details


text: Template:SPARC Assembly/Instruction

title: Template:SPARC Assembly/Instruction


text:
Template talk:SPARC Assembly/Instruction

This template is used primarily in the SPARC Assembly book, to display the various SPARC assembly instructions in a succinct and standardized format.


text:
SPARC Assembly/SPARC Instructions

Instruction Format
Here is a quick-rundown of the arithmetic instruction format, when writing your SPARC code:

 * mnemonic %rsrcA, srcB, %rdest

The instruction mnemonic (commonly, but inaccurately, also referred to as the "opcode") specifies the type of operation to be performed. rsrcA is the first operand, while srcB is the second. rsrcA must be a register, and srcB can usually be a signed immediate (13 bit) constant or a second register. rdest is the destination register, and not all instructions have one (for example: cmp for compare).

Note that in SPARC assembly language, instructions always read from left to right. The left (and middle, if present) operands are source operands. If the operation writes a result anywhere (as almost all operations do), the result is written to the rightmost operand (destination register or destination memory location).

In SPARC assembly language, the following instructions are completely valid:

add %r3, %r4, %r5

add %r3, 16, %r5

 * The first instruction adds register 3 and register 4, and places the result in register 5.
 * The second instruction adds register 3, and the number 16, and places the result in register 5.

As you can see, SPARC assembly places a % sign before each register name, while numeric literals are written normally.

Warning: This syntax is backwards from Intel syntax (used in PPC chips, and some compilers).

It should also be noted that many SPARC instructions such as the logic and arithmetic instructions have a version of each instruction with "cc" appended to the end of the mnemonic. These instructions perform the same function as their non-"cc" counterpart, but also set condition codes (more on these later) that can be used to regulate branching within a program. For example, the "add" instruction mentioned above has a counterpart "addcc", which when performing an addition sets specific condition codes that later branch instructions check when deciding whether or not to branch to another part of the program.

Comments
Comments will not be read by the compiler, and are indicated with an exclamation point. Anything following the exclamation point on that line will be ignored. Comments help you understand what you are doing, and why you are doing it. The following is a bad example of commenting: sub %l0, %l3, %g1 ! Subtract local register 3 from l0, and put the result in global 1. ! add %g1, %l4, %g1! We should add in local 4, but I'm not doing that yet We can easily tell what we are doing; the code says that. The comments have told us nothing.

However this is better: sub %l0, %l3, %g1 ! Subtract our monthly expenses from our monthly income. !   This will later be used in function _foo. ! add %g1, %l4, %g1! Local 4 will hold "other" sources of income, but we're not there yet. Now we know what we're doing (we're figuring spare change for the month), and why we're doing it (function foo will apparently use this). Also, note that the second line in both examples will not be executed as their instructions have been commented out (apparently to be implemented later).

Do note that many people comment almost every single line of code in assembly, due to the fact that it can sometimes be difficult to tell what's going on without useful things like variable names, complex structures, etc.

Labels
Labels are indicated by placing a "label_name:" at some point in your code. As labels are just areas that give the compiler addresses, they can be used for anything that's stored directly in the program: most popularly, these are used for function jumps (via branch or call statements), or ways to reference constant variables. If it is a function, and not a jump, ".global" must be placed before it. There is one special label/global, just like every language, and that is the "main" label, which is where the program starts.

.global main main:  save %sp, -64, %sp mov 5, %l0 cmp %l0, 5 be,a end ta 1 ! Should NEVER happen end:   mov 1, %g1 ta 0

In this program are a bunch of things that might not be understandable, but this is a full program. It starts at the main function (defined by ".global main, followed by the label). It then copies the value "5" into a local register, and then compares that register to the value of "5".  If they are equal, it branches to the label end, where the program then exits.

title: SPARC Assembly/SPARC Instructions


text:
SPARC Assembly/Arithmetic Instructions

Arithmetic Instructions
These are the basic operations used for addition, subtraction, and multiplication. Note that any of these arithmetic instructions may take a register or an immediate value as the op2 parameter. All other parameters (rd and rs1 must be registers).

Adds rs1 and op2, and stores result in rd.

Same as above, except that it sets the condition codes.

subtracts op2 from rs1, and stores the difference in rd

same as above, except that it sets the condition codes.

Performs a single step in the multiplication operation. Stores partial results in register Y. Complete multiplication algorithms are discussed in more detail later.

Extended Precision
These instructions account for the carry bit setting, so that large numbers (larger then the machine word) can be virtually manipulated as a single entity.

Performs extended addition (adds two operands and carry bit), and stores result in rd.

Same as above, but sets the condition codes.

Performs extended subtractions (subtracts op2 and C from rs1) and stores result in rd.

same as above, but sets the condition codes.

Y Register
These operations affect the Y register.

reads the contents of the Y register in to the rd destination register

exclusively ORs the rs1 and op2 values, and stores that result in the Y register.

Logic Instructions
performs the bitwise AND of rs1 and op2, and stores the result in rd.

same as above, sets the condition codes.

performs the bitwise OR of rs1 and op2, and stores the result in rd.

same as above, sets the condition codes.

performs the bitwise XOR, between rs1 and op2. stores the result in rd.

same as above, sets the condition codes.

performs the bitwise XNOR between rs1 and op2. puts result in rd.

same as above, sets condition codes.

Inverted Logic Operations
ANDs rs1 and the bitwise inverse of op2. stores result in rd.

same as above, sets condition codes.

ORs rs1 and the bitwise inverse of op2. stores the result in rd.

same as above, sets the condition codes.

Shift Instructions
performs the logical left-shift of rs1. Shift amount is according to value of op2. result is stored in rd.

performs the logical right-shift of rs1. Shift amount is the value of op2. stores the result into rd.

performs the arithmetic right-shft of rs1. shift amount is the value of op2. stores the result in rd.

title: SPARC Assembly/Arithmetic Instructions


text:
SPARC Assembly/Memory Instructions

Instruction Format
This is going to be a quick primer for how to write these memory instructions.

Load Instruction Format
Memory instructions load a value from memory, or store a value into memory. The target address is computed as the addition of a base value with an optional offset value.

For example:

ld [%r4 + 10], %r5

loads the register %r5 with the value in memory located at [%r4 + 10]. If %r4 contains the number 25, then the memory location read would be [25 + 10] = 35. The op2 parameter, like the arithmetic instructions can be a register or an immediate. This means that the following are both valid:

ld [%r4 + %r3], %r5

ld [%r4 + 100], %r5

The offset value is the number of bytes offset, not the number of machine words or halfwords. This means that to load consecutive words on a 32 bit machine, the offset needs to be incremented by 4:

ld [%r4 + 4], %r5 ld [%r4 + 8], %r6 ...

Also, the offset value is optional. If the offset is omitted, the assembler will assume a value of 0. For example:

ld [%r4], %r5

will read from location %r4, with no offset.

Store Instruction Format
Store instructions are similar to load instructions, except that the operands are reversed. This means that we have the following instruction format:

st rd, [rs1 + op2]

All the rest of the above material applies.

Load Instructions
Loads an unsigned byte from memory into rd.

loads a signed byte from memory into rd. sign-extends result.

loads an unsigned halfword from memory into rd.

loads a signed halfword from memory into rd. Sign extends result.

loads a machine word into rd.

Loads a double word into 2 consecutive registers.

Store Instructions
Stores a byte from register rd into memory.

stores a halfword from register rd into memory.

stores a machine word from register rd into memory.

stores a double value from two consecutive registers into memory.

Swap Instruction
performs a simultaneous load and store operation, which effectively swaps the value in memory with the value in rd. Is formatted like a load instruction, for example:

swap [%r3 + 4], %r5

title: SPARC Assembly/Memory Instructions


text:
SPARC Assembly/Control Flow

Comparison
compares two numbers (Subtraction). Sets flags.

tests two numbers (performs 'and' operation). Sets flags.

Jump Instructions
jumps to specified indirect address. stores return address in %o7.

Performs an unconditional, register indirect jump. Target address is provided in the first operand, and the return address is then stored into the rd operand.

jmpl rs1, rd

If the return address is stored in %o7, this acts like a subroutine call. If the return address is stored in %g0, it acts like a subroutine return.

Sets the highest 22 bits of the target register, sets the lowest 10 bits to zero.

sethi const22, rd

const22 must be a constant value, cannot be a register.

Subroutine Instructions
calls a subroutine. Takes a single label as a new target address. Stores the return address in %o7. cannot jump to a register indirect address.

return from a subroutine.

return from a leaf subroutine.

Return from a trap instruction, or from a register indirect control transfer.

saves the current register window and creates a new window. raises an exception if there is a register window overflow.

restores a saved register window.

Branch Instructions
branches do not store the return address.

Branch always. an unconditional jump to the target location. d

Branch never.

branches if the two operands are equal or not equal, respectively.

branches on "less than"

branches on "less than or equal"

branches on "greater than or equal"

branches on "greater than"

Same as bl and ble, except uses unsigned numbers

Same as bge and bg, except uses unsigned numbers

branches if the number is positive.

branches if the number is negative.

branches if the carry bit is set or clear, respectively.

branches if the signed overflow bit is set or clear, respectively.

title: SPARC Assembly/Control Flow


text: SPARC Assembly/Floating Point

title: SPARC Assembly/Floating Point


text:
SPARC Assembly/SPARC Assemblers

This page is going to discuss some assemblers for programming SPARC Assembly.

title: SPARC Assembly/SPARC Assemblers


text:
SPARC Assembly/SPARC Emulators

One possible solution is to use QuickTransit from Transitive, which allows SPARC binaries to execute on Solaris/x86, Linux/x86 or Linux/Itanium systems. It can be downloaded from the Transitive Web site at: http://www.transitive.com/evaluate. Unfortunately, IBM has acquired Transitive and is no longer selling Transitive, instead integrating it into their PowerVM product. Whether Transitive will be available as a stand-alone emulator in the future or not is yet to be seen.

Another option is QEMU. QEMU supports several SPARC platforms and is capable of booting operating systems NetBSD for example which still actively supports both 32 bit and 64 SPARC. Sources for QEMU can be found at the QEMU Wiki. Or install it via your native packaging system precompiled binaries of recent versions of QEMU are available for windows at this site: http://lassauge.free.fr/qemu/.

title: SPARC Assembly/SPARC Emulators


text:
SPARC Assembly/Subroutines

This page is going to discuss the use of subroutines in SPARC Assembly.

Subroutine Linkage
A typical (non-leaf) subroutine has a procedure prologue and epilogue something like this:

title: SPARC Assembly/Subroutines


text: SPARC Assembly/Memory Management

title: SPARC Assembly/Memory Management


text: SPARC Assembly/Instruction Formats

title: SPARC Assembly/Instruction Formats


text: SPARC Assembly/Traps and Exceptions

title: SPARC Assembly/Traps and Exceptions


text:
SPARC Assembly/Ultra SPARC

This page is going to discuss the upgrades in Ultra SPARC, and will discuss some issues thereof.

The UltraSPARC processors were designed by Sun Microsystems and implement the SPARC version 9 (sparcv9) architecture. This architecture natively supports 64 bit processing by extending the virtual address space to 64 bits and widening the general purpose registers to 64 bits.

title: SPARC Assembly/Ultra SPARC


text:
Floating Point

This wikibook discusses the IEEE 754 standard concerning floating-point numbers. Beginning chapters of this book focus on newcomers to the standard, who wish to understand and make use of floating point numbers, especially in a programming project. Later chapters of this book, however, focus more on the details of implementation of the IEEE 754 standard. This way, advanced users who want more details, or users who are working to create a floating-point implementation of their own can find the information they need. This book can be used as an ancillary reference source to support other books in the computer science and engineering fields.

Programming examples found in this book attempt to use pseudocode where possible, to prevent an over-reliance on any particular language or platform. Specific examples may utilize a single computer language or assembly language.

Prerequisites to this book include an understanding of exponents and Algebra, and an understanding of binary number representation.

Section 1: Number Representation

 * /Introduction/
 * /Scientific Notation/
 * /Fixed-Point Numbers/
 * /Floating-Point Numbers/

Section 2: IEEE 754

 * /IEEE 754/
 * /Floating Point Formats/
 * /Special Numbers/
 * /Normalization/

Section 3: Floating Point Arithmetic

 * /Rounding/
 * /Floating Point Arithmetic/
 * /Epsilon/
 * /Arithmetic Errors/
 * Guard Bits
 * /Comparing FP Numbers/

Section 4: Floating Point Hardware

 * Converting FP and Integers
 * Exceptions
 * Trap Handlers
 * Flags
 * /Floating Point Hardware/
 * /Soft Implementations/

Section 5: Algorithms

 * Arithmetic Algorithms
 * Exponents and Square Roots
 * Trancendentals

title: Floating Point


text:
User:SEWilco

I am User:SEWilco on en:Wikipedia.

title: User:SEWilco


text:
Cookbook:Shirmal (Persian Saffron Flatbread)

| Cuisine of India | Cuisine of Pakistan

Shirmal, also sheermal, is a traditional flatbread made in Pakistan and in the Hyderabad region of India, probably from Persian influences.

Ingredients

 * A few saffron strands
 * 2 tbsp warm milk
 * 3 cups plain flour
 * Salt to taste
 * 1 tsp sugar
 * ¾ cup ghee
 * 1 cup milk

Procedure

 * 1) Soak the saffron strands in the warm milk. Set aside.
 * 2) Sift together flour and salt, then sprinkle in sugar.
 * 3) Add the melted ghee, and mix with your fingers until evenly distributed.
 * 4) Add milk a little at a time, and knead the mixture to a dough. When it forms a soft smooth lump, cover with a moist cloth and set aside for 2 hours.
 * 5) Knead, then set aside again for 2 hours.
 * 6) Knead again, and divide the dough into 7 parts.
 * 7) Rub saffron strands in the milk to dissolve them.
 * 8) Place an inverted heavy iron pan on the lower shelf of oven. Keep the grill on upper rack. Preheat to 250°C (480°F).
 * 9) On a floured surface, roll each piece of dough into a thick round about 6 inches in diameter. Prick with fork all over.
 * 10) Slap dough onto the hot pan base, and allow to bake until brown spots appear.
 * 11) Move sheermal to the grill with tongs. Dip fingers in saffron milk and splash on sheermal. Keep in oven few more seconds.
 * 12) Remove sheermal, and either immediately serve hot or wrap in slightly moist towel.
 * 13) Apply butter or ghee on top if desired. Serve with gravies, veggies, curds, pickles or jams.

Notes, tips, and variations

 * You can also bake the shirmal in a traditional tandoor or in inverted pressure cooker.


text:
Cookbook talk:Shirmal (Persian Saffron Flatbread)

* (cur) (last) 19:41, 7 May 2006 Salmaakbar
 * (cur) (last) 20:24, 7 May 2006 Bayyoc [rollback] [proxycheck]


text: Talk:Guide to Unix/Solaris

title: Talk:Guide to Unix/Solaris


text:
Transwiki:Special product and factoring

Donna Grace Matti BSIT-C22 MATH110         jULY 23, 2008

BINOMIAL SQUARE 1. Square the 1st term

2. Twice the Product of the two terms

3. Square the last term PRODUCT OF SUM AND DIFFERENCE

1.square the 1st term

2.square the last term

3.Place the minus sign between the two terms SQUARING A TRINOMIAL/ TRINOMIAL SQUARE

1.Square the 1st term =

2.Square the 2nd term

3.Square the 3rd term

4.Twice the product of the 1st and 2nd terms

5.Twice the product of the 1st and 3rd terms

6.Twice the product of the second and third terms CUBE OF BINOMIAL

1.Cube the 1st term

2.Three times the product of the square of 1st term and the last

3.Three times the product of the 1st term and square of the last term

4.Cube the last term MONOMIAL FACTORS OF POLYNOMIAL/ FACTORING MONOMIALS

1.Find The GCF

2.Divide the terms by the GCF

3.Distribute the GCF to the answer

 * IN GETTING THE GCF GET THE LOWEST EXPONENT, AND THE LOWEST NUMERICAL COEFFICIENT [IT MUST BE STILL BE DIVISIBLE TO THE OTHER NUMERICAL COEFFECIENT] THEN GET THE LITERAL COEFFICIENT THAT IS PRESENT IN ALL TERMS)

DIFFERENCE OF TWO SQUARES

(SQUARE ROOT MEANS A NUMBER THAT IF U MULTIPLY TO ITSELF THE PARTICULAR NUMBER WILL APPEAR LIKE 25 THE SQUARE ROOT IS 5 BECAUSE 5(5)= 25 1.find the square root of the 1st term

2.find the square root of the 2nd term 3.Form two binomial using the roots w/ plus and minus as its operators

SUM & DIFFERENCE OF CUBE 1.find the cube root of the 1st term

2.find the cube root of the 2nd term

3.form a binomial using the roots and copy the operation

4.Using the binomial obtained, square the 1st term.

5.Multiply the 1st and the last term

6.square the last term

 * IF THE 1ST BINOMIAL IS POSITIVE THE 2ND IS NEGATIVE THE LAST TERM OF THE 2ND BINOMIAL IS ALWAYS POSITIVE

FACTORING BINOMIAL

1.Determine the square root of the 1st term

2.Find the square root of the last term

3.copy the sign/operation of the middle term

VERIFICATION

Divide the middle by 2

FACTORING TRINOMIAL SQUARE

1.Get the Factor of the last term the factor you must get is that if you add it the 2nd term numerical coefficient will appear

FACTORING QUADRATIC TRINOMIAL

1.find the pair factor of the 1st and last term

2.formulate the 2 binomial using the pair factor

3.Verify using multiplication then add the product of O AND I ( multiply both outer and inner)

title: Transwiki:Special product and factoring


text:
Transwiki talk:Special product and factoring

* (cur) (last) 18:41, 3 February 2006 Sayama * (cur) (last) 11:51, 15 January 2006 RHaworth * (cur) (last) 11:50, 15 January 2006 RHaworth m (moved Special pruduct and factoring to Special product and factoring) * (cur) (last) 19:45, 14 January 2006 Sayama * (cur) (last) 19:38, 14 January 2006 Sayama * (cur) (last) 19:35, 14 January 2006 Sayama
 * (cur) (last) 00:51, 4 April 2006 Pearle m (Changing wikify to wikify-date|February 2006) [rollback] [proxycheck]


text:
Cookbook:Sydney Smith's Salad Dressing

Sydney Smith's salad dressing is a type of salad dressing. The recipe originated from Sydney Smith who founded the Edinburgh Review, and it was popular in the 19th century among American cooks.

Ingredients

 * 2 boiled potatoes
 * 1 spoonful mustard
 * 2 spoonfuls salt
 * 4 spoonfuls olive oil
 * 2 spoonfuls vinegar
 * 2 hard-boiled egg yolks, mashed
 * Small amount of minced onions
 * 1 spoonful anchovy sauce

Procedure

 * 1) Pass the potatoes through a sieve or a ricer.
 * 2) Combine potatoes and remaining ingredients. Mix well.

title: Cookbook:Sydney Smith's Salad Dressing


text:
Cookbook talk:Sydney Smith's Salad Dressing

* (cur) (last) 20:58, 12 January 2006 Mitsukai (disambiguation link repair (You can help!)) * (cur) (last) 12:36, 11 December 2005 Johnleemk (rm afd tag) * (cur) (last) 10:59, 4 December 2005 Bk0 (AfD) * (cur) (last) 05:09, 11 July 2005 Sysin * (cur) (last) 14:14, 23 June 2005 Taxman (might as well link the ingredients) * (cur) (last) 05:17, 20 June 2005 HappyCamper m (spelling - mustart --> mustard) * (cur) (last) 19:57, 19 June 2005 HappyCamper m (spelling - should be "Edinburgh Review") * (cur) (last) 19:51, 19 June 2005 HappyCamper (poem for Sydney Smith's salad dressing, to complement list of foods named after people)
 * (cur) (last) 10:35, 19 January 2006 Garion96 (move to cookbook tag) [rollback] [proxycheck]

Salad or dressing?
It is unclear if this is a dressing or the salad? what is thsi dressing put on? {{unsigned|67.181.105.114|2007-02-20T07:35:24}

 * It's a dressing. The potato is forced through a sieve and thickens the dressing. Webaware talk 22:20, 19 February 2007 (UTC)


text:
Bartending/Tiki Bar TV recipes

The podcast "Tiki Bar TV" has created a series of themed drinks.

Episode 1 - Margaritaville
Jimmy Buffett Classic Margarita
 * Fill shaker with broken ice cubes
 * Squeeze 2 fresh lime wedges into shaker
 * 2 oz gold Tequila
 * ½ oz White Tequila
 * 1¼ oz Lime Cordial
 * ½ oz Triple Sec
 * A splash of Orange Curaçao
 * Shake vigorously
 * Rim outside of glass with lime peel
 * Salt outside rim only
 * Add fresh ice
 * Squeeze one more lime wedge and drop in

Episode 2 - Suffering Bastard

 * 1½ oz Gin
 * ½ oz Bourbon
 * 3 oz Gingerale
 * ½ Lime
 * Sprig of Mint

Episode 3 - The Trap Door

 * 1 oz Gin
 * 1 oz Spiced Rum
 * ½ Fresh Lime
 * 2 oz Fresh Orange Juice
 * 1 oz Soda

Episode 4 - Hulla-Balloo

 * 2 oz Brandy
 * 2 oz Scotch
 * 5 oz Fresh Lemonade

Episode 5 - Trader Woody

 * 2 oz Dark Rum
 * 1 oz Amaretto
 * 1 oz Pineapple Juice
 * 1 oz Orange Juice
 * Couple splashes of Lime Juice

Serve over crushed ice

Episode 6 - Interlude

 * Drink Newfoundland Screech

Red Orchid

 * 1 Dark Rum
 * 1 Chambord
 * Dash of Grenadine
 * Dash of Cranberry

Banana Slam

 * 1 Gold Rum
 * 1 Banana Liqueur
 * ½ Orange Juice
 * ¼ Sour mix

Episode 8 - London Fogcutter

 * 2 oz Gin
 * 1 oz Lime Juice
 * 6 oz Champagne

Serve on ice

Episode 9 - Red Oktober

 * 2 oz Cherry Brandy
 * 1 oz Orange Vodka
 * 1 tbsp 151 Rum
 * Fill rest with soda
 * Garnish with cherry

Episode 10 - Drinkbot
Love in the South Pacific
 * 1 oz White Rum
 * 1 oz Southern Comfort
 * ½ oz Crème de Bananes
 * ½ oz Triple Sec
 * ½ oz Sloe Gin
 * ½ oz Vodka
 * 4 oz Orange Juice
 * Shake & Pour over Ice
 * Fill Rest with Soda
 * Garnish with Love

Episode 11 - Volcano

 * 3 oz Demerara Rum
 * 2 oz Gold Rum
 * 1 oz Cuban Rum or Puerto Rican Gold Rum
 * 151 for flame
 * 6 oz Grapefruit
 * 2 oz Fresh Squeezed Lime
 * ¾ oz grade A/1 maple syrup
 * ½ oz simple syrup

Served in a Volcano bowl.

Episode 13 - Skull & Bones
In a blender mix:
 * 1 peeled banana
 * 1 cup milk
 * 2 oz pineapple juice
 * 1 oz gold rum
 * 2 oz sloe gin
 * ½ oz 151 rum
 * dash of bitters

Episode 14 - Boomerang

 * 2 oz Gold Rum
 * 1 oz Melon Liqueur
 * 1 oz Lychee Juice
 * 2 oz Guava Juice
 * 2 oz Orange Juice
 * 2 oz Mango Juice
 * ¼ Fresh Lime

Episode 15 - Legal Ease
Out-Of-Court Settlement
 * 2 oz Lemon Liquor
 * 2 oz Cranberry Juice
 * 2 oz Rye
 * 2 oz Club Soda
 * ½ a fresh lime

Episode 16 - Tongue Twister

 * ½ oz Light Rum
 * ½ oz Tequila
 * ½ oz Vodka
 * 1 oz Coconut Cream
 * 1 Drop Grenadine
 * 3 oz Pineapple Juice
 * 2 tbsp Milk

Episode 17 - Space Cadet
Newton's Apple
 * 1 oz of Amaretto
 * 1 oz of Apple Liqueur
 * ¾ oz of Lime cordial
 * 1 oz of Triple Sec
 * 1 oz of Vodka

Episode 18 - Greeki Tiki
Ouzo Cocktail

Alpha
 * 1 oz Ouzo
 * 1 oz Vodka
 * 2 oz Orange Juice
 * ½ Fresh Lemon

Beta
 * 1 oz Brandy
 * 1 oz Bourbon
 * ½ oz Ouzo
 * 1 oz Vodka
 * 1 oz Orange Juice
 * 2 oz Lemon-lime soda

Gamma
 * ½ oz Ouzo
 * ½ oz Vodka
 * 1 oz Cassis
 * 3 oz Lemon-lime soda

Episode 20 - Son of the Internet
Short Fuse

Pint
 * 8 oz Beer
 * 4 oz Cola
 * ½ oz Cherry Brandy

Shot
 * 1 oz Coffee Liqueur
 * 1 oz Amaretto

Episode 21 - Snake
Forbidden Serpent
 * 1 oz Lime Juice
 * 2 oz Orange Juice
 * 2 oz Pineapple Juice
 * 2½ oz White Rum
 * 1 oz Dark Rum
 * ½ oz Apricot Brandy
 * ½ oz Peach Schnapps

Episode 22 - Dry Halloween
Pumpkin Rum Punch
 * 1 Part rum
 * 1 Part Cider
 * 2 Parts Ginger Ale

Served in a hollowed pumpkin with floating pumpkin bits.

Episode 23 - Red Handed
Diplomatic Immunity
 * 1 oz Scotch Whiskey
 * ½ oz Apricot Brandy
 * ½ oz Orange Curaçao
 * 3 oz Pineapple Juice
 * ¾ oz Fresh Lime Juice

Garnish with Cherry

Episode 25 – Blue Hawaiian

 * 3 oz Pineapple Juice
 * ½ oz Blue Curaçao
 * 1 oz Gold Rum
 * 1 oz Cream of Coconut or Coconut Syrup (not Coconut Cream)
 * Garnish with Lime Wedge

Episode 26 – Missionary
Missionary’s Downfall
 * 4 oz Ice
 * ⅓ Cup of Pineapple Chunks
 * 1 sprig of mint, leaves only
 * ½ oz Apricot Liqueur
 * ½ oz Simple Syrup
 * 1 oz Light Rum
 * 1½ oz Fresh Lime Juice
 * Blend until smooth

Episode 27 - Dingo
Dingo hunter
 * 1 oz Coffee Liqueur
 * 1 oz Irish Cream
 * 1 oz Crème de Cacao
 * 1 oz Tequila
 * 2 oz Milk
 * Blend with Ice

Episode 28 - The Play
Standing Ovation
 * 2 oz Bourbon
 * ½ oz Cherry Brandy
 * ¾ oz Fresh Lemon Juice
 * ½ oz Sugar Syrup

Garnish with cherry and lemon

Episode 29 - The Wedding
Wedding Cake
 * 1 oz Vanilla Vodka
 * ½ oz Light Crème de Cacao
 * ½ oz Hazelnut Liqueur
 * ½ oz Almond Liqueur
 * 1½ oz Milk
 * Blend with 6 ice cubes
 * Serve in bowl topped with whipped cream

Episode 30 - Ice Breaker
Ice Breaker
 * 1½ oz Vodka
 * ½ oz Cassis
 * 4 oz Energy Drink
 * 4 oz Pineapple Juice

Episode 31 - Casino
House Rules
 * 1 oz Barbados Rum
 * 1 oz Jamaican Rum
 * ½ oz Lime Juice
 * 1 tbsp maraschino cherry syrup
 * ½ oz unsweetened pineapple juice
 * Blend with 3 oz of ice

Episode 32 - Holiday Special
Tropical Blizzard
 * 1 oz Blue Curaçao
 * 1 oz Coconut Rum
 * ½ oz Apple Juice
 * 1½ oz Orange Juice

Episode 33 - CCCP
White Russian
 * 2 oz Vodka
 * 2 oz Milk
 * 1 oz Coffee Liquor
 * Sprinkle Nutmeg

Episode 34 - Mailbag's Revenge
Purple Emerald
 * 1 Part Black Currant Liqueur
 * 1 Part Vodka
 * 1 Part unsweetened grapefruit juice
 * Dash of Triple Sec

Episode 35 - Conspiracy
Brainwasher
 * 1 oz Coconut Rum
 * 1 oz 151 proof Rum
 * 5 oz Pineapple Juice
 * Splash of Triple Sec

Episode 36 - The Roman
Italian Lover
 * 1¼ oz Vodka
 * ¾ oz Campari
 * ¼ oz Limoncello
 * 1 oz Orange Juice
 * ¾ oz Sour mix

Episode 37 - Apocalypse Tiki
Kentucky Drought
 * 1 oz Peach Juice
 * ½ oz Lemon Juice
 * ¼ oz Triple Sec
 * ¼ oz Southern Comfort
 * 1½ oz Bourbon
 * ½ oz Simple Syrup

Episode 38 - Beatnik
Paradise Overdose
 * ½ oz Lime Juice
 * ½ oz Passion Fruit Juice
 * 1 oz Simple Syrup
 * 1 oz Grenadine
 * 2 oz Dark Rum
 * 1 oz Coconut or Spiced Rum
 * 4 Maraschino Cherry Ice cubes
 * Dash of Bitters

Garnish with Lime wedge

Tiki Bar TV Trailer
Chi Chi
 * 1½ oz Vodka
 * 4 oz Pineapple Juice
 * 1 oz Cream of Coconut
 * 1 slice Pineapple
 * 1 Cherry

Episode 40 - Drinkbot vs Robot Box
Duck and Cover
 * 1 oz Vodka
 * ½ oz Fireball
 * ½ oz Jågermeister

Episode 41 - Jump The Shark
Sea Legs
 * 1 oz White Rum
 * 1/2 oz Gold Rum
 * 1/2 oz Spiced Rum
 * 2 oz Pineapple/Coconut Juice
 * 2 oz Orange Juice
 * juice of 1/2 a lime

Episode 42 - Fishbone
Fishbone
 * 1 oz Melon Liqueur
 * 1 oz Blue Curaçao
 * 1 oz Coconut Rum
 * 2 oz Orange Juice
 * 2 oz Sour Mix
 * 1 oz Lemon-lime soda

Episode 43 - Ghost of Internet
Defibrillator
 * 3 oz orange juice
 * 1 oz Whiskey
 * 1 oz Vodka
 * 1 oz Beer
 * Stir, don't shake!

Episode 44 - Gypsy
Plot Hole
 * 2 oz Whiskey
 * 1 oz Sweet Vermouth
 * 1/4 oz Maraschino Cherry Juice
 * 2 oz Orange juice

Episode 45 - The Commodore
Jet Fuel
 * 2 oz Whiskey
 * 3/4 oz Dry Sack Sherry
 * 2 dashes Bitters
 * Squeeze orange slice into glass

title: Bartending/Tiki Bar TV recipes