Hi All

I am working with the new G120X inverter and s7-1200 which is not integrated in TIA startdrive you have to use use a gsdml file

I want to use telegram 352 but I need 2 extra words to read power and voltage the only thing I can see in the modules is supplementary data but there doesn't seem to be a way of extending the telegram like the normal G120(CU240)

does anyone know how to extend the telegram and map the extra words as power and voltage for the S7-1200 to read with this drive

Regards

Mel

Dear Mel,

You can add a supplementary data PZD 2/2.

 Hi Mel, how did you manage to do it?

Mel

Hi All

I am working with the new G120X inverter and s7-1200 which is not integrated in TIA startdrive you have to use use a gsdml file

I want to use telegram 352 but I need 2 extra words to read power and voltage the only thing I can see in the modules is supplementary data but there doesn't seem to be a way of extending the telegram like the normal G120(CU240)

does anyone know how to extend the telegram and map the extra words as power and voltage for the S7-1200 to read with this drive

Regards

Mel

Hi 

I added a supplementary telegram in the drive hardware configuration and  used Getio to read the data from the supplementary telegram

I mapped the parameters in the drive to PZD words using P2051

regards

Mel

Can you not use Free Telegram (Telegram 999)? By default Free Telegram is 8/8 on G120X (comparing to telegram 352 which is 6/6, so you can squeeze more data). Yes you have to configure the drive comms yourself but that's what siemens is pushing for with the "novel" G120X system.

I'm looking for a solution myself to read an extra up to 80 reals outside the regular telegram communication, and it looks like a risky drive to my goal.

As far as I'm aware G120X is never going to be implemented in Tia Portal/Start drive, all the information available for the drive is on Micro Size screen (assuming you use IOP2) or as you guessed, Siemens Support if you are lucky enough.

Hi 

yes you can use a free telegram 

regards

Mel

I have not tried this with StartDrive, but with Starter, the tip I received from Siemens Sinamics Support was to configure the telegram closest to the end resulting telegram, then select Free Telegram 999.

Starter would leave all the previously configured telegram BICO interconnections, saving you time with just configuring what was different or new. 

Tom_91

Can you not use Free Telegram (Telegram 999)? By default Free Telegram is 8/8 on G120X (comparing to telegram 352 which is 6/6, so you can squeeze more data). Yes you have to configure the drive comms yourself but that's what siemens is pushing for with the "novel" G120X system.

I'm looking for a solution myself to read an extra up to 80 reals outside the regular telegram communication, and it looks like a risky drive to my goal.

As far as I'm aware G120X is never going to be implemented in Tia Portal/Start drive, all the information available for the drive is on Micro Size screen (assuming you use IOP2) or as you guessed, Siemens Support if you are lucky enough.

Unfortunately g120x cannot be used with Startdrive or starter

but  picking the closest telegram and the and then changing it to a free telegram may work from the IOP

regards

Mel

So finally I could get it done by extending Telegram 325, with a PZD 2/4. It could have been done with telegram 999, but it was easier to do with the telegram extension so that I don't have to re-configure the typical words.

p922 = 999 (telegram 999) (Extension of p2079)

p2079 = 352

My real problem was getting the energy consumption, wich takes a double word and has to be wired in 2061 (to the next available slot, carefully not to override any word from standard 352). I said problem because it cannot be read as bytes, there is no way. I tried everything. Siemens support suggested using SinaPara to read it and it worked.

So basically I read the whole telegram with DPRD_DAT and put it in a byte array except for the energy which has to be read with SinaPara (beause its a real coming from a double word, strange).

Regards

Glad you got it working, but I am confused.  Are you saying you could add the energy to the PZD 2/4 extension but could not accept it on the PLC end of things?

Jorge KW

So finally I could get it done by extending Telegram 325, with a PZD 2/4. It could have been done with telegram 999, but it was easier to do with the telegram extension so that I don't have to re-configure the typical words.

p922 = 999 (telegram 999) (Extension of p2079)

p2079 = 352

My real problem was getting the energy consumption, wich takes a double word and has to be wired in 2061 (to the next available slot, carefully not to override any word from standard 352). I said problem because it cannot be read as bytes, there is no way. I tried everything. Siemens support suggested using SinaPara to read it and it worked.

So basically I read the whole telegram with DPRD_DAT and put it in a byte array except for the energy which has to be read with SinaPara (beause its a real coming from a double word, strange).

Regards

Oh no, I could finally read the telegram extension with the PLC. I do it the same way as the standard 352 Telegram, with DPRD_DAT, except for the energy (or any real double word) which I could only read with SinaPara, which is a bit messy and the program looks really ugly.

It took me a while to get this because in the G120X you configure only one extended telegram (the same way as a G120C but from the IOP panel) whereas from the plc side I have two telegrams, each with a different HW_ID: the Standard 352, and the extension PZD 2/4.

I don't know if you where asking me that

If you are using profinet communications with the G120X, you do not need to do the DP.._DAT calls to read/write data.

Also, if the extended telegram is at least 4 bytes long to contain the energy Real data, you can accept that into the PLC as "Real" starting at the address of the PZD receive (plc side).  It may need to be scaled compared to reading it via acyclic where you can read it is a Real directly.

Jorge KW

Oh no, I could finally read the telegram extension with the PLC. I do it the same way as the standard 352 Telegram, with DPRD_DAT, except for the energy (or any real double word) which I could only read with SinaPara, which is a bit messy and the program looks really ugly.

It took me a while to get this because in the G120X you configure only one extended telegram (the same way as a G120C but from the IOP panel) whereas from the plc side I have two telegrams, each with a different HW_ID: the Standard 352, and the extension PZD 2/4.

I don't know if you where asking me that

You mean using the process Image to map the drive values?

I don't like that because I have 20 drives and I prefer to use data encapsulation so that I can use the telegram as one data structure as input to my FB, instead of having FBs with 10 different inputs, which implies more work.

Let's say your Telegram process image Input starts at I300.0, is 8 words (16 bytes) long, and Output starts at Q300.0, is 6 words (12 bytes) long.

P#IX300.0 BYTE 16 is the input to your FB for inputs. P#QX300.0 BYTE 12 for outputs.

That's pretty encapsulated, but I get what you are saying.  The only thing is, your PLC is already providing the telegram data in a deterministic manner every PN update.  You are doing the work twice.

I have never wiresharked a session where the work was done twice like this, but suspect it adds traffic to the PN network.

If you are using PB, ignore everything I've said.

Jorge KW

You mean using the process Image to map the drive values?

I don't like that because I have 20 drives and I prefer to use data encapsulation so that I can use the telegram as one data structure as input to my FB, instead of having FBs with 10 different inputs, which implies more work.

New question published by guimbastos is split to a separate thread with the subject G150C not able to access these parameters.

Best regards
Jen_Moderator