Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

EASYSCREEN - Displaying reals and integers

Created by: Clive Thorne at: 7/18/2013 3:48 PM (17 Replies)

Rating (0)

Thanks 1

Result pages:: |; 1 | 2; |

18 Entries

Entries per page: 10 | all

7/18/2013 3:48 PM	Rate (0)
Clive Thorne Posts: 18 Rating: (0)	I want to display values from the PLC via EasyScreen. Case 1: ======= Value is a floating point value in the PLC main memory area. EG MD1428. This displays correctly if looked at as a floating point in an S7 variable table. If I try to display it directly as a real value, eg: DEF Rot_Pos2 = (R3 / / /"","REAL Direct","" /wr1,fs1 / /"MD1428" /20,120,100 /150,120,100) then I get a silly value displayed. I can get around this by copying the value from PLC main memory to a DB location, and then displaying the DB location as a real,eg: DEF Rot_Pos = (R3 / / /"","REAL via DB","" /wr1,fs1 / /"DB300.DBR0" /20,100,100 /150,100,100) CHANGE() Test = RNP("MD1428") WNP ("DB300.DBD0", Test) END_CHANGE Obviously I could also save the value in a DB as a real within the PLC, but that's not how its done at the moment. Does anyone know an easier way to do this? UPDATE: Asmall success!! The following line: DEF Rot_Pos2 = (R3 / / /"","REAL Direct","" /wr1,fs1 / /"MD1428:REAL" /20,120,100 /150,120,100) will allow me to display a real value directly from the PLC main memory. I stumbled across this in the standard "Leaktest" example. This is not mentioned at all in the manual(09/2011), so I'm not sure if it is new feature or just a bad manual. Case 2: ======= Value is an 32 bit integer in the PLC If I display it directly then it's OK, eg: DEF MD1404_dir = (I / / /"","MD1404 Direct","" /wr1,fs1 / /"MD1404" /20,180,100 /150,180,100) If I display it indrectly, eg: DEF MD1404_indir = (I / / /"","MD1404 inDirect","" /wr1,fs1 / / /20,220,100 /150,220,100) CHANGE() MD1404_indir = RNP("MD1404") ; (MD1404_indir = "MD1404" gives the same result) END_CHANGE Then it displays the correct value for positive values but silly values if MD1404 is negative. Again, I could get around this by storing the value as a real in a DB from within the PLC, but for various reasons I'd prefer to do this within EasyScreen Does anybody know a way around this? Many thanks in advance, Clive Thorne.
Clive Thorne Posts: 18 Rating: (0)	Last edited by: Clive Thorne at: 7/24/2013 5:59 PM
Suggestion To thank Quote Answer

7/19/2013 9:15 AM	Rate (0)
Gorka Herranz Posts: 38 Rating: (0)	For case 2 I attach you in a pdf wher you can find any combination for Integer variable type. For the first case I will have to do many test. Thanks. Attachment Commissioning Manual Basesoftware and operating software.pdf (238 Downloads)
Gorka Herranz Posts: 38 Rating: (0)
Suggestion To thank Quote Answer

7/22/2013 6:28 PM	Rate (0)
Clive Thorne Posts: 18 Rating: (0)	Gorka, Thanks for this. However I still can't see the problem. I have a 32 bit signed integer in the PLC (defined as DINT), and the "I" type in the display line also means a 32 bit signed integer. This works perfectly if I specify the source directly in the definition/display line. The problem arises if I do the indirect read to the MD1404_Indirect variable using the RNP function. Notionally I am still copying a 32 bit signed integer to another 32 bit signed integer, but it does not display correct negative values. It seems to me that something in the process of the RNP corrupts or changes the format of the data that it writes to the displayed variable. Thanks again.
Clive Thorne Posts: 18 Rating: (0)	Last edited by: Clive Thorne at: 7/22/2013 6:31 PM
Suggestion To thank Quote Answer

7/23/2013 11:22 AM	Rate (0)
Gorka Herranz Posts: 38 Rating: (0)	Good morning Clive, I will do many test when I have a CNC free. I hope to find or at least find help or any way to help you. Thanks.
Gorka Herranz Posts: 38 Rating: (0)
Suggestion To thank Quote Answer

