"another process is accessing the bl-net"

[berwinter]

"another process is accessing the bl-net"

[berwinter]

Could you please try to set the port to 80? The CMI doesn't have an dedicated port for datalogging (WinSOL). All data is transferred through port 80.

[nils50122]

Now i become an next error "Device with code 0x87 and CAN id 1 not supported" after this, the same another process is accessing the bl-net.

[berwinter]

Currently the dataset format for a device with the code 0x87 is unknown. Is this your upgraded CMI and uvr16x2 with 64 datasets? Maybe TA gave it a new device code in order to differentiate between the old and new implementation.

[nils50122]

Yes, its the UVR16x2 with FW 1.22 and i think with 64 datasheets.
I would be very happy when you integrate the new datastream to your logger.

[nils50122]

Any news? For me the implemation of an UVR16x2 into DataLoggerPro is important.

[NoelHendrikx]

@berwinter :
I also upgraded my UVR and receive the same error message: "Device with code 0x87 and CAN id 1 not supported". Any chance where I can find the new device code?

I dived into the code and saw 3 constants:
const UVR = 0x80;
const CAN_BC = 0x84;
const CAN_EZ = 0x85;

I assume the new firmware will result in a new constant, right? The question is how to get the new value.

[NoelHendrikx]

emabled debug flag, output of dump:

#0 /share/MD0_DATA/Web/uvr/lib/backend/cmi-parser.inc.php(82): CmiDataset->getFrameId()↵#1 /share/MD0_DATA/Web/uvr/lib/backend/cmi-parser.inc.php(164): CmiDataset->getFormat()↵#2 /share/MD0_DATA/Web/uvr/lib/backend/cmi-connection.inc.php(103): CmiParser->addDataset('C\x00\x01\x87\x00\x00\x00\x00\x01\x01\x04\x00\x00\x00\x00...')↵#3 /share/MD0_DATA/Web/uvr/lib/backend/cmi-connection.inc.php(44): CmiConnection->getCount()↵#4 /share/MD0_DATA/Web/uvr/latest.php(25): CmiConnection->getLatest()↵#5 {main}

[berwinter]

Continue in #22 ...