Hi All,

How come the time in the system log is different to what the system actually is?

The local and RTC are correct, but the time in the system log in Studio is 13 hours ahead.

Cheers,
Mike

@Jan-Reitinger Hi Jan,

All sorted, thank you.

Cheers,
Mike

sorry, I've just worked it out using the Bitwise demultiplexer

@cechurat Hi Tomas,

Thank you, that lead me down the right path to fix it.

New error! What does this mean?

Cheers,
Mike

I'm sure how or if it's related but this seemed to go away after I removed the HMI block from the exec.

Cheers,
Mike

Hi All,

Is this something to be worried about? I'm not sure what it means.

Cheers,
Mike

Hi All,

What is error 106 that is causing the configuration not to be created?

I've also had error 103

It can't be a license issue as I have the required licensing installed.

Cheers,
Mike

Hello All,

Is there, or does anyone have an example of using an MCP41X digital 257 position potentiometer with SPI?

Cheers,
Mike

sorry, I've just worked it out using the Bitwise demultiplexer

Hi All,

I have a Modbus register that is 2bytes, this contains component status information. How do I break it down into bits to make it usable.

Here is the bit break down.

For example I have a value from the register of 23, but I'm not sure how to translate it into the bit table above.

Cheers,
Mike

@cechurat Hi Tomas,

I will try and record this this week, sorry for the delay.

Cheers,
Mike

@cechurat Hi Tomas,

My versions are below.

The parse error has gone now. What seems to happen now is after I set the connect strings in the HMI configuration, it doesn't save them so are always blank when I open it again.

Thanks for your help with this

I'm also getting this for the logger too, but can't work out why, any ideas?