jSerialComm | Platform-independent serial port access for Java | Wrapper library

I've found a workaround, that seems to be working. I've just created an empty compile configuration.

I managed to solve the problem by making a TimeSeries instead of a XYSeries, then i just scanned the incoming time String from arduino and parse it to a Date using:

It's not really clear what you're asking: you already have all the pieces.

I'm not familiar with jSerialComm (in particular how it manages threading), but your JavaFX application will look like this:

Take a look at LinkedBlockingDeque or any other class that implements BlockingQueue. They have a take() method that blocks until the queue has an element available. As elements become available the take() method unblocks, and allows the processing code to execute.

I did something similar when I was waiting on serial data as I wanted to queue it for processing and process it sequentially.

In your listener class you would put elements into the queue:

Neither the current source code nor the API documentation has such a feature.

Fazecast/jSerialComm
public final void waitForSerialEvent() throws Exception

Windows:
JNIEXPORT jboolean JNICALL Java_com_fazecast_jSerialComm_SerialPort_configEventFlags(JNIEnv *env, jobject obj, jlong serialPortFD)
JNIEXPORT jint JNICALL Java_com_fazecast_jSerialComm_SerialPort_waitForEvent(JNIEnv *env, jobject obj, jlong serialPortFD)

Posix:
JNIEXPORT jboolean JNICALL Java_com_fazecast_jSerialComm_SerialPort_configEventFlags(JNIEnv *env, jobject obj, jlong serialPortFD)
JNIEXPORT jint JNICALL Java_com_fazecast_jSerialComm_SerialPort_waitForEvent(JNIEnv *env, jobject obj, jlong serialPortFD)

Documentation:
Home - jSerialComm
API Documentation
Class SerialPortEvent
Class SerialPortIOException

@manuignatius is right, Groovy complains about this when there is a syntax error in a dynamically loaded Groovy class.

To get a more detailed stack trace on the error, you can manually invoke the Groovy compiler. Set your CLASSPATH environment variable to include all the jars in the lib folder in your local UnetStack installation. Then simply run groovyc MyModemDriver.groovy, and it should show you compilation errors, if any. The compiled .class file that is produced on successful compilation can then be copied to the classes folder in UnetStack/modem instead of the source code.

The maven-shade-plugin is much more powerful for create an Uber jar or fat jar and is the preferred plugin for this task for over ten years. https://maven.apache.org/plugins/maven-shade-plugin/examples/executable-jar.html describes how you should specify the mainClass.

You did not explain the protocol but I suggest to look it up. Presumably these are control characters or like a comment suggests binary data. You create a String from a byte buffer without an encoding so this also depends on your environment/ JVM's default encoding.

Try treating the first and the last two bytes as specified in the protocol in use for your project. It might also be related to jSerialComm not removing serial signalling, e.g. handshake, EOT and such.

If you're reverse-engineering the protocol instead maybe also try another library like RxTx to see if the bytes stay the same.

To inspect the bytes safely use for example BigInteger to print out a Hex-String instead:

Not sure if any of this works (can't test atm), but I hope it does:

• You could maybe look up the name in Device Manager -> Ports;

• You can try running this and see what it says: