Industry Online Support
Technical Forum
Navigation
Rating 
Thanks 0
5 Entries
| 2/16/2011 7:39 AM | |
|
Posts: 58 Rating:
|
Gents. When I try to convert a Step 5 (CPU 115U) program to S7 (CPU315-2DP) The S7 program has occurs error when I try switch to run mode and went to stopped, the module information said "BCD Conversion Error". Follow this error, I found that the error will be solved if I disable the timer T102 in network 12 (please see attached file) I have extract here in the attached file the related code in Step5 and Step 7 Please, any one can help me how can I solve this problem to push the timer T102 in working back as it original program ?! Ban PS ! In Step7 when I try to go online, I Saw that the value of DBW4 in NETWORK12 is : 200C AttachmentS5-S7.pdf (66 Downloads) |
Last edited by: ntban at: 2/16/2011 7:44 AM |
|
| 2/17/2011 2:49 AM | |
Joined: 10/7/2005 Last visit: 6/3/2023 Posts: 2966 Rating:
|
Hello ntban well, "200C" hex is certainly an invalid BCD number andwillcause the "BCD conversion error"when used as the S5 Timer setpoint in an S7. The original S5 program would of cause have had the same non-BCD compliant value as the Timer setpoint. You'll find though that the S5 program couldn't care less about this and will simply accept the setpoint and run(from memory it will in this casetake "2009" hex (i.e. 9 seconds) as the setpoint, which is a valid BCD value, butI suggest you verify that with a test in anS5 CPU, as my memory may serve me wrong). As a solution for your converted program, I suggest you either directly transferS5T#12S (if you want 12 sec as the Setpoint) OR S5T#9S (if that's what the current S5 program does indeed use) into DB14.DBW24 and/or DB195.DBW4 and get rid of the "OW 2000" logic. I hope this helps |
|
Cheers |
|
| 2/17/2011 6:54 AM | |
|
Joined: 10/7/2005 Last visit: 6/3/2023 Posts: 2966 Rating:
|
What I mean by the S5 "not caring" about a non-BCD compliant value as a Timer Setpoint, is that it will simply take the value and run the Timer without "complaining" (anS7 however willcreate a BCD conversion error and call an error OB). WhatI can't remember is if the S5 Timer in your case would start with a 12 sec. value (i.e. the S5 CPU does an "automatic" conversion to a BCD value), or if it will start with a "truncated" valid BCD value. This is somethingI suggest you test with a real S5 CPU.
It's a small world isn't it (I can't take credit for this project though as I wasn't involved). |
|
Cheers |
|
Follow us on