Configuring Telegram 999 from IOP & Temp Scaling

I'm running a G120 5.5hp VFD with IOP 2 controlled by an Allen-Bradley Controllogix PLC. Two questions:

1) My Startdrive decided to stop downloading to the VFD and started crashing everytime I try, so until I can get that sorted, I need to configure Telegram 999 via IOP2.  I've gotten everything to work using the existing parameters under r2067 (2 control words, 8 status words).  However, I'd like to add 3 more status values to the telegram, and cannot find a parameter that allows me to adjust the number of variables sent from VFD.  Is there a way to increase this number from 8 using the IOP?

2) I am reading r0035 Mot Temp out of the drive, and scaling with p2006.  Reference temp is set to 212.0 in p2006. No matter what I do though, in the PLC I cannot get the value to scale properly. I'm also reading torque, current, speed and power, and those all scale perfectly fine using the exact same equation (different references obviously).  I've looked over the program to exhaustion now, and can't find a problem in the PLC. Is there something different about temperature calculations/scaling than the others?

Thanks!

My recommendation is to install Starter with G120 support and (optional) help system.

Then you can go online with starter, find accessible nodes, accept the G120 into the Starter project, and then upload from VFD to PG/PC.  At that point, you should save the project.

Then go offline and configure the telegram as required.  Go online and download to the G120.  RAM to ROM and upload back to Starter / PG/PC.

That is less error prone than using an IOP2.  Takes a long time to download starter, install software, and all that.  However, you can be pressing IOP2 buttons while waiting for the downloads or install to complete.  If you get the IOP2 manual entry to work before Starter is ready, at least you can upload to starter to confirm everything is as it should be in the telegram.

User62719

I'm running a G120 5.5hp VFD with IOP 2 controlled by an Allen-Bradley Controllogix PLC. Two questions:

1) My Startdrive decided to stop downloading to the VFD and started crashing everytime I try, so until I can get that sorted, I need to configure Telegram 999 via IOP2.  I've gotten everything to work using the existing parameters under r2067 (2 control words, 8 status words).  However, I'd like to add 3 more status values to the telegram, and cannot find a parameter that allows me to adjust the number of variables sent from VFD.  Is there a way to increase this number from 8 using the IOP?

2) I am reading r0035 Mot Temp out of the drive, and scaling with p2006.  Reference temp is set to 212.0 in p2006. No matter what I do though, in the PLC I cannot get the value to scale properly. I'm also reading torque, current, speed and power, and those all scale perfectly fine using the exact same equation (different references obviously).  I've looked over the program to exhaustion now, and can't find a problem in the PLC. Is there something different about temperature calculations/scaling than the others?

Thanks!

The p2006 =100.0 is only true in SI units, in US units it's 212.0.  At least this is the parameter I get when reading out of the drive when switching to US units.

Strangely, now that I repaired my TIA installation I can go online in StartDrive, and under all parameters I see the motor temp alarm thresholds of 130F and 145F respectively.  However, the manual says these should be 130C and 145C.

Can I assume that these numbers were simply not converted properly by the drive, and I can up the 130F and 145F values to their celsius equivalents in Fahrenheit?  We're having an issue that the motor keeps stopping with an overtemp fault, and I'm wondering if this is why. 

Based on this I'm wondering if there is some scaling issue due to the drive temp reference internally.

Screenshot of your scaling logic for the temperature parameter?  It should be arriving to the PLC as -200% to +200% of the reference temperature.  Use the value in p2006 to scale accordingly.

100% = 212.0 = 16384 from the drive
-100% = -212.0 = -16384 from the drive

200% = 424.0 = 32768 from the drive
-200% = -424.0 = -32767 from the drive

Scaling should be set up per the expected range of either +/-100%, 0-100%, or something beyond.

I tend to set p2006 to the maximum temperature, and then rounded up to the next logical temperature with 2 0's, like 155 would cause me to put 200 or 300 in p2006.  If it might reach 255, I might go for 500 in p2006.

The key is to use the p2006 value to both scale and range the value received from the drive.

If I am using norm_x, with say 212 in p2006 and I do not expect > 150 actual temperature, I would normalize using 0 and 16384.  Then I would use scale_x to convert the normalized result to either C or F based on 0-100 or 32-212 (or 0-212 if Siemens didn't store the value for 0 C as 32F and scale the value sent via telegram that way).

User62719

The p2006 =100.0 is only true in SI units, in US units it's 212.0.  A least this is the parameter I get when reading out of the drive.

2 Options:

Go through the commissioning wizard again, but this time, while offline with the drive, set it to SI units so everything is in sync with SI units.  Then go through it again and switch units back.  Hopefully that puts the values displayed and measured in the same scale.

If the overtemp values are showing F in the units column, change them to equivalent F values.

The 2nd method might miss something, but should get your drive to stop faulting for overtemp just because it's a little warm to the touch but not quite so hot it melts your skin off.

User62719

Einstein, thanks for that helpful info.  I edited my post above, any take on the conversion issues?
 

haha ok, thanks.

3 more quick questions:

1) The motor insulation rating is NEMA F, the manual suggests entering 40C (104F) into parameter p625, which is the motor nameplate rating.  However the description is "motor ambient temp at commisioning", which is here around 80F.  Which parameter should be entered here?  I've noticed when the motor hasn't been running, the VFD starts with this value for the motor temp, so it would make more sense to enter the actual temp, correct?

2) Some parameters are specified as "referred to the ambient temperature", i.e. p0627. Does this mean "relative to", like the stator overtemp value is actually p0627 + p0625?

3) Is there a standard password for the service parameters? I can't access them in Startdrive without a password.

In every equation you have with a 1 or 16384, add .0 (1.0 or 16384.0) so the block is not forced to convert between int and real as it sees fit.

Mixing datatypes in calculations is not good.

Also, you are using CPT where the NORM_X and SCALE_X blocks were built to handle that type of calculation - scaling data.

The use of NORM_X also allows different types of end-user units from the same normalization output.

For example, 0-100% : 0-xxxPA : 0-yyy psi 

It also removes the problems associated with implicit datatype conversions possibly affecting results.

With a reference temperature of 311.0F, 0-16384 => 16384 counts = 311.0F.  Have you looked up the function chart for the motor temperature calculation used for internal calculations?  It might help you understand what is going on.

User62719

Hmm, looks like I still have the temperature scaling issue.  Everything else other than temperature scales properly. See attached.