| 1 |
| h02 |
| CS16 S18 |
| Name: | ||||
|---|---|---|---|---|
| (as it would appear on official course roster) | ||||
| Umail address: | @umail.ucsb.edu | section |
||
| Optional: name you wish to be called if different from name above. | ||||
| Optional: name of "homework buddy" (leaving this blank signifies "I worked alone" |
h02: Chapter 2: Variables and assignments, Input/output, Data types and expressions, Simple flow control
| ready? | assigned | due | points |
|---|---|---|---|
| true | Fri 04/06 09:00AM | Fri 04/13 11:59PM |
You may collaborate on this homework with AT MOST one person, an optional "homework buddy".
MAY ONLY BE TURNED IN IN THE LECTURE/LAB LISTED ABOVE AS THE DUE DATE,
OR IF APPLICABLE, SUBMITTED ON GRADESCOPE. There is NO MAKEUP for missed assignments;
in place of that, we drop the three lowest scores (if you have zeros, those are the three lowest scores.)
Please:
- No Staples.
- No Paperclips.
- No folded down corners.
Complete your reading of Chapter 1, section 1.3 pages 27-32, Chapter 2 sections 2.1 thru 2.2, pages 39-59 . You don’t need to turn this homework in. To earn credit for this homework, complete the corresponding quiz on gauchospace AFTER you have completed the pen and pencil version of the homework. The quiz will be available one day before the due date indicated on the homework.
-
1. (6 pts) The author describes the difference between "syntax errors" and "logic errors", and also the difference between syntax errors that produce an "error message" vs. those that produce a "warning message". Briefly explain each of the items below in a way that makes the DIFFERENCES among them clear:
i. Syntax errors that result in an error message:
ii. Syntax errors that result in an warning message:
iii. Logic errors:
2. (1 pt) If the following statement were in a C++ program, what would it do?
cout >> "I love oranges and apples";
3. (1 pt) If the following statement were in a C++ program, what would it do?
cout << "The world goes round and round"
4. (4 pts) Show 2 different ways to initialize variables in C++?
5. (2 pts) Is this variable declaration statement in C++ a good one? Why or why not?
double int=30;
auto x = 2.73;
#include <iostream>
int main(){
int a , sumPositive, sumNegative;
string promptContinue ="\nTo continue enter Y/y\n";
string promptNum = "\nEnter a number: ";
char response;
while (response = 'y'||`Y') {
cout << promptNum;
cin >> a;
if(a)
sumPositive+=a;
else
sumNegative+=a;
cout<< promptContinue;
}
cout<< "Sum of all the positive numbers is: "<< sumPositive<<endl;
cout<< "Sum of all the negative numbers is: "<< sumNegative<<endl;
return 0;
}
int x=20, y=5;
bool v, w;
v = (x != y);
w = ((x/=y) == 4);
cout << x << " " <<y << " "<< v << " "<< w << endl;


We buy networks!
- facilitate proactive portals
- incentivize extensible users
- unleash compelling networks
- engage seamless synergies
- unleash cutting-edge e-commerce
- innovate mission-critical functionalities
- unleash intuitive content
- engage wireless applications
- benchmark open-source ROI
- target vertical metrics
- synergize end-to-end partnerships
- morph cutting-edge networks
- incentivize holistic web services
- recontextualize 24/7 relationships
- harness real-time functionalities


|
| Local Properties | Local Methods | |
| Managed Object Types | Data Object Types | All Properties | All Methods |
Although datastores may often be implemented using a traditional file system, a full interface to a file system is not provided here. Instead, specialized access for virtual machine files is provided. A datastore implementation may completely hide the file directory structure.
The intent is to provide functionality analogous to a file chooser in a user interface.
Files on datastores do not have independent permissions through this API. Instead, the permissions for all the files on a datastore derive from the datastore object itself. It is not possible to change individual file permissions as the user browsing the datastore may not necessarily be a recognized user from the point of view of the host changing the permission. This occurs if the user browsing the datastore is doing so through the VirtualCenter management server.
The DatastoreBrowser provides many ways to customize a search for files. A search can be customized by specifying the types of files to be searched, search criteria specific to a file type, and the amount of detail about each file. The most basic queries only use file details and are efficient with limited side effects. For these queries, file metadata details can be optionally retrieved, but the files themselves are opened and their contents examined. As a result, these files are not necessarily validated.
More complicated queries can be formed by specifying the specific types of files to be searched, the parameters to filter for each type, and the desired level of detail about each file. This method of searching for files is convenient because it allows additional data about the virtual machine component to be retrieved. In addition, certain validation checks can be performed on matched files as an inherent part of the details collection process. However, gathering extra details or the use of type specific filters can sometimes only be implemented by examining the contents of a file. As a result, the use of these conveniences comes with the cost of additional latency in the request and possible side effects on the system as a whole.
The DatastoreBrowser is referenced from various objects, including from Datastore, ComputeResource, HostSystem and VirtualMachine. Depending on which object is used, there are different requirements for the accessibility of the browsed datastore from the host (or hosts) associated with the object:
Properties
| Name | Type | Description |
|---|---|---|
| datastore* P | ManagedObjectReference[]
to a Datastore[] |
Set of datastores that can be searched on this DatastoreBrowser.
The list of datastores available to browse on this DatastoreBrowser is contextual
information that depends on the object being browsed. If the host is being
browsed, the host's datastores are used. If the Datacenter is being browsed, the
Datacenter's list of datastores is used.
|
| supportedType* | FileQuery[] |
The list of supported file types. The supported file types are represented as
items in this list. For each supported file type, there is an object in the list
whose dynamic type is one of the types derived from the
FileQuery data object
type. In general, the properties in this query type are not set.
Use the Query of the desired file type in the SearchSpec.query to indicate the desired file types.
This property is used by clients to determine what kinds of file types are
supported. Clients should consult this list to avoid querying for types of virtual
machine components that are not supported.
|
Methods
| Methods defined in this Managed Object |
|---|
| DeleteFile, SearchDatastore_Task, SearchDatastoreSubFolders_Task |
Parameters
| Name | Type | Description |
|---|---|---|
| _this | ManagedObjectReference | A reference to the HostDatastoreBrowser used to make the method call. |
| datastorePath | xsd:string |
|
Return Value
| Type | Description |
|---|---|
| None |
Faults
| Type | Description |
|---|---|
| CannotDeleteFile | Thrown if the delete operation on the file fails. |
| FileFault | |
| FileNotFound | Thrown if the file or folder specified by datastorePath is not found. |
| InvalidArgument | Thrown if fileInfo is not a valid FileInfo type. |
| InvalidDatastore | Thrown if the operation cannot be performed on the target datastores. Typically, a specific subclass of this exception is thrown. |
| RuntimeFault | Thrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error. |
Events
| Type | |
|---|---|
| None |
Parameters
| Name | Type | Description |
|---|---|---|
| _this | ManagedObjectReference | A reference to the HostDatastoreBrowser used to make the method call. |
| datastorePath | xsd:string |
|
| searchSpec* | HostDatastoreBrowserSearchSpec |
|
Return Value
| Type | Description |
|---|---|
| ManagedObjectReference
to a Task | This method returns a Task object with which to monitor the operation. The info.result property in the Task contains the HostDatastoreBrowserSearchResults upon success. |
Faults
| Type | Description |
|---|---|
| FileFault | |
| FileNotFound | Thrown if the file or folder specified by datastorePath is not found. |
| InvalidArgument | Thrown if the SearchSpec contains duplicate file types. |
| InvalidDatastore | Thrown if the operation cannot be performed on the target datastores. The server can throw InvalidDatastorePath to indicate a malformed datastorePath, or InaccessibleDatastore to indicate inaccessibility of the datastore. |
| RuntimeFault | Thrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error. |
Events
| Type | |
|---|---|
| None |
Parameters
| Name | Type | Description |
|---|---|---|
| _this | ManagedObjectReference | A reference to the HostDatastoreBrowser used to make the method call. |
| datastorePath | xsd:string |
|
| searchSpec* | HostDatastoreBrowserSearchSpec |
|
Return Value
| Type | Description |
|---|---|
| ManagedObjectReference
to a Task | This method returns a Task object with which to monitor the operation. The info.result property in the Task contains the HostDatastoreBrowserSearchResults upon success. |
Faults
| Type | Description |
|---|---|
| FileFault | |
| FileNotFound | Thrown if the file or folder specified by datastorePath is not found. |
| InvalidArgument | Thrown if the SearchSpec contains duplicate file types. |
| InvalidDatastore | Thrown if the operation cannot be performed on the target datastores. Typically, a specific subclass of this exception is thrown. |
| RuntimeFault | Thrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error. |
Events
| Type | |
|---|---|
| None |
| Top of page | Local Properties | Local Methods | |
| Managed Object Types | Data Object Types | All Properties | All Methods |


(left, bottom),
**arrow_style)
ax.annotate("",
(left + 2*np.sign(right - left), bottom),
(left, bottom),
**arrow_style)
ax.annotate(text, **text_kwargs)
ax.axis("off")
return columns
extents = (None,
(-0.5, 6.5, -0.5, 5.5),


In the bottom part of this page you can see a quick automatic slide show showing what I've worked on.


Oops!
We can't seem to find the page you're looking for.
Error code: 404
Here are some helpful links instead:
Home
Help


Stokes and Curran put England on top in first New Zealand Test
Ben Stokes scored 91 and Sam Curran took two wickets to put England on top in the first Test against New Zealand.
Resuming on 241-4, Stokes’ innings and a ninth-wicket stand of 52 between Jos Buttler and Jack Leach took England to 353.
Kane Williamson hit fifty in New Zealand’s reply before becoming the second of Curran’s victims and the home side had reached 144-4 by the close of play on day two.
England had aspirations of surpassing 400 in their first-innings after Stokes, Joe Denly and Rory Burns all scored fifties on day one of the match in Tauranga.
World Cup hero Stokes and young batsman Ollie Pope made a bright start this morning, adding 36 runs in the first ten overs before Ross Taylor produced a superb catch to dismiss Stokes nine runs short of his century.
Stokes’ departure sparked a collapse of 4-18 in 21 balls as Surrey’s Pope fell for 29 while Curran and Jofra Archer contributed just four runs between them.
Advertisement Advertisement
Somerset team-mates and close friends Buttler and Leach combined to frustrate New Zealand, however, with their ninth-wicket partnership almost taking the tourists past 350.
Buttler eventually departed for 43 and Neil Wagner also dismissed Stuart Broad to finish with figures of 3-90, bettered only by Tim Southee (4-88).
In New Zealand’s reply, Curran – selected ahead of experienced all-rounder Chris Woakes – came on first change and immediately found the breakthrough, trapping Tom Latham LBW.
Fellow opener Jeet Raval and Kiwi skipper Williamson then added 54 before the former was removed by Leach.
Stokes continued to impress by dismissing Ross Taylor and Curran claimed the prize wicket of Williamson in the final hour of the day.
Henry Nicholls and BJ Watling survived a tricky period before the close of play but New Zealand will still resume on day three trailing by 209 runs.
Reflecting on the day and the state of the match, England bowler Leach said: ‘It was a good day for us.
‘We would have liked an extra wicket at the end but if we can get a couple early, we’ll be right on top.
‘The ball from Sam Curran to get Kane Williamson misbehaved and that’s a good sign when you’ve got runs on the board.’
New Zealand’s Southee, meanwhile, added: ‘We’ve still got a lot of batting to come so we just need some partnerships and eke out some more runs.
‘We’ll turn up tomorrow, approach the first session and then reassess where we are at lunch and then the same at tea.’
Advertisement Advertisement


Max Verstappen says it's a 'shame' crash cost Red Bull teammate podium finish - video
by FOMMax Verstappen won the Brazilian Grand Prix after a crash between Ferrari's Sebsstian Vettel and Charles Leclerc crashed out in a late dramatic finish. Lewis Hamilton finished in third place, after Toro Rosso driver Pierre Gasly took advantage of the British driver's contact with Alex Albon on the penultimate lap


300
A communication error (DTER) for the serial pulse coder was detected.
Check the connection of the signal cable. If the cable is normal, the pulse coder may be defec- tive. Turn the power off. If the alarm recurs when the power is reapplied, replace the serial pulse coder, together with the motor.
301
A communication error (CRCER) for the serial pulse coder was detected.
Check the connection of the signal cable. If the cable is normal, the pulse coder or servo ampli- fier unit may be defective. This error can also be caused by external noise.
302
A communication error (STBER) for the serial pulse coder was detected.
Check the connection of the signal cable. If the cable is normal, the pulse coder or servo ampli- fier unit may be defective. This error can also be caused by external noise.
303 An LED disconnection (LDAL) was detected in the serial pulse coder.
Turn the power off. If this alarm recurs when the power is reapplied, replace the motor.
304 A mispulse alarm (PMAL) for the serial pulse coder was detected.
Turn the power off. If this alarm recurs when the power is reapplied, replace the motor.
305
A miscount alarm (CMAL) for the serial pulse coder was detected.
Turn the power off. If the alarm recurs when the power is reapplied, replace the motor. If the alarm does not recur, restart the operation from reference position return.
306
The motor has overheated (OHAL). This alarm is issued when the motor has over- heated, causing the thermostat to trip. Possible causes include an excessively high ambient temperature and excessively strict op- erating conditions. Check the actual cause. If it occurs again when the motor is cooled, the motor or servo amplifier may have failed. Re- place the faulty motor or servo amplifier.
308 A soft phase alarm (SPHAL) was detected. Turn the power off. This alarm may be caused
by noise.
319 When the absolute pulse coder is used, the mo- tor has not yet rotated through more than one turn after the first power–up.
Rotate the motor through more than one turn in jog feed mode, then turn the power off then back on.
350 The battery voltage of the absolute pulse coder is low.
Replace the battery. Restart the operation from reference position return.
351 The battery voltage of the absolute pulse coder is low. (warning)
Replace the battery.
401
A communication error was detected in the seri- al pulse coder.
Check the connection of the pulse coder signal cable. If the cable is normal, the pulse coder or servo amplifier unit may be defective. This er- ror can also be caused by external noise.
APPENDIXG. ALARM LIST B–64124EN/01
880
Servo alarms
No. LED display Description Countermeasure
400 The servo motor has overheated (estimated value).
The motor operation condition may be too se- vere. Check the operation condition.
403
SVU–12 SVU–20
The cooling fins have over- heated. (hardware detection)
The load on the motor may be too high. Re–ex- amine the load conditions.
403 SVU–40 SVU–80
This alarm will not be issued.
404
The regenerative discharge unit has over- heated.
This alarm is issued when the average regenera- tive discharge energy is too high (when the ac- celeration/deceleration frequency is too high, for example).
404
(1) When the separate regenerative discharge resistor is not used: For the SVU–12 and the SVU–20, check whether the CX11–6 connector is short–circuited with a dummy connector; for the SVU–40 and the SVU–80, check whether the CX20 and CX23 connectors are short– circuited with a dummy connector.
(2) The average regenerative discharge energy may be too high. Decrease the acceleration/de- celeration frequency.
(3) The separate regenerative discharge unit may not be connected properly. Check the connec- tion.
(4) The thermostat of the separate regenerative discharge unit may be defective. Disconnect the separate regenerative discharge unit, then check the thermostat. If the thermostat is open even through the separate regenerative discharge unit is cool, replace the separate regenera- tive discharge unit.
(5) The resistor of the separate regenerative discharge unit may be defective. Disconnect the separate regenerative discharge unit, then check the resistance. If it does not fall in the range of the predetermined resistance (20%, replace the separate regenerative discharge unit.
(6) If (1) to (5) are not the cause of the alarm, replace the servo amplifier unit.
405
Reference position return could not be executed correctly.
Re–execute reference position return.
405 If a value in the range of 4 to 96 is set for parameter No. 032 (CMR), an alarm may be issued. In this case, prevent an alarm from being issued by setting N405 (bit 4 of parameter No. 001) to ”1”.
410 The servo position error in the stop state is larger than the value specified in parameter No.110.
Determine the mechanical cause of the large position error. If no mechanical cause is found, specify a larger value for the parameter.
411
The servo position error during movement is larger than the value specified in parameter No.182.
Determine the mechanical cause of the large position error. If no mechanical cause is found, apply any of the following countermeasures:
Specify a larger value for the parameter.
Specify a lower feedrate.
Increase the time constants.
APPENDIXB–64124EN/01 G. ALARM LIST
881
No. CountermeasureDescriptionLED display
412
[SVU–12, SVU–20] An overcurrent alarm is issued.
This alarm is issued when an excessively large current flows in the main circuit.
412
(1) Check whether a valid motor number is specified in parameter No.30.
(2) Check whether the standard values are specified in the current control parameters for servo control. Correct current control is possible only when the standard values are specified for the follow- ing parameters: No.70, 71, 72, 78, 79, 84, 85, 86, 87, 88, 89, 90
(3) Disconnect the power line from the servo amplifier unit connector. Then, release the emergen- cy stop state.
– If the overcurrent alarm continues to be issued, replace the servo amplifier unit.
– If no overcurrent alarm is issued, go to (4).
(4) Check the insulation between the ground and each of U, V, and W. If the insulation is satisfac- tory, go to (5).
– If a short–circuit is detected, disconnect the power line from the motor connector. Then, check the insulation between the ground and each of U, V, and W of the motor.
– If a short–circuit is found between the ground and U, V, or W of the motor, replace the motor.
– If the insulation is satisfactory, replace the power line.
(5) Connect the power line. Observe the waveform of the motor current (IR, IS) while the motor is accelerating or decelerating.
– If the motor current (IR, IS) does not show a normal sine wave, replace the servo amplifier unit.
(6) Check if the motor current (IR, IS) waveforms include noise.
– When noise is included, take an action such as making a connection to shield ground.
– When noise is not included, replace the servo amplifier unit.
(7) If (1) to (4) above are not the cause of the alarm, the pulse coder, command cable, or internal hardware of the CNC may be defective.
APPENDIXG. ALARM LIST B–64124EN/01
882
No. CountermeasureDescriptionLED display
412
[SVU–40, SVU–80] An overcurrent alarm or IPM alarm is issued.
This alarm is issued in the following cases:
This alarm is issued when an excessively large current flows in the main circuit.
This alarm is issued when an error (overcur- rent, overheat, low IPM control power supply voltage) is detected in the IPM (semiconduc- tor driving the motor).
412
(1) Check whether a valid motor number is specified in parameter No.30.
(2) Check whether the standard values are specified in the current control parameters for servo control. Correct current control is possible only when the standard values are specified for the follow- ing parameters: No.70, 71, 72, 78, 79, 84, 85, 86, 87, 88, 89, 90
(3) Turn off the servo amplifier unit for about ten minutes, then release the emergency stop state. If no overcurrent alarm is issued, The IPM protection function (against overheat) may be oper- ating. Possible causes of overheat include a high ambient temperature and a too severe mo- tor operating condition. Check the cause.
– If an overcurrent alarm is issued, go to (4).
(4) Disconnect the power line from the servo amplifier unit connector. Then, release the emergen- cy stop state.
– If an overcurrent alarm is issued, the IPM protection function (against overcurrent, low con- trol power supply voltage, overheat) may be operating or defective. Replace the IPM or servo amplifier unit.
– If no overcurrent alarm is issued, go to (5).
(5) Disconnect the power line from the amplifier connector. Check the insulation between the ground and each of U, V, and W.
– If a short–circuit is found between the ground and U, V, or W of the motor, replace the motor.
– If the insulation is satisfactory, replace the power line.
(6) Connect the power line. Observe the waveform of the motor current (IR, IS) while the motor is accelerating or decelerating.
– If the motor current (IR, IS) does not show a normal sine wave, replace the servo amplifier unit.
(7) Check whether the waveform of the motor current (IR, IS) contains noise.
– If it contains noise, take appropriate measures against noise, such as grounding the shield.
– If it does not contain noise, replace the servo amplifier unit.
(8) If (1) to (7) above are not the cause of the alarm, the pulse coder, command cable, or internal hardware of the CNC may be defective.
APPENDIXB–64124EN/01 G. ALARM LIST
883
No. CountermeasureDescriptionLED display
413
A DC link overvoltage alarm is issued. This alarm is issued when the DC voltage of the main circuit power is too high.
413
(1) When SVU–12 or SVU–20 is used, and a separate regenerative discharge unit is not used, check the specification to see if regenerative energy per one time does not exceed the allow- able regenerative energy of the servo amplifier unit.
(2) For the SVU–40 and the SVU–80, when the separate regenerative discharge resistor is not used, check whether the CX23 connector is short–circuited with a dummy connector.
(3) The supply voltage for dynamic power may exceed the rated value. Check the voltage. If the voltage is too high, reduce the voltage to an appropriate level.
(4) The regenerative discharge unit may not be properly connected. Check the connection.
(5) The resistance of the separate regenerative discharge unit may be abnormal. Disconnect the separate regenerative discharge unit, then check the resistance. If the resistance is not within (20% of the predetermined resistance, replace the separate regenerative discharge unit.
(6) If (1) to (5) are not the cause of the alarm, replace the servo amplifier unit.
414
A DC link low voltage alarm is issued. This alarm is issued when the DC voltage of the main circuit power is too low.
414
(1) 190 ms or longer may pass from the time when both the *ESP of the built–in DI and the *ESP of the I/O link interface signal are canceled until the external magnetic contactor inserted into the input for motive power turns on(including the operating time of the magnetic contactor). The magnetic contactor must turn on within 100 ms.
(2) The external circuit breaker may be turned off. Check the circuit breaker.
(3) The supply voltage for dynamic power is lower than the rated value. Check the voltage. If the voltage is too low, increase it to an appropriate level.
(4) The external magnetic contactor may not be connected properly. Check the connection.
If (1) to (4) are not the cause of the alarm, replace the servo amplifier unit.
417
A parameter has been specified incorrectly. Check the following parameters: No.30: Is the specified motor type correct? No.31: Is the specified direction of rotation of the motor correct? No.106: Is the denominator of the number of pulses per single revolution of the motor 0? No.180: Is the specified reference counter ca- pacity 0 or a negative value?
418 A DO alarm is issued. Replace the servo amplifier unit.
423 The specified speed exceeds 32767000 detection units per second.
Re–examine the CMR and speed settings.
425
The cooling fan has stopped. This alarm is issued when the fan motor built into the servo amplifier unit has failed. The fan motor is consumable.
425 (1) Check that the fan is not clogged with something.
(2) Check that the power connector of the fan is connected properly.
(3) Replace the fan or servo amplifier unit.
446 The external pulse input line is disconnected. Connect the external pulse input signal correctly.
447 The velocity deviation is too high (velocity con- trol)
Check the actual velocity. See the settings of parameter No. 136.
APPENDIXG. ALARM LIST B–64124EN/01
884
Overtravel alarms
No. LED display Description Countermeasure
500 The positive stroke limit has been exceeded. Check whether *+OT and *–OT are connected
correctly. Check whether a correct move com- mand is specified. Move the tool in the opposite
501 The negative stroke limit has been exceeded.
mand is specified. Move the tool in the opposite direction in jog mode, then perform a reset.
510 The positive soft stroke limit has been exceed- ed.
Check whether appropriate values have been specified for parameters No.142 and 143. Check whether a valid move command is spe-
511 The negative soft stroke limit has been exceed- ed.
Check whether a valid move command is spe- cified. Move the tool in the opposite direction in jog mode, then perform a reset.
System alarms
No. LED display Description Countermeasure
– An error was detected in the RAM write/read test at power–up.
Replace the servo amplifier unit.
– An error was detected in the data collation check for the non–volatile memory.
Turn the power off then back on. Then, re–enter the parameters. If this alarm recurs, replace the servo amplifier unit.
– A data transfer alarm for the non–volatile memory has been issued.
Replace the servo amplifier unit.
– A watchdog alarm was issued. Turn the power off then back on. If this alarm re-
curs, replace the servo amplifier unit.
– A checksum alarm for the control software ROM is issued.
Replace the servo amplifier unit.
– A checksum alarm for the ROM that is built into the CPU is issued.
Replace the servo amplifier unit.
– An error was detected in the control circuit. Replace the servo amplifier unit.
I/O link alarm
No. LED display Description Countermeasure
– A FANUC I/O Link error occurred. Any unit con- nected to the line was turned off.
Turn off the power to all units connected to the line. Then, turn on the slave devices, followed by the master device.
No LED display
No. LED display Description Countermeasure
– No indicators
lit
The control circuit is not operating normally. (1) Check the 24–VDC control supply voltage. If the voltage is low, increase the voltage to an appropriate level.
(2) Check whether a fuse in the servo amplifier unit has blown. If a blown fuse is found, re- place it.
If (1) and (2) are not the cause, replace the ser- vo amplifier.
APPENDIXB–64124EN/01 G. ALARM LIST
885
12) System alarms (These alarms cannot be reset with reset key.)
Number Message Contents
900 ROM PARITY ROM parity error (CNC/OMM/Servo) Replace the number of ROM.
910 SRAM PARITY : (BYTE 0) RAM parity error in the tape memory RAM module. Clear the memory or replace the module.
911 SRAM PARITY: (BYTE 1) or replace the module. After this operation, reset all data including the parameters.
912 DRAM PARITY : (BYTE 0) RAM parity error in the DRAM module. Replace the DRAM module.
913 DRAM PARITY : (BYTE 1)
914 DRAM PARITY : (BYTE 2)
915 DRAM PARITY : (BYTE 3)
916 DRAM PARITY : (BYTE 4)
917 DRAM PARITY : (BYTE 5)
918 DRAM PARITY : (BYTE 6)
919 DRAM PARITY : (BYTE 7)
920 SERVO ALARM (1 to 4 AXIS) Servo alarm (1st to 4th axis). A watchdog alarm or a RAM parity error in the servo module occurred. Replace the servo control module on the main CPU board.
926 FSSB ALARM FSSB alarm. Replace the servo control module on the main CPU board.
930 CPU INTERRUPUT CPU error (abnormal interrupt) The main CPU board is faulty.
935 SRAM ECC ERROR An error occurred in RAM for part program storage. Action: Replace the master printed circuit board (SRAM module), perform all– clear operation, and set all parameter and other data again.
950 PMC SYSTEM ALARM Fault occurred in the PMC. The PMC control module on the main CPU board or option board may be faulty.
951 PMC–RC WATCH DOG ALARM Fault occurred in the PMC–RC (watchdog alarm).Option board may be faulty.
970 NMI OCCURRED IN PMCLSI With the PMC–SA1, an error occurred in the PMC control LSI device on the motherboard. (I/O RAM parity) Replace the motherboard.
971 NMI OCCURRED IN SLC With the PMC–SA1, an I/O Link disconnection was detected. Check the I/O Link.
972 NMI OCCURRED IN OTHER MOD- ULE
NMI occurred in a board other than the main CPU board.
973 NON MASK INTERRUPT NMI occurred for an unknown reason.
974 F–BUS ERROR BUS error of FANUC BUS. The main CPU board or option boards may be faulty.
975 BUS ERROR (MAIN) Main CPU board bus error. The main CPU board may be faulty.
976 L–BUS ERROR Bus error of Local Bus. The main CPU board may be faulty.
IndexB–64124EN/01
i–1
[Numbers] 7.2″ Monochrome/8.4″ Color LCD/MDI Unit (Hori-
zontal Type), 431
7.2″ Monochrome/8.4″ Color LCD/MDI Unit (Vertical Type), 432
[A] Absolute and Incremental Programming (G90, G91),
99
Actual Feedrate Display, 648
Adding Workpiece Coordinate Systems (G54.1 or G54), 93
Advanced Preview Control (G08), 378
AI Advanced Preview Control Function/ AI Contour Control Function, 380
Alarm and Self–Diagnosis Functions, 531
Alarm Display, 426, 532
Alarm History Display, 534
Alarm List, 848
Alarms, 811
Altering a Word, 601
Angular Axis Control/Angular Axis Control B, 408
Arc, 785, 790, 806
Arc that Contacts to both Crossing Lines and Arcs, 795
Arc that Contacts to Uncrossing 2 Arcs, 797
Arc that Contacts to Uncrossing Line and Arc, 796
Arithmetic and Logic Operation, 317
Automatic Corner Deceleration, 73
Automatic Corner Override, 70
Automatic Erase Screen Display, 704
Automatic Insertion of Sequence Numbers, 625
Automatic Operation, 417, 477
Automatic Override for Inner Corners (G62), 70
Automatic Tool Length Measurement (G37), 214
Auxiliary Function, 121
Auxiliary Function (M Function), 122
Axis Control Functions, 403
Axis Name, 29
[B] Back Boring Cycle (G87), 167
Background Editing, 620
Battery for Absolute Pulse Coder Built into the Motor (6VDC), 821
Battery for Memory Backup (3VDC), 816
Battery for Separate Absolute Pulse Coders (6VDC), 820
Boring Cycle (G85), 163
Boring Cycle (G86), 165
Boring Cycle (G88), 169
Boring Cycle (G89), 171
Branch and Repetition, 323
[C] Calculation of Inputting Data, 808
Calling Contour Programming Screen, 776
Canned Cycle, 141
Canned Cycle Cancel (G80), 173, 185
Canned Cycle Machining, 757
Canned Grinding Cycle (For Grinding Machine), 186
Caution for using system variables, 343
Cautions on Reading this Manual, 8
Cautions on Various Kinds of Data, 8
Chamfering, 786
Changing Workpiece Coordinate System, 88
Character–to–Codes Correspondence Table, 847
Characters and Codes to be Used for the Pattern Data Input Function, 371
Check by Running the Machine, 419
Checking by Self–Diagnostic Screen, 535
Checking Contour Figures, 782
Checking the Minimum Grinding Wheel Diameter (For Grinding Machine), 196
Circular Interpolation (G02, G03), 43
Clearing the Screen, 703
Command for Machine Operations–Miscellaneous Function, 22
Compensation Function, 205
Conditional Branch (IF Statement), 324
Constant Surface Speed Control (G96, G97), 107
Continuous–Feed Surface Grinding Cycle (G78), 191
Contour Programming, 775
Controlled Axes, 28, 29
Conversational Programming with Graphic Function, 630
Convert to NC Program, 783
Coordinate System, 84
Index B–64124EN/01
i–2
Coordinate System on Part Drawing and Coordinate System Specified by CNC – Coordinate System, 16
Coordinate System Rotation (G68, G69), 291
Coordinate Value and Dimension, 98
Copying an Entire Program, 611
Copying Part of a Program, 612
Corner Circular Interpolation (G39), 282
Corner Deceleration According to the Corner Angle, 73
Corner Deceleration According to the Feedrate Differ- ence between Blocks Along Each Axis, 75
Corner R, 785
Creating a New Part Program, 748
Creating Programs, 623
Creating Programs in Teach in Mode (Playback), 627
Creating Programs Using the MDI Panel, 624
Current Block Display Screen, 655
Current Position Display, 426
Custom Macro, 304
Cutting Feed, 63
Cutting Feedrate Control, 68
Cutting Speed–Spindle Speed Function, 20
Cylindrical Interpolation (G07.1), 48
[D] Data for Each Canned Cycle, 760
Data Input/Output, 428, 538
Data Input/Output On the All IO Screen, 566
Data Input/Output Using a Memory Card, 583
Decimal Point Programming, 104
Deleting a Block, 603
Deleting a Word, 602
Deleting All Programs, 608
Deleting Blocks, 603
Deleting Files, 563
Deleting More Than One Program by Specifying a Range, 609
Deleting Multiple Blocks, 604
Deleting One Program, 608
Deleting Programs, 608
Detail of Contour Calculation, 787
Detail of Contour Figure Data, 785
Details of Auxiliary Calculation, 798
Details of Cutter Compensation C, 229
Details of Functions, 354
Details of NC statements and macro statements execu- tion, 341
Direct Constant–Dimension Plunge Grinding Cycle (G77), 189
Direct Input of Measured Workpiece Origin Offsets, 677
Display, 425
Display of Run Time and Parts Count, 650
Displaying a Program List for a Specified Group, 662
Displaying and Entering Setting Data, 670
Displaying and Setting Custom Macro Common Vari- ables, 679
Displaying and Setting Data, 422
Displaying and Setting Extended Tool Life Manage- ment, 687
Displaying and Setting Parameters, 693
Displaying and Setting Pitch Error Compensation Data, 695
Displaying and Setting Run Time, Parts Count, and Time, 674
Displaying and Setting the Software Operator’s Panel, 682
Displaying and Setting the Workpiece Origin Offset Value, 676
Displaying and Setting Tool Life Management Data, 684
Displaying Directory of Floppy Cassette, 557
Displaying Memory Used and a List of Programs, 659
Displaying Pattern Data and Pattern Menu, 680
Displaying the Directory, 558
Displaying the Pattern Menu, 363
Displaying the Program Number and Sequence Num- ber, 698
Displaying the Program Number, Sequence Number, and Status, and Warning Messages for Data Setting or Input/Output Operation, 698
Displaying the Status and Warning for Data Setting or Input/Output Operation, 699
DNC Operation, 485, 509
DNC Operation with Memory Card, 508
Drilling Cycle Counter Boring Cycle (G82), 153
Drilling Cycle, Spot Drilling (G81), 151
Dry Run, 518
Dwell (G04), 77
Dynamic Graphic Display, 712
[E] Editing a Part Program, 421
B–64124EN/01 Index
i–3
Editing of Custom Macros, 619
Editing Programs, 595
Emergency Stop, 522
Entering of Contour Program, 778
Erase Screen Display, 703
Exact Stop (G09, G61) Cutting Mode (G64) Tapping Mode (G63), 69
Explanation of the Keyboard, 435
Extended Part Program Editing Function, 610
External I/O Devices, 457
External Motion Function (G81), 201
External Operator Message History Display, 701
External Output Commands, 348
[F] FANUC Handy File, 459
Feed Functions, 59
Feed–Feed Function, 14
Feedrate Clamping by Arc Radius, 377
Feedrate Override, 516
Figure block of Face machining, 768
Figure block of Groove machining, 774
Figure block of Hole machining, 762
Figure block of Pocket machining, 771
File Deletion, 543
File Search, 541
Files, 539
Fine Boring Cycle (G76), 149
Function Keys, 438
Function Keys and Soft Keys, 437
Functions to Simplify Programming, 140
[G] G–code Assistance, 752
G53, G28, and G30 Commands in Tool Length Offset Mode, 211
G53,G28,G30,G30.1 and G29 Commands in Cutter Compensation C Mode, 263
General, 798
General Flow of Operation of CNC Machine Tool, 6
General Screen Operations, 437
Graphic Display, 427
Graphics Display, 706
Graphics Function, 705
Grinding–Wheel Wear Compensation by Continuous Dressing (For Grinding Machine), 195
[H] Heading a Program, 599
Helical Interpolation (G02, G03), 47
Help Function, 733
High Speed Cutting Functions, 376
High Speed Skip Signal (G31), 55
High–speed Peck Drilling Cycle (G73) , 145
How to Indicate Command Dimensions for Moving the Tool – Absolute, Incremental Commands, 19
How to use nomograph, 838
How to View the Position Display Change without Running the Machine, 420
[I] In–Feed Grinding Along the Y and Z Axes at the End
of Table Swing (For Grinding Machine), 197
Inch/Metric Conversion (G20,G21), 103
Incorrect Threaded Length, 837
Increment System, 30
Incremental Feed, 468
Index Table Indexing Function, 202
Input Command from MDI, 262
Inputting a Program, 544
Inputting and Outputting Floppy Files, 578
Inputting and Outputting Offset Data, 575
Inputting and Outputting Parameters, 573
Inputting and Outputting Parameters and Pitch Error Compensation Data, 551
Inputting and Outputting Programs, 568
Inputting Custom Macro Common Variables, 555
Inputting Offset Data, 549
Inputting Parameters, 551
Inputting Pitch Error Compensation Data, 553
Inputting/Outputting Custom Macro Common Vari- ables, 555
Inserting a Word, 600
Inserting, Altering and Deleting a Word, 596
Interference Check, 254
Intermittent–Feed Surface Grinding Cycle (G79), 193
Internal Circular Cutting Feedrate Change, 72
Index B–64124EN/01
i–4
Interpolation Functions, 36
Interruption Type Custom Macro, 352
[J] Jog Feed, 466
[K] Key Input and Input Buffer, 455
Key Location of MDI (Horizontal Type LCD/MDI Unit), 433
Key Location of MDI (Vertical Type LCD/MDI Unit), 434
[L] Left–handed Rigid Tapping Cycle (G74), 180
Left–handed Tapping Cycle (G74), 147
Limitation and Notes, 511
Limitations, 347
Line, 787, 804
Line tangential to two arcs, 794
Linear Interpolation (G01), 41
List of Function and Tape Format, 828
Local Coordinate System, 95
[M] M–code Assistance, 755
Machine Coordinate System, 85
Machine Lock and Auxiliary Function Lock, 514
Machining type block of Face machining, 767
Machining type block of Groove machining, 772
Machining type block of Hole machining, 760
Machining type block of Pocket machining, 769
Macro Call, 328
Macro Call Using an M Code, 336
Macro Call Using G Code, 335
Macro Statements and NC Statements, 322
Manual Absolute On and Off, 472
Manual Guide 0i, 743
Manual Handle Feed, 469
Manual Handle Interruption, 501
Manual Intervention and Return, 506
Manual Operation, 414, 463
Manual Reference Position Return, 464
Maximum Stroke, 30
MDI Operation, 481
Memory Operation, 478
Memory Operation Using FS10/11 Tape Format, 375
Merging a Program, 614
Method of Replacing Battery, 815
Mirror Image, 504
Modal Call (G66), 333
Moving Part of a Program, 613
Multiple M Commands in a Single Block, 123
Multistage Skip (G31), 56
[N] Next Block Display Screen, 656
Nomographs, 836
Normal Direction Control (G40.1, G41.1, G42.1 or G150, G151, G152), 297
Notes should be paid Attention in Contour Program- ming, 809
Notes should be paid Attention in Macro Executor, 809
[O] Offset Data Input and Output, 549
Operating Monitor Display, 651
Operation, 758
Operational Devices, 429
Operations, 509
Operations of Contour Programming, 776
Optional Angle Chamfering and Corner Rounding, 198
Others, 808
Outputting a Program, 547
Outputting a Program List for a Specified Group, 565
Outputting Custom Macro Common Variable, 556
Outputting Custom Macro Common Variables, 577
Outputting Offset Data, 550
Outputting Parameters, 552
Outputting Pitch Error Compensation Data, 554
Outputting Programs, 562
Overall Position Display, 646
B–64124EN/01 Index
i–5
Overcutting by Cutter Compensation, 259
Overtravel, 523
Overview of Cutter Compensation C (G40 – G42), 223
[P] Parameter, 511, 810
Part Drawing and Tool Movement, 15
Parts Count Display, Run Time Display, 427
Password Function, 621
Path Drawing, 712
Pattern Data Display, 367
Pattern Data Input Function, 362
Peck Drilling Cycle (G83), 155
Peck Rigid Tapping Cycle (G84 or G74), 183
Plane Selection, 97
Plunge Grinding Cycle (G75), 187
Polar Coordinate Command (G15, G16), 100
Position Display in the Relative Coordinate System, 644
Position Display in the Work Coordinate System, 643
Positioning (G00), 37
Power Disconnection, 462
Power On/Off, 460
Preparatory Function (G Function), 31
Presetting the Workpiece Coordinate System, 647
Procedure for Fixing the Memory Card, 511
Process Assistance, 750
Processing Macro Statements, 341
Program Check Screen, 657
Program Components other than Program Sections, 127
Program Configuration, 23, 125
Program Contents Display, 654
Program Creating Operations, 746
Program Display, 425
Program Input/Output, 544
Program Number Search, 605
Program Restart, 487
Program Screen for MDI Operation, 658
Program Section Configuration, 130
Programmable Mirror Image (G50.1, G51.1), 302
Programmable Parameter Entry (G10), 373
[R] Radius Direction Error at Circle Cutting, 844
Range of Command Value, 833
Rapid Traverse, 62
Rapid Traverse Override, 517
Reading Files, 561
Reference Position, 78
Reference Position (Machine–Specific Position), 15
Reference Position Return, 79
Register, Change and Delete of Tool Life Manage- ment Data, 114
Registering Custom Macro Programs, 346
Repetition (While Statement), 325
Replacement of Words and Addresses, 617
Rigid Tapping, 176
Rigid Tapping (G84), 177
Rotary axis roll–over, 407
[S] Safety Functions, 521
Sample Program, 339
Scaling (G50, G51), 286
Scheduling Function, 494
Screen Displayed at Power–on, 461
Screen Hardcopy, 738
Screens Displayed by Function Key MESSAGE
, 701
Screens Displayed by Function Key OFS/SET
, 665
Screens Displayed by Function Key POS
, 642
Screens Displayed by Function Key PROG
(In Memory Mode or MDI Mode), 653
Screens Displayed by Function Key PROG
(In the Edit Mode), 659
Screens Displayed by Function Key SYSTEM
, 692
Select Crossing Point of Figure, 786
Selecting a Workpiece Coordinate System, 87
Selecting of Method to Edit of Contour Program, 776
Selection of Tool Used for Various Machining–Tool Function, 21
Sequence Number Comparison and Stop, 672
Sequence Number Search, 606
Index B–64124EN/01
i–6
Setting a Workpiece Coordinate System, 86
Setting and Display Units, 430
Setting and Displaying Data, 634
Setting and Displaying the Tool Offset Value, 666
Setting Input/Output–Related Parameters, 567
Setting of the reference position return feedrate, 81
Simple Calculation of Incorrect Thread Length, 839
Simple Call (G65), 329
Simple synchronous control, 404
Single Block, 519
Single Direction Positioning (G60), 39
Skip Function (G31), 53
Small–hole peck drilling cycle (G83), 157
Soft Keys, 439
Solid Graphics, 721
Specification, 508
Specification Method, 353
Specifying the Spindle Speed Value Directly (S5–Dig- it Command), 106
Specifying the Spindle Speed with a Code, 106
Spindle Speed Function (S Function), 105
Start Point, 799
Start Up, 746, 747
Status when Turning Power On, when Clear and when Reset, 845
Stored Stroke Check, 524
Stroke Limit Check Prior to Performing Movement, 528
SUBPROGRAM (M98, M99), 136
Subprogram Call (M198), 510
Subprogram Call Function (M198), 499
Subprogram Call Using an M Code, 337
Subprogram Calls Using a T Code, 338
Supplementary Explanation for Copying, Moving and Merging, 615
System Variables, 308
[T] Tandem Control, 410
Tape Code List, 825
Tapping Cycle (G84), 161
Test Operation, 513
Testing a Program, 419
The Second Auxiliary Functions (B Codes), 124
Thread Cutting (G33), 51
Tool Compensation Values, Number of Compensation Values, and Entering Values From the Program (G10), 284
Tool Figure and Tool Motion by Program, 26
Tool Function (T Function), 110
Tool Length Measurement, 668
Tool Length Offset (G43,G44,G49), 206
Tool Life, 120
Tool Life Management Command in a Machining Pro- gram, 117
Tool Life Management Data, 113
Tool Life Management Function, 112
Tool Movement Along Workpiece Parts Figure– Inter- polation, 12
Tool Movement by Programming – Automatic Opera- tion, 416
Tool Movement in Offset Mode, 234
Tool Movement in Offset Mode Cancel, 248
Tool Movement in Start–up, 230
Tool Movement Range–Stroke, 27
Tool Offset (G45–G48), 218
Tool Path at Corner, 841
Tool Selection Function, 111
Torque Limit Skip (G31 P99), 57
Turning on the Power, 460
[U] Unconditional Branch (GOTO Statement), 323
[V] Variables, 305
[W] Warning Messages, 456
Word Search, 597
Workpiece Coordinate System, 86
Workpiece coordinate system preset (G92.1), 91
R ev
is io
n R
ec o
rd
FA N
U C E - � � �� �
0i –M
C O
P E
R A
T O
R ’S
M A
N U
A L
( B
–6 41
24 E
N )
01 Ju
n. , 2
00 4
E di
tio n
D at
e C
on te
nt s
E di
tio n
D at
e C
on te
nt s


Are The Row Headers in PowerPoint Accessible By Screen Reader?
The question:When you use the PowerPoint header and row design features, does that make them available by screen readers? (from the workshop for Columns and Rows on April 19, 2019
Short answer:As of April 2019, No. That said, you should still take the time to do it. At a minimum, it helps those with low vision, and in the future, Microsoft may change the code under the hood so that the column and row headers in tables are accessible to screen readers.


Standard Information Format (SIF) is a computer-oriented language for the representation of data and knowledge. It has declarative semantics (i.e. the meaning of expressions in the representation can be understood without appeal to an interpreter for manipulating those expressions), and it is logically comprehensive (i.e. it provides for the expression of arbitrary sentences in relational logic).


Properties
functions of type function(req, res, next, handler) that will be called as middle wares
Type:
- Array
the request as delivered from express framework
Type:
- http.clientRequest
the response as delivered from express framework
Type:
- http.serverResponse
If true no further handling will be done because the response is already sent
Type:
- Bool
Methods
To be overridden by inheriting classes
Parameters:
| Name | Description |
|---|---|
callback |
callback that should be called when handling is done ( function( req, res, handler) ) |
To be called from outside (user of class) when setup is finished
Parameters:
| Name | Description |
|---|---|
callback |
callback that should be called when handling is done ( function( req, res, handler) ) |
Add middle ware
Parameters:
| Name | Description |
|---|---|
middleWare |
function to be called before handler function. ( function( req, res, next, handler)) |


"KERIOTH "cities. (1.) A town in the south of Judah (Joshua 15:25). Judas the traitor was probably a native of this place, and hence his name Iscariot. It has been identified with the ruins of el-Kureitein, about 10 miles south of Hebron. (See HAZOR [4]). (2.) A city of Moab (Jeremiah 48:24, 41), called Kirioth (Amos 2:2).
"KERIOTH "cities. (1.) A town in the south of Judah (Joshua 15:25). Judas the traitor was probably a native of this place, and hence his name Iscariot.
It has been identified with the ruins of el-Kureitein, about 10 miles south of Hebron. (See HAZOR [4]).
(2.) A city of Moab (Jeremiah 48:24, 41), called Kirioth (Amos 2:2).


Getting started with Theory Maker Drag & Drop
Be careful, still in beta! Only works in Chrome, Firefox or Opera. Also try
theorymaker.info, the text-based alternative.
-
Zoom in: Scroll with mouse wheel (or two finger drag on your trackpad)
-
Move diagram around: Click on the background and drag
-
Add a new Variable: Double-click on the diagram OR drag away from one Variable, using the ➦ icon.
-
Change or delete something: Click the ✎ icon (near the end of an Arrow, at the top-left of Variables
and Groups) OR right-click on it. To finish, just click the diagram background.
-
Add an arrow: Hover your mouse over a Variable or Group and click on the ➦ icon at the top-right,
then drag to another or to an empty space (press Ctrl+Shift at the same time to get a reverse Arrow).
-
Add a Group box: Click on the Variables you want, right-click, “Add group”.
-
Move a Variable or a Group: Drag it and drop it.
-
Move a Variable into and out of Groups: Near the top-right corner of the Variable, grab the ➟ icon.
Using the right-hand panel (if you can’t see it, click on the gear-wheel icon)
-
Fold and unfold sections of the panel: click on the
-
Save your diagram online: In the
Save
section, type a name and press “Save diagram online”. You can revisit it again at the link
which appears. An online
png
image is also created.
-
Download your diagram as a picture: Zoom in or out as required, Select the type you want (
emf
is good for Microsoft Office docs), Click download.
-
Copy your diagram to the clipboard: click “Create Web Graphic”, then Ctrl+C (or right-click
/ copy), then click to return to app.
-
Change the appearance of
all your Variables, Groups and/or Arrows: change the settings in the right-hand panel.


Terms & Conditions
You are granted a non-exclusive limited license to use War Worlds in accordance with these Terms & Conditions (the “license”) issued by us.
1. Acceptance of Terms
Codeka Consulting provides software and website services to you subject to the following Terms of Service (“TOS”). If you do not agree to the TOS, then you should not use War Worlds or this website.
2. Product Compatibility
All reasonable effort is made to ensure the application is compatible with all supported versions of Android, but we can give no guarantee that the application will run on every variation possible. We are, however, committed to doing our best to make the application compatible with as many devices as is feasible as quickly as we can.
3. Refund Policy
Refunds are generally granted for most reasons, and can be initiated by sending and email to<EMAIL_ADDRESS>4. Ownership
You may not claim intellectual or exclusive ownership to any of our products, modified or unmodified. War Worlds is open source software, and is licensed under the MIT License, however the name "War Worlds" is a trademark of Codeka Consulting and cannot be used without permission.
5. Site Content
All content, including forum posts, documentation and imagery, published on the war-worlds.com domain, is property of Codeka Consulting and under copyright.
6. Privacy
We take user privacy very seriously, details given on our Privacy Policy page.
7. Support
War Worlds is provided “as is,” however, best-effort is made to provide support to users as required. Please contact us at<EMAIL_ADDRESS>with all support requests, and we will do our best to address all issues. However, no gaurantee is provided that all requests will be looked into.
8.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Codeka Consulting reserves the right to change or modify current Terms & Conditions with no prior notice.


All Packages Class Hierarchy This Package Previous Next Index
Class javax.servlet.http.Cookie
java.lang.Object
|
+----javax.servlet.http.Cookie
- public class Cookie
- extends Object
- implements Cloneable
This class represents a "Cookie", as used for session management with
HTTP and HTTPS protocols. Cookies are used to get user agents (web
browsers etc) to hold small amounts of state associated with a user's
web browsing. Common applications for cookies include storing user
preferences, automating low security user signon facilities, and helping
collect data used for "shopping cart" style applications.
Cookies are named, and have a single value. They may have optional
attributes, including a comment presented to the user, path and domain
qualifiers for which hosts see the cookie, a maximum age, and a version.
Current web browsers often have bugs in how they treat those attributes,
so interoperability can be improved by not relying on them heavily.
Cookies are assigned by servers, using fields added to HTTP response
headers. In this API, cookies are saved one at a time into such HTTP
response headers, using the
javax.servlet.http.HttpServletResponse.addCookie method. User
agents are expected to support twenty cookies per host, of at least four
kilobytes each; use of large numbers of cookies is discouraged.
Cookies are passed back to those servers using fields added to HTTP
request headers. In this API, HTTP request fields are retrieved using
the cookie module's
javax.servlet.http.HttpServletRequest.getCookies method.
This returns all of the cookies found in the request. Several cookies
with the same name can be returned; they have different path attributes,
but those attributes will not be visible when using "old format" cookies.
Cookies affect the caching of the web pages used to set their values.
At this time, none of the sophisticated HTTP/1.1 cache control models
are supported by this class. Standard HTTP/1.0 caches will not cache
pages which contain cookies created by this class.
Cookies are being standardized by the IETF. This class supports
the original Cookie specification (from Netscape Communications Corp.)
as well as the updated RFC 2109 specification. By default, cookies
are stored using the original specification. This promotes maximal
interoperability; an updated RFC will provide better interoperability
by defining a new HTTP header field for setting cookies.
-
Cookie(String, String)
- Defines a cookie with an initial name/value pair.
-
clone()
- Returns a copy of this object.
-
getComment()
- Returns the comment describing the purpose of this cookie, or
null if no such comment has been defined.
-
getDomain()
- Returns the domain of this cookie.
-
getMaxAge()
- Returns the maximum specified age of the cookie.
-
getName()
- Returns the name of the cookie.
-
getPath()
- Returns the prefix of all URLs for which this cookie is targetted.
-
getSecure()
- Returns the value of the 'secure' flag.
-
getValue()
- Returns the value of the cookie.
-
getVersion()
- Returns the version of the cookie.
-
setComment(String)
- If a user agent (web browser) presents this cookie to a user, the
cookie's purpose will be described using this comment.
-
setDomain(String)
- This cookie should be presented only to hosts satisfying this domain
name pattern.
-
setMaxAge(int)
- Sets the maximum age of the cookie.
-
setPath(String)
- This cookie should be presented only with requests beginning
with this URL.
-
setSecure(boolean)
- Indicates to the user agent that the cookie should only be sent
using a secure protocol (https).
-
setValue(String)
- Sets the value of the cookie.
-
setVersion(int)
- Sets the version of the cookie protocol used when this cookie saves
itself.
Cookie
public Cookie(String name,
String value)
- Defines a cookie with an initial name/value pair. The name must
be an HTTP/1.1 "token" value; alphanumeric ASCII strings work.
Names starting with a "$" character are reserved by RFC 2109.
- Parameters:
- name - name of the cookie
- value - value of the cookie
setComment
public void setComment(String purpose)
- If a user agent (web browser) presents this cookie to a user, the
cookie's purpose will be described using this comment. This is
not supported by version zero cookies.
- See Also:
- getComment
getComment
public String getComment()
- Returns the comment describing the purpose of this cookie, or
null if no such comment has been defined.
- See Also:
- setComment
setDomain
public void setDomain(String pattern)
- This cookie should be presented only to hosts satisfying this domain
name pattern. Read RFC 2109 for specific details of the syntax.
Briefly, a domain name name begins with a dot (".foo.com") and means
that hosts in that DNS zone ("www.foo.com", but not "a.b.foo.com")
should see the cookie. By default, cookies are only returned to
the host which saved them.
- See Also:
- getDomain
getDomain
public String getDomain()
- Returns the domain of this cookie.
- See Also:
- setDomain
setMaxAge
public void setMaxAge(int expiry)
- Sets the maximum age of the cookie. The cookie will expire
after that many seconds have passed. Negative values indicate
the default behaviour: the cookie is not stored persistently,
and will be deleted when the user agent (web browser) exits.
A zero value causes the cookie to be deleted.
- See Also:
- getMaxAge
getMaxAge
public int getMaxAge()
- Returns the maximum specified age of the cookie. If none was
specified, a negative value is returned, indicating the default
behaviour described with setMaxAge.
- See Also:
- setMaxAge
setPath
public void setPath(String uri)
- This cookie should be presented only with requests beginning
with this URL. Read RFC 2109 for a specification of the default
behaviour. Basically, URLs in the same "directory" as the one
which set the cookie, and in subdirectories, can all see the
cookie unless a different path is set.
- See Also:
- getPath
getPath
public String getPath()
- Returns the prefix of all URLs for which this cookie is targetted.
- See Also:
- setPath
setSecure
public void setSecure(boolean flag)
- Indicates to the user agent that the cookie should only be sent
using a secure protocol (https). This should only be set when
the cookie's originating server used a secure protocol to set the
cookie's value.
- See Also:
- getSecure
getSecure
public boolean getSecure()
- Returns the value of the 'secure' flag.
- See Also:
- setSecure
getName
public String getName()
- Returns the name of the cookie. This name may not be changed
after the cookie is created.
setValue
public void setValue(String newValue)
- Sets the value of the cookie. BASE64 encoding is suggested for
use with binary values.
With version zero cookies, you need to be careful about the
kinds of values you use. Values with various special characters
(whitespace, brackets and parentheses, the equals sign, comma,
double quote, slashes, question marks, the "at" sign, colon, and
semicolon) should be avoided. Empty values may not behave the
same way on all browsers.
- See Also:
- getValue
getValue
public String getValue()
- Returns the value of the cookie.
- See Also:
- setValue
getVersion
public int getVersion()
- Returns the version of the cookie. Version 1 complies with
RFC 2109, version 0 indicates the original version, as specified
by Netscape. Newly constructed cookies use version 0 by default,
to maximize interoperability. Cookies provided by a user agent
will identify the cookie version used by the browser.
- See Also:
- setVersion
setVersion
public void setVersion(int v)
- Sets the version of the cookie protocol used when this cookie saves
itself. Since the IETF standards are still being finalized, consider
version 1 as experimental; do not use it (yet) on production sites.
- See Also:
- getVersion
clone
public Object clone()
- Returns a copy of this object.
- Overrides:
- clone in class Object
All Packages Class Hierarchy This Package Previous Next Index


|
1-Wire API for .NET Version 4.00
|
Inherits com::dalsemi::onewire::adapter::DSPortAdapter, and com::dalsemi::onewire::adapter::NetAdapterConstants.
Public Member Functions | |
| NetAdapter () | |
| Creates an instance of NetAdapter that isn't connected. | |
| void | setSecret (String secret) |
| Sets the shared secret for authenticating this NetAdapter with a NetAdapterHost. | |
| void | resetSecret () |
| Resets the secret to be the default stored in the onewire.properties file (if there is one), or the default as defined by NetAdapterConstants. | |
| void | pingHost () throws OneWireException, OneWireIOException |
| Sends a ping to the host, just to keep the connection alive. | |
| boolean | adapterDetected () throws OneWireIOException, OneWireException |
| Detects adapter presence on the selected port. | |
| String | getAdapterName () |
| Retrieves the name of the port adapter as a string. | |
| String | getPortTypeDescription () |
| Retrieves a description of the port required by this port adapter. | |
| String | getClassVersion () |
| Retrieves a version string for this class. | |
| Enumeration | getPortNames () |
| Retrieves a list of the platform appropriate port names for this adapter. | |
| boolean | selectPort (String portName) throws OneWireIOException, OneWireException |
| Specifies a platform appropriate port name for this adapter. | |
| boolean | selectPort (Socket sock) throws OneWireIOException, OneWireException |
| New method, unique to NetAdapter. | |
| void | freePort () throws OneWireException |
| Frees ownership of the selected port, if it is currently owned, back to the system. | |
| String | getPortName () throws OneWireException |
Retrieves the name of the selected port as a String . | |
| boolean | canOverdrive () throws OneWireIOException, OneWireException |
| Returns whether adapter can physically support overdrive mode. | |
| boolean | canHyperdrive () throws OneWireIOException, OneWireException |
| Returns whether the adapter can physically support hyperdrive mode. | |
| boolean | canFlex () throws OneWireIOException, OneWireException |
| Returns whether the adapter can physically support flex speed mode. | |
| boolean | canProgram () throws OneWireIOException, OneWireException |
| Returns whether adapter can physically support 12 volt power mode. | |
| boolean | canDeliverPower () throws OneWireIOException, OneWireException |
| Returns whether the adapter can physically support strong 5 volt power mode. | |
| boolean | canDeliverSmartPower () throws OneWireIOException, OneWireException |
| Returns whether the adapter can physically support "smart" strong 5 volt power mode. | |
| boolean | canBreak () throws OneWireIOException, OneWireException |
| Returns whether adapter can physically support 0 volt 'break' mode. | |
| boolean | findFirstDevice () throws OneWireIOException, OneWireException |
Returns true if the first iButton or 1-Wire device is found on the 1-Wire Network. | |
| boolean | findNextDevice () throws OneWireIOException, OneWireException |
Returns true if the next iButton or 1-Wire device is found. | |
| void | getAddress (byte[] address) |
| Copies the 'current' 1-Wire device address being used by the adapter into the array. | |
| void | setSearchOnlyAlarmingDevices () |
| Sets the 1-Wire Network search to find only iButtons and 1-Wire devices that are in an 'Alarm' state that signals a need for attention. | |
| void | setNoResetSearch () |
| Sets the 1-Wire Network search to not perform a 1-Wire reset before a search. | |
| void | setSearchAllDevices () |
| Sets the 1-Wire Network search to find all iButtons and 1-Wire devices whether they are in an 'Alarm' state or not and restores the default setting of providing a 1-Wire reset command before each search. | |
| void | targetAllFamilies () |
| Removes any selectivity during a search for iButtons or 1-Wire devices by family type. | |
| void | targetFamily (int family) |
| Takes an integer to selectively search for this desired family type. | |
| void | targetFamily (byte family[]) |
| Takes an array of bytes to use for selectively searching for acceptable family codes. | |
| void | excludeFamily (int family) |
| Takes an integer family code to avoid when searching for iButtons. | |
| void | excludeFamily (byte family[]) |
| Takes an array of bytes containing family codes to avoid when finding iButtons or 1-Wire devices. | |
| boolean | beginExclusive (boolean blocking) throws OneWireException |
| Gets exclusive use of the 1-Wire to communicate with an iButton or 1-Wire Device. | |
| void | endExclusive () |
| Relinquishes exclusive control of the 1-Wire Network. | |
| int | reset () throws OneWireIOException, OneWireException |
| Sends a Reset to the 1-Wire Network. | |
| void | putBit (boolean bitValue) throws OneWireIOException, OneWireException |
| Sends a bit to the 1-Wire Network. | |
| boolean | getBit () throws OneWireIOException, OneWireException |
| Gets a bit from the 1-Wire Network. | |
| void | putByte (int byteValue) throws OneWireIOException, OneWireException |
| Sends a byte to the 1-Wire Network. | |
| int | getByte () throws OneWireIOException, OneWireException |
| Gets a byte from the 1-Wire Network. | |
| byte[] | getBlock (int len) throws OneWireIOException, OneWireException |
| Gets a block of data from the 1-Wire Network. | |
| void | getBlock (byte[] arr, int len) throws OneWireIOException, OneWireException |
| Gets a block of data from the 1-Wire Network and write it into the provided array. | |
| void | getBlock (byte[] arr, int off, int len) throws OneWireIOException, OneWireException |
| Gets a block of data from the 1-Wire Network and write it into the provided array. | |
| void | dataBlock (byte[] dataBlock, int off, int len) throws OneWireIOException, OneWireException |
| Sends a block of data and returns the data received in the same array. | |
| void | setPowerDuration (int timeFactor) throws OneWireIOException, OneWireException |
| Sets the duration to supply power to the 1-Wire Network. | |
| boolean | startPowerDelivery (int changeCondition) throws OneWireIOException, OneWireException |
| Sets the 1-Wire Network voltage to supply power to a 1-Wire device. | |
| void | setProgramPulseDuration (int timeFactor) throws OneWireIOException, OneWireException |
| Sets the duration for providing a program pulse on the 1-Wire Network. | |
| boolean | startProgramPulse (int changeCondition) throws OneWireIOException, OneWireException |
| Sets the 1-Wire Network voltage to eprom programming level. | |
| void | startBreak () throws OneWireIOException, OneWireException |
| Sets the 1-Wire Network voltage to 0 volts. | |
| void | setPowerNormal () throws OneWireIOException, OneWireException |
| Sets the 1-Wire Network voltage to normal level. | |
| void | setSpeed (int speed) throws OneWireIOException, OneWireException |
| Sets the new speed of data transfer on the 1-Wire Network. | |
| int | getSpeed () |
| Returns the current data transfer speed on the 1-Wire Network. | |
Protected Attributes | |
| Integer | currentThreadHash = NOT_OWNED |
| Keeps hash of current thread for exclusive lock. | |
| Connection | conn = EMPTY_CONNECTION |
| instance for current connection, defaults to EMPTY | |
| String | portNameForReconnect = null |
| portName For Reconnecting to Host | |
| byte[] | netAdapterSecret = null |
| secret for authentication with the server | |
| boolean | useCustomSecret = false |
| if true, the user used a custom secret | |
| Boolean | multicastEnabled = null |
| indicates whether or not mulicast is enabled | |
| String | multicastGroup = null |
| The multicast group to use for NetAdapter Datagram packets. | |
| int | datagramPort = -1 |
| The port to use for NetAdapter Datagram packets. | |
Static Protected Attributes | |
| static final String | UNSPECIFIED_ERROR = "An unspecified error occurred." |
| Error message when neither RET_SUCCESS or RET_FAILURE are returned. | |
| static final String | COMM_FAILED = "IO Error: " |
| Error message when I/O failure occurs. | |
| static final Integer | NOT_OWNED = new Integer(0) |
| constant for no exclusive lock |
NetAdapter is a network-based DSPortAdapter. It allows for the use of an actual DSPortAdapter which isn't on the local machine, but rather is connected to another device which is reachable via a TCP/IP network connection.
The syntax for the selectPort(String)
command is the hostname of the computer which hosts the actual DSPortAdapter and the TCP/IP port that the host is listening on. If the port number is not specified, a default value of 6161 is used. Here are a few examples to illustrate the syntax:
<P?The use of the NetAdapter is virtually identical to the use of any other DSPortAdapter. The only significant changes are the necessity of the 'host' component (see NetAdapterHost) and the discovery of hosts on your network. There are currently two techniques used for discovering all of the hosts: The look-up of each host from the onewire.properties file and the use of multicast sockets for automatic discovery.
In the onewire.properties file, you can add a host to your list of valid hosts by making a NetAdapter.host with an integer to distinguish the hosts. There is no limit on the number of hosts which can appear in this list, but the first one must be numbered '0'. These hosts will then be returned in the list of valid 'ports' from the selectPortNames()
method. Note that there do not have to be any servers returned from selectPortNames()
for the NetAdapter to be able to connect to them (so it isn't necessary to add these entries for it to function), but applications which allow a user to automatically select an appropriate adapter and a port from a given list will not function properly without it. For example:
The multicast socket technique allows you to automatically discover hosts on your subnet which are listening for multicast packets. By default, the multicast discovery of NetAdapter hosts is disabled. When enabled, the NetAdapter creates a multicast socket and looks for servers every time you call selectPortNames()
. This will add a 1 second delay (due to the socket timeout) on calling the method. If you'd like to enable this feature, add the following line to your onewire.properties file:
The port used and the multicast group used for multicast sockets can also be changed. The group however, must fall withing a valid range. For more information about multicast sockets in Java, see the Java tutorial on networking at http://java.sun.com/docs/books/tutorial/. Change the defaults in the onewire.properties file with the following entries:
Once the NetAdapter is connected with a host, a version check is performed followed by a simple authentication step. The authentication is dependent upon a secret shared between the NetAdapter and the host. Both will use a default value, that each will agree with if you don't provide a secret of your own. To set the secret, add the following line to your onewire.properties file:
Optionally, the secret can be specified on a per-host basis by simply adding the secret after the port number followed by a colon. If no port number is specified, a double-colon is required. Here are examples:
All of the above mentioned properties can be set on the command-line as well as being set in the onewire.properties file. To set the properties on the command-line, use the -D option: java -DNetAdapter.Secret="custom secret" myApplication
The following is a list of all parameters that can be set for the NetAdapter, followed by default values where applicable.
If you wanted added security on the communication channel, an SSL socket (or similar custom socket implementation) can be used by circumventing the standard DSPortAdapter's selectPort(String)
and using the NetAdapter-specific selectPort(Socket)
. For example:
NetAdapter na = new NetAdapter();
Socket secureSocket = // insert fancy secure socket implementation here
na.selectPort(secureSocket);
For information on setting up the host component, see the JavaDocs for theNetAdapterHost
| NetAdapter | ( | ) |
Creates an instance of NetAdapter that isn't connected.
Must call selectPort(String); or selectPort(Socket);
| boolean adapterDetected | ( | ) | throws OneWireIOException, OneWireException [virtual] |
Detects adapter presence on the selected port.
true
if the adapter is confirmed to be connected to the selected port, false
if the adapter is not connected.| OneWireIOException | |
| OneWireException |
Implements DSPortAdapter.
| boolean beginExclusive | ( | boolean | blocking | ) | throws OneWireException [virtual] |
Gets exclusive use of the 1-Wire to communicate with an iButton or 1-Wire Device.
This method should be used for critical sections of code where a sequence of commands must not be interrupted by communication of threads with other iButtons, and it is permissible to sustain a delay in the special case that another thread has already been granted exclusive access and this access has not yet been relinquished.
It can be called through the OneWireContainer class by the end application if they want to ensure exclusive use. If it is not called around several methods then it will be called inside each method.
| blocking | true if want to block waiting for an excluse access to the adapter |
true
if blocking was false and a exclusive session with the adapter was aquired| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| boolean canBreak | ( | ) | throws OneWireIOException, OneWireException |
Returns whether adapter can physically support 0 volt 'break' mode.
true
if this port adapter can do break, false
otherwise.| OneWireIOException | on a 1-Wire communication error with the adapter |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| boolean canDeliverPower | ( | ) | throws OneWireIOException, OneWireException |
Returns whether the adapter can physically support strong 5 volt power mode.
true
if this port adapter can do strong 5 volt mode, false
otherwise.| OneWireIOException | on a 1-Wire communication error with the adapter |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| boolean canDeliverSmartPower | ( | ) | throws OneWireIOException, OneWireException |
Returns whether the adapter can physically support "smart" strong 5 volt power mode.
"smart" power delivery is the ability to deliver power until it is no longer needed. The current drop it detected and power delivery is stopped.
true
if this port adapter can do "smart" strong 5 volt mode, false
otherwise.| OneWireIOException | on a 1-Wire communication error with the adapter |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| boolean canFlex | ( | ) | throws OneWireIOException, OneWireException |
Returns whether the adapter can physically support flex speed mode.
true
if this port adapter can do flex speed, false
otherwise.| OneWireIOException | on a 1-Wire communication error with the adapter |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| boolean canHyperdrive | ( | ) | throws OneWireIOException, OneWireException |
Returns whether the adapter can physically support hyperdrive mode.
true
if this port adapter can do HyperDrive, false
otherwise.| OneWireIOException | on a 1-Wire communication error with the adapter |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| boolean canOverdrive | ( | ) | throws OneWireIOException, OneWireException |
Returns whether adapter can physically support overdrive mode.
true
if this port adapter can do OverDrive, false
otherwise.| OneWireIOException | on a 1-Wire communication error with the adapter |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| boolean canProgram | ( | ) | throws OneWireIOException, OneWireException |
Returns whether adapter can physically support 12 volt power mode.
true
if this port adapter can do Program voltage, false
otherwise.| OneWireIOException | on a 1-Wire communication error with the adapter |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| void dataBlock | ( | byte[] | dataBlock, |
| int | off, | ||
| int | len | ||
| ) | throws OneWireIOException, OneWireException [virtual] |
Sends a block of data and returns the data received in the same array.
This method is used when sending a block that contains reads and writes. The 'read' portions of the data block need to be pre-loaded with 0xFF's. It starts sending data from the index at offset 'off' for length 'len'.
| dataBlock | array of data to transfer to and from the 1-Wire Network. |
| off | offset into the array of data to start |
| len | length of data to send / receive starting at 'off' |
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| void endExclusive | ( | ) | [virtual] |
Relinquishes exclusive control of the 1-Wire Network.
This command dynamically marks the end of a critical section and should be used when exclusive control is no longer needed.
Implements DSPortAdapter.
| void excludeFamily | ( | int | family | ) |
Takes an integer family code to avoid when searching for iButtons.
or 1-Wire devices. If this method is used, then no devices of this family will be found by any of the search methods.
| family | the code of the family type NOT to target in searches |
Reimplemented from DSPortAdapter.
| void excludeFamily | ( | byte | family[] | ) |
Takes an array of bytes containing family codes to avoid when finding iButtons or 1-Wire devices.
If used, then no devices with family codes in this array will be found by any of the search methods.
| family | array of family cods NOT to target for searches |
Reimplemented from DSPortAdapter.
| boolean findFirstDevice | ( | ) | throws OneWireIOException, OneWireException [virtual] |
Returns true
if the first iButton or 1-Wire device is found on the 1-Wire Network.
If no devices are found, then false
will be returned.
true
if an iButton or 1-Wire device is found.| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| boolean findNextDevice | ( | ) | throws OneWireIOException, OneWireException [virtual] |
Returns true
if the next iButton or 1-Wire device is found.
The previous 1-Wire device found is used as a starting point in the search. If no more devices are found then false
will be returned.
true
if an iButton or 1-Wire device is found.| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| void freePort | ( | ) | throws OneWireException [virtual] |
Frees ownership of the selected port, if it is currently owned, back to the system.
This should only be called if the recently selected port does not have an adapter, or at the end of your application's use of the port.
| OneWireException | If port does not exist |
Implements DSPortAdapter.
| String getAdapterName | ( | ) | [virtual] |
Retrieves the name of the port adapter as a string.
The 'Adapter' is a device that connects to a 'port' that allows one to communicate with an iButton or other 1-Wire device. As example of this is 'DS9097U'.
String
representation of the port adapter. Implements DSPortAdapter.
| void getAddress | ( | byte[] | address | ) | [virtual] |
Copies the 'current' 1-Wire device address being used by the adapter into the array.
This address is the last iButton or 1-Wire device found in a search (findNextDevice()...). This method copies into a user generated array to allow the reuse of the buffer. When searching many iButtons on the one wire network, this will reduce the memory burn rate.
| address | An array to be filled with the current iButton address. |
Implements DSPortAdapter.
| boolean getBit | ( | ) | throws OneWireIOException, OneWireException [virtual] |
Gets a bit from the 1-Wire Network.
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| byte [] getBlock | ( | int | len | ) | throws OneWireIOException, OneWireException [virtual] |
Gets a block of data from the 1-Wire Network.
| len | length of data bytes to receive |
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| void getBlock | ( | byte[] | arr, |
| int | len | ||
| ) | throws OneWireIOException, OneWireException [virtual] |
Gets a block of data from the 1-Wire Network and write it into the provided array.
| arr | array in which to write the received bytes |
| len | length of data bytes to receive |
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| void getBlock | ( | byte[] | arr, |
| int | off, | ||
| int | len | ||
| ) | throws OneWireIOException, OneWireException [virtual] |
Gets a block of data from the 1-Wire Network and write it into the provided array.
| arr | array in which to write the received bytes |
| off | offset into the array to start |
| len | length of data bytes to receive |
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| int getByte | ( | ) | throws OneWireIOException, OneWireException [virtual] |
Gets a byte from the 1-Wire Network.
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| String getClassVersion | ( | ) | [virtual] |
| String getPortName | ( | ) | throws OneWireException [virtual] |
Retrieves the name of the selected port as a String
.
String
of selected port| OneWireException | if valid port not yet selected |
Implements DSPortAdapter.
| Enumeration getPortNames | ( | ) | [virtual] |
Retrieves a list of the platform appropriate port names for this adapter.
A port must be selected with the method 'selectPort' before any other communication methods can be used. Using a communcation method before 'selectPort' will result in a OneWireException
exception.
Enumeration
of type String
that contains the port names Implements DSPortAdapter.
| String getPortTypeDescription | ( | ) | [virtual] |
Retrieves a description of the port required by this port adapter.
An example of a 'Port' would 'serial communication port'.
String
description of the port type required. Implements DSPortAdapter.
| int getSpeed | ( | ) |
Returns the current data transfer speed on the 1-Wire Network.
int
representing the current 1-Wire speed Reimplemented from DSPortAdapter.
| void pingHost | ( | ) | throws OneWireException, OneWireIOException |
Sends a ping to the host, just to keep the connection alive.
Although it currently is not implemented on the standard NetAdapterHost, this command is used as a signal to the NetAdapterSim to simulate some amount of time that has run.
| void putBit | ( | boolean | bitValue | ) | throws OneWireIOException, OneWireException [virtual] |
Sends a bit to the 1-Wire Network.
| bitValue | the bit value to send to the 1-Wire Network. |
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| void putByte | ( | int | byteValue | ) | throws OneWireIOException, OneWireException [virtual] |
Sends a byte to the 1-Wire Network.
| byteValue | the byte value to send to the 1-Wire Network. |
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| int reset | ( | ) | throws OneWireIOException, OneWireException [virtual] |
Sends a Reset to the 1-Wire Network.
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Implements DSPortAdapter.
| boolean selectPort | ( | Socket | sock | ) | throws OneWireIOException, OneWireException |
New method, unique to NetAdapter.
Sets the "port", i.e. the connection to the server via an already established socket connection.
| sock | Socket connection to NetAdapterHost |
true
if connection to host was successful| OneWireIOException | If port does not exist, or unable to communicate with port. |
| OneWireException | If port does not exist |
| boolean selectPort | ( | String | portName | ) | throws OneWireIOException, OneWireException [virtual] |
Specifies a platform appropriate port name for this adapter.
Note that even though the port has been selected, it's ownership may be relinquished if it is not currently held in a 'exclusive' block. This class will then try to re-aquire the port when needed. If the port cannot be re-aquired ehen the exception PortInUseException
will be thrown.
| portName | Address to connect this NetAdapter to, in the form of "hostname:port". For example, "shughes.dalsemi.com:6161", where 6161 is the port number to connect to. The use of NetAdapter.DEFAULT_PORT is recommended. |
true
if the port was aquired, false
if the port is not available.| OneWireIOException | If port does not exist, or unable to communicate with port. |
| OneWireException | If port does not exist |
Implements DSPortAdapter.
| void setNoResetSearch | ( | ) | [virtual] |
Sets the 1-Wire Network search to not perform a 1-Wire reset before a search.
This feature is chiefly used with the DS2409 1-Wire coupler. The normal reset before each search can be restored with the 'setSearchAllDevices()' method.
Implements DSPortAdapter.
| void setPowerDuration | ( | int | timeFactor | ) | throws OneWireIOException, OneWireException |
Sets the duration to supply power to the 1-Wire Network.
This method takes a time parameter that indicates the program pulse length when the method startPowerDelivery().
Note: to avoid getting an exception, use the canDeliverPower() and canDeliverSmartPower() method to check it's availability.
| timeFactor |
|
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| void setPowerNormal | ( | ) | throws OneWireIOException, OneWireException |
Sets the 1-Wire Network voltage to normal level.
This method is used to disable 1-Wire conditions created by startPowerDelivery and startProgramPulse. This method will automatically be called if a communication method is called while an outstanding power command is taking place.
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter or the adapter does not support this operation |
Reimplemented from DSPortAdapter.
| void setProgramPulseDuration | ( | int | timeFactor | ) | throws OneWireIOException, OneWireException |
Sets the duration for providing a program pulse on the 1-Wire Network.
This method takes a time parameter that indicates the program pulse length when the method startProgramPulse().
Note: to avoid getting an exception, use the canDeliverPower() method to check it's availability.
| timeFactor |
|
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| void setSearchAllDevices | ( | ) | [virtual] |
Sets the 1-Wire Network search to find all iButtons and 1-Wire devices whether they are in an 'Alarm' state or not and restores the default setting of providing a 1-Wire reset command before each search.
(see setNoResetSearch() method).
Implements DSPortAdapter.
| void setSearchOnlyAlarmingDevices | ( | ) | [virtual] |
Sets the 1-Wire Network search to find only iButtons and 1-Wire devices that are in an 'Alarm' state that signals a need for attention.
Not all iButton types have this feature. Some that do: DS1994, DS1920, DS2407. This selective searching can be canceled with the 'setSearchAllDevices()' method.
Implements DSPortAdapter.
| void setSecret | ( | String | secret | ) |
Sets the shared secret for authenticating this NetAdapter with a NetAdapterHost.
| secret | the new secret for authenticating this client. |
| void setSpeed | ( | int | speed | ) | throws OneWireIOException, OneWireException |
Sets the new speed of data transfer on the 1-Wire Network.
| speed |
|
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter or the adapter does not support this operation |
Reimplemented from DSPortAdapter.
| void startBreak | ( | ) | throws OneWireIOException, OneWireException |
Sets the 1-Wire Network voltage to 0 volts.
This method is used rob all 1-Wire Network devices of parasite power delivery to force them into a hard reset.
| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter or the adapter does not support this operation |
Reimplemented from DSPortAdapter.
| boolean startPowerDelivery | ( | int | changeCondition | ) | throws OneWireIOException, OneWireException |
Sets the 1-Wire Network voltage to supply power to a 1-Wire device.
This method takes a time parameter that indicates whether the power delivery should be done immediately, or after certain conditions have been met.
Note: to avoid getting an exception, use the canDeliverPower() and canDeliverSmartPower() method to check it's availability.
| changeCondition |
|
true
if the voltage change was successful, false
otherwise.| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter |
Reimplemented from DSPortAdapter.
| boolean startProgramPulse | ( | int | changeCondition | ) | throws OneWireIOException, OneWireException |
Sets the 1-Wire Network voltage to eprom programming level.
This method takes a time parameter that indicates whether the power delivery should be done immediately, or after certain conditions have been met.
Note: to avoid getting an exception, use the canProgram() method to check it's availability.
| changeCondition |
|
true
if the voltage change was successful, false
otherwise.| OneWireIOException | on a 1-Wire communication error |
| OneWireException | on a setup error with the 1-Wire adapter or the adapter does not support this operation |
Reimplemented from DSPortAdapter.
| void targetAllFamilies | ( | ) |
Removes any selectivity during a search for iButtons or 1-Wire devices by family type.
The unique address for each iButton and 1-Wire device contains a family descriptor that indicates the capabilities of the device.
Reimplemented from DSPortAdapter.
| void targetFamily | ( | byte | family[] | ) |
Takes an array of bytes to use for selectively searching for acceptable family codes.
If used, only devices with family codes in this array will be found by any of the search methods.
| family | array of the family types to target for searches |
Reimplemented from DSPortAdapter.
| void targetFamily | ( | int | family | ) |
Takes an integer to selectively search for this desired family type.
If this method is used, then no devices of other families will be found by any of the search methods.
| family | the code of the family type to target for searches |
Reimplemented from DSPortAdapter.