Free telegram : PZD without reference

Dear,

I use free telegram with S7-1200 PLC and G120C drive. 

For reference value it is not problem with the following thing : 

From DPRD_DAT then (INT TO REAL ("value") / 16384.0) * reference

But for an unreferenced value, how to do ? For exemple with r0039 (kWh) ?    

See attachment.

Thank you.

Hi,

I know that I heard already of that topic with r0039 some time ago. 

I am not 100% sure but I think the value that you will get when interconnecting the BICO is in the unit Ws. And it is transferred maybe without a reference. So check out the Integer value that you receive and look if it makes sense to be in Ws.

 Y have 32767 as value in the INT. But in the drive i have 0,00kWh. 

RB91

Hi,

I know that I heard already of that topic with r0039 some time ago. 

I am not 100% sure but I think the value that you will get when interconnecting the BICO is in the unit Ws. And it is transferred maybe without a reference. So check out the Integer value that you receive and look if it makes sense to be in Ws.

Sounds like the value is scaled 0-65535 for -100 to +100 % kWh, which puts 0 kWh @ 32767. 

AutoGen_6296554

 Y have 32767 as value in the INT. But in the drive i have 0,00kWh. 

RB91

Hi,

I know that I heard already of that topic with r0039 some time ago. 

I am not 100% sure but I think the value that you will get when interconnecting the BICO is in the unit Ws. And it is transferred maybe without a reference. So check out the Integer value that you receive and look if it makes sense to be in Ws.

A look in the SINAMICS G120C list manual (https://support.industry.siemens.com/cs/ww/en/view/109751318) tells us on page 32 the parameter r39  is a REAL value (FloatingPoint32), see attachment.

I'm not sure if it uses the unit kWh or Ws. But a quick test should show which one is used with the communication.

Based on miami's post above about r39 being FP32, your telegram configuration needs to change.

New telegram configuration

Slot  Parameter

 3    r66
 4    r27
 5    r32
6&7   r39
 8    r2131
 9    r2132

Then assign a tag of type real to IDxxxx which points to PZD 6 and the kWh value will appear and should match what you see in the drive using starter / startdrive.

Hello, i have changed the telegram. See below. 

The PZD 8 = 32767 and PZD9 = -128 . 

0_Einstein

Based on miami's post above about r39 being FP32, your telegram configuration needs to change.

New telegram configuration

Slot  Parameter

 3    r66
 4    r27
 5    r32
6&7   r39
 8    r2131
 9    r2132

Then assign a tag of type real to IDxxxx which points to PZD 6 and the kWh value will appear and should match what you see in the drive using starter / startdrive.

 

Ok, you did not really listen to me and just mashed everything together and stuck r39 at the end.

r39 is not an INT.  r39 is a REAL and does not require any conversion.  It occupies 2 words (4 bytes), and can be read directly from the telegram address IDxxxx for (in the latest post below) PZD8's starting address.

AutoGen_6296554

Hello, i have changed the telegram. See below. 

The PZD 8 = 32767 and PZD9 = -128 . 

0_Einstein

Based on miami's post above about r39 being FP32, your telegram configuration needs to change.

New telegram configuration

Slot  Parameter

 3    r66
 4    r27
 5    r32
6&7   r39
 8    r2131
 9    r2132

Then assign a tag of type real to IDxxxx which points to PZD 6 and the kWh value will appear and should match what you see in the drive using starter / startdrive.

 

 

Can i use the function DPRD_DAT ("HW extension telegram" . byte "xx") ? To read the real ?

Serge