RomRaider Logger java.lang.NullPointerException

dschultz · **Posted:** Fri Nov 26, 2021 6:49 pm

I find it odd that just unplugging the J2534 cable causes it to not even report all the possible J2534 drivers you have installed.
Mine does not do this which is going to make it hard to troubleshoot. My system has at least one built in COM port, does yours?
If not, can you plug in a USB-to-Serial or a USB-KKL cable to create one and try the test again with the J2534 disconnected?
If you have no USB COM devices at all, you can load a software driver to emulate one.
http://com0com.sourceforge.net/

dschultz · **Posted:** Fri Nov 26, 2021 9:58 pm

dschultz wrote:

My system has at least one built in COM port, does yours?

I think this is the key. The QueryManager was modified such that if there are no COM ports on your system it will never do anything but sit and wait for a COM port to appear. This negates the whole purpose of putting the COM port refresher in the background and proceeding to attempt another connection type.

Code:

[main] - Timeout while waiting for serial port refresher - continuing anyway...

I'll have to push a new version to undo this change:

Code:

if (!settings.isLogExternalsOnly() &&  (target != null && settings.getLoggerPort() != null && doEcuInit(target))) {

"settings.getLoggerPort() != null" will never have a value on a system with no ports, so it will never connect to the ECU.

Pytrex · **Posted:** Fri Nov 26, 2021 10:03 pm

dschultz wrote:

My system has at least one built in COM port, does yours?

I think this is the key. The QueryManager was modified such that if there are no COM ports on your system it will never do anything but sit and wait for a COM port to appear. This negates the whole purpose of putting the COM port refresher in the background and proceeding to attempt another connection type.

Code:

[main] - Timeout while waiting for serial port refresher - continuing anyway...

I'll have to push a new version to undo this change:

Code:

if (!settings.isLogExternalsOnly() &&  (target != null && settings.getLoggerPort() != null && doEcuInit(target))) {

"settings.getLoggerPort() != null" will never have a value on a system with no ports, so it will never connect to the ECU.

Oooh great find! I’ll still test it out, as my laptop doesn’t have any COM ports. So I definitely think this is the issue haha But it’ll be nice to confirm it firsthand.

Edit;
As expected, you were right haha By having a VAG-COM cable connected to my laptop, the V8.0 logger ran like a champ! But then obviously, the logger realized a COM port was open and continually attempted to try running NCS via VAG-COM rather than using the comparatively beefy OP2 lol

Pytrex · **Posted:** Sun Nov 28, 2021 8:36 am

Seriously, great job dschultz! the v0.8.1 logger works perfectly! I really appreciate you taking the time to figure out what could've been causing such an issue, as I had no ideas about why RR was acting in such a way.

amtech · **Joined:** Sun Nov 28, 2021 9:51 am **Posts:** 1

hello,
did you find a solution for the issue with the Tactrix cable?
Even my logger is sitting there without finding any cable ... it shows "stopped" and nothing else.

If there isn't a solution yet , do you have maybe a previous version of the logger to be used temporarily?

thanks a lot

Pytrex · **Posted:** Sun Nov 28, 2021 12:43 pm

amtech wrote:

hello,
did you find a solution for the issue with the Tactrix cable?
Even my logger is sitting there without finding any cable ... it shows "stopped" and nothing else.

If there isn't a solution yet , do you have maybe a previous version of the logger to be used temporarily?

thanks a lot

Yup! Dschultz fixed the issue in the new release -> viewtopic.php?f=2&t=19056

RomRaider

Forum rules

RomRaider Logger java.lang.NullPointerException

Who is online