Java/Comunicazione seriale: differenze tra le versioni

Il contenuto del file di proprietà è in genere una sola riga, il nome della classe Java con il driver nativo, ad esempio:

 

 

Il seguente è un hack che permette di distribuire JavaComm via Web Start ignorando che il cervello di proprietà morti file. Si è gravi inconvenienti, e potrebbe non riuscire con le nuove uscite JavaComm - Sun dovrebbe mai venire intorno e fare una nuova versione.

In primo luogo, disattivare il gestore della sicurezza. Alcuni programmatori Doofus a Sun ha deciso che sarebbe bello nuovo e di nuovo per verificare l'esistenza del temuto''javax.comm.properties''file, anche dopo che è stato caricato inizialmente, per nessun altro motivo apparente, rispetto al controllo per la file.

 

 

Poi, quando si inizializza l'API JavaComm, inizializzare il driver manualmente:

 

 CommDriver CommDriver = (CommDriver) Class.forName (driverName). NewInstance ();

 commDriver.initialize ();</ source>

 

Enumerating and selecting the desired port identifier is typically done in one loop:

import javax.comm.*;

import java.util.*;

//

// Use port identifier for acquiring the port

...

 

 

Once a port identifier has been found, it can be used to acquire the desired port:

//

// Use port identifier for acquiring the port

// Now we are granted exclusive access to the particular serial

// port. We can configure it and obtain input and output streams.

...

 

 

As part of the initialization process the Input and Output streams for communication will be configured in the example.

import java.io.*;

...

if (is != null) is.close();

if (os != null) os.close();

 

=== Simple Data Transfer ===

* Explain how to mix binary and character I/O over the same stream

* Fix the example to use streams}}

// Write to the output

os.print("AT");

is.readLine(); // First read will contain the echoed command you sent to it. In this case: "AT"

is.readLine(); // Second read will remove the extra line feed that AT generates as output

 

==== Simple Reading of Data (Polling) ====

If you correctly carried out the write operation (see above) then the read operation is as simple as one command:

 

 

==== Problems with the simple Reading / Writing ====

 

==== Setting up a serial Event Handler ====

import javax.comm.*;

 

}

}

Once the listener is implemented, it can be used to listen to particular serial port events. To do so, an instance of the listener needs to be added to the serial port. Further, the reception of each event type needs to be requested individually.

SerialPort port = ...;

...

port.notifyOnRingIndicator(true);

<- other events not used in this example */

 

 

 

A ring buffer as such is nothing special, and has no special properties regarding threading. It is just that this simple data structure is used here to provide data buffering. The implementation is done so that access to this data structure has been made thread safe.

/**

* Synchronized ring buffer.

}

}

With this ring buffer one can now hand over data from one thread to another in a controlled way. Any other thread-safe, non-blocking mechanism would also do. The key point here is that the write does not block when the buffer is full and also does not block when there is nothing to read.

 

 

The skeleton event listener proposed a method <code>outputBufferEmpty()</code>, which could be implemented as it follows.

RingBuffer dataBuffer = ... ;

 

{{TODO}}

 

==== Reading of Data ====

 

The following example assumes that the data's destination is some file. Whenever data becomes available it is fetched from the serial port and written to the file. This is an extremely simplified view, because in reality one would need to check the data for an end-of-file indication to, for example, return to the modem command mode.

import javax.comm.*;

 

if (is != null) is.close();

if (port != null) port.close();

 

=== Handling multiple Ports in one Application ===