7/23/2013 10:02 PM	Rate (0)
SteveA Posts: 297 Rating: (41)	You could try explicitly setting the variable type as: Variable type INTEGER The following extensions for determining the display in the input/output field and the memory utilization are possible for the "INTEGER" type: 2nd character in the extension data type Display format B Binary D Decimal signed H hexadecimal No data Decimal signed 3rd and/or 4th character in the extension data type Memory utilization B Byte W Word D Double Word BU Byte, Unsigned WU Word, Unsigned DU Double word, Unsigned Valid INTEGER type specifications: IB Integer variable 32 bits in binary notation IBD Integer variable 32 bits in binary notation IBW Integer variable 16 bits in binary notation IBB Integer variable 8 bits in binary notation I Integer variable 32 bits in decimal notation signed IDD Integer variable 32 bits in decimal notation signed IDW Integer variable 16 bits in decimal notation signed IDB Integer variable 8 bits in decimal notation signed IDDU Integer variable 32 bits in decimal notation unsigned IDWU Integer variable 16 bits in decimal notation unsigned IDBU Integer variable 8 bits in decimal notation unsigned IH Integer variable 32 bits in hexadecimal notation IHDU Integer variable 32 bits in hexadecimal notation IHWU Integer variable 16 bits in hexadecimal notation IHBU Integer variable 8 bits in hexadecimal notation So, try IDD instead of just I For the REAL Memory variable, that might not be supported. They list: PLC data Byte y bit z of data block x DBx.DBXy.z Byte y of data block x DBx.DBBy Word y of data block x DBx.DBWy Double word y v. of data block x DBx.DBDy Real y of data block x DBx.DBRy Flag byte x bit y Mx.y Flag byte x MBx Flag word x MWx Flag double word x MDx Input byte x bit y Ix.y or Ex.y Input byte x IBx or EBx Input word x IWx or EWx Input double word x IDx or EDx Output byte x bit y Qx.y or Ax.y Output byte x QBx or ABx Output word x QWx or AWx Output double word x QDx or ADx String y with length z from data block x DBx.DBSy.z You could try MR instead of MD, but it probably won't work... HTH, SteveA
SteveA Posts: 297 Rating: (41)
Suggestion To thank Quote Answer

7/24/2013 11:30 AM	Rate (0)
Clive Thorne Posts: 18 Rating: (0)	Thank you Steve. I've tried "IDD" and the result is the same as "I", which agrees with the manual and your list which shows the default"I" as being the same format as "IDD". The other type identifiers you list, including "MR" can only be used (as far as I can tell) when reading from a data block (DB) and in that case it works OK. But at the moment the value I want to read is main PLC memory, not a data block. Am I alone in finding EasyScreen exasperating (not just related to this thread). I'm used to Siemens software being over complicated and difficult to use, but it does generally work. In EasyScreen you can write lines that will crash the HMI rather than report an error, and you can have lines that don't report an error, but don't work either. EasyScreen must be about the worst bit of Siemens software out there. Other NC manaufactures have graphic development environments for this sort of thing! (I know there are things like WinCC, but as I understand it with those you have to recreate the whole front end). Siemens, are you listening? Perhaps we need a support group for EasyScreen users, not technical support - we've got that here, but more of a support group where people say things like "There, there, it's not just you, we all sufferering from the same affliction"
Clive Thorne Posts: 18 Rating: (0)
Suggestion To thank Quote Answer

7/24/2013 3:04 PM	Rate (0)
Gorka Herranz Posts: 38 Rating: (0)	For EasyScreen log you cand fin in the following path under the following name Path: F:\hmisl\user\sinumerik\hmi\log\ Name: easyscreen_log.txt in this log you can see what is the failure on easyscreen. Thanks.
Gorka Herranz Posts: 38 Rating: (0)
Suggestion To thank Quote Answer

7/24/2013 3:23 PM	Rate (0)
Clive Thorne Posts: 18 Rating: (0)	Gorka, The problem is that there are errors which stop it working, but do not generate any error in the log file. I have not actually checked if the errors that crash the HMI generate an error message in there. Thanks, Clive
Clive Thorne Posts: 18 Rating: (0)
Suggestion To thank Quote Answer

7/24/2013 4:19 PM	Rate (0)
Gorka Herranz Posts: 38 Rating: (0)	can you upload a picture of that HMI Error please?
Gorka Herranz Posts: 38 Rating: (0)
Suggestion To thank Quote Answer

7/24/2013 5:58 PM	Rate (0)
Clive Thorne Posts: 18 Rating: (0)	A small success!! The following line: DEF Rot_Pos2 = (R3 / / /"","REAL Direct","" /wr1,fs1 / /"MD1428:REAL" /20,120,100 /150,120,100) will allow me to display a real value directly from the PLC main memory, so my original "CASE 1" is resolved. I stumbled across this in the standard "Leaktest" example. This is not mentioned at all in the manual (09/2011), so I'm not sure if it is new feature or just a bad manual. Gorka, What exactly is it you'd like a screen shot of - the stae of the HMI after it has crashed? If so then its a plain pale blue/grey background over the whole screen, with a small 'window' about 20mm x 8mm (on an OP15). I'm not in a position to take a shot at the moment, bt will post one when I can. Thanks, Clive.
Clive Thorne Posts: 18 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Mr_Engineer

|

Share this page:

Share this page on...

Follow us on