drunsinn

A professional will probably have more success than us poking around in the dark. You might also add that one part of the key is the date as well as...

Oh, that seems to be a bug that was introduced with #40. I will look into it and get back to you.

Can you please check if there are any warnings or errors in the log?

Ok, this seems to be more of a problem with the documentation than with th e code. To get the same results with `read_plc_memory` and `read_data_path` you have to adjust...

@npalmerDNX as mentioned in an earlier comment, the addressing works different between the data_path and plc_memory. In the case of a WORD, the factor is two.  In earlier versions...

This is very strange. If you look at https://github.com/drunsinn/pyLSV2/blob/dc06e43c1f826be84169fb6b6058f804fc689688/tests/test_plc_read.py#L112 you can see the test I added to make sure the memory addressing works as intended. I would have expected this...

I still quite follow your reasoning. According to the memory tables on the control the address values are correct. If you check the screenshot I posted [here](https://github.com/drunsinn/pyLSV2/issues/48#issuecomment-1701545091), word 11 is...

I interpreted the blue column numbers a bit differently. Since I have no manual I assume that these numbers count the number of bytes from the start of memory. The...

Hello @npalmerDNX thank you for the testing you did. To be honest, most of the testing I did was with a programming station and not a real machine. I expect...

Sounds reasonable. Taking into account issue #55 a rework of the logging concept might be in order. Either by reducing most/all logging levels or by adding a debug mode that...