Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Why M1.0 is not being set? Strange!

Created by: rajasekhar at: 9/19/2006 7:01 PM (6 Replies)

Rating (0)

Thanks 0

7 Entries

9/19/2006 7:01 PM	Rate (0)
rajasekhar Posts: 73 Rating: (0)	Sir, Below is the STL code...T58 and T59 are on-delay timers...T58 gives pulse of duration 30s...T59 gives impulse every 60s...I hope I am correct....Then why M1.0 is not set? network-1 AN T 59 L S5T#30S SD T 58 NOP 0 NOP 0 NOP 0 NOP 0 network-2 A T 58 L S5T#30S SD T 59 NOP 0 NOP 0 NOP 0 A T 59 S M 1.0
rajasekhar Posts: 73 Rating: (0)
Suggestion To thank Quote Answer

9/20/2006 6:41 AM	Rate (0)
Siemen-Stains Posts: 101 Rating: (0)	disable the code, and make sure you can turn the bit on in 'stat vars' if it goes off again, you may want to search the bit with 'overlapping access to mem areas' ticked, so you can make sure its not used in a word somewhere. also make sure its not in the system clock byte check in your hardware config/clock memory, and check if a byte address is not entered there.
Siemen-Stains Posts: 101 Rating: (0)
Suggestion To thank Quote Answer

9/20/2006 3:10 PM	Rate (0)
rajasekhar Posts: 73 Rating: (0)	Hello, I am again...Yes I have checked M1.0 bit and I am sure that I have not used it anywhere in the program....Also I am attaching the project archive...Please go thru it and correct me... Thanks in advance.. Attachment learning.zip (242 Downloads)
rajasekhar Posts: 73 Rating: (0)
Suggestion To thank Quote Answer

9/30/2006 7:56 PM	Rate (0)
Late Platinum Expert Joined: 1/7/2006 Last visit: 5/11/2025 Posts: 2705 Rating: (321)	Hi Rajesekhar, I'am back and as promised I check the code. FUNCTION FC 2 : VOID TITLE = VERSION : 0.1 BEGIN NETWORK TITLE = A T 59; S M 1.0; AN T 59; L S5T#30S; SD T 58; NETWORK TITLE = A T 58; L S5T#30S; SD T 59; END_FUNCTION If you change the code as mentioned as before then it will work. This (normal) behaviour is coming from the way timers are working. The timers are updated every 10mSec and so it could be that when you asking in different places in the program the timers that the timer will be set. But thats not the problem here, the trouble is here because you first change the Timer and after that check if the timer is set. Because the T58 is started on a AN T59 and the timer T59 is changed from FALSE to TRUE, the T58 is now started and the T59 will directly be reseted, so if you came in the old software by the instructions A T59 and S M1.0, the timer will be always FALSE........
	I hope that the answer will help, if you have still questions, don't hesitate to ask me. All the best, Late Never say never, think in solutions, not in trouble......
Suggestion To thank Quote Answer

10/1/2006 11:05 PM	Rate (0)
rajasekhar Posts: 73 Rating: (0)	My Dear Late, Thanks for providing the concept....still I have a doubt... Let us assume initially PLC is stop mode and T58 and T59 are at false condition.... at t=0+ I have put PLC in run mode....at t=30+ T58=1 and at t=60+ T59=1 and it should set M1.0=1.....because program scans from top to bottom... Am I doing a basic mistake? Also suggest me How to test this code instruction by instruction using PLCSIM? So that I can understand... Thanking You, Rajasekhar.
rajasekhar Posts: 73 Rating: (0)
Suggestion To thank Quote Answer

4/21/2011 9:44 AM	Rate (0)
nbk Posts: 197 Rating: (3)	Dear all, While browsing through this forum ,I came across this interesting thread (& I apologize for raising it back) What concerns me is this : If the CPU cannot set M1.0 (in the original logic of the questioner) in the same scan cycle , then , what is the reason that it sets M1.0 successfully after executing these codes (and perhaps a few more blocks after this block) before it comes back to the top of the re-arranged logic to set M1.0 ,in probably , the next scan cycle , where it finds "A T59" still to be "true"? Regards
nbk Posts: 197 Rating: (3)
Suggestion To thank Quote Answer

4/22/2011 9:31 AM	Rate (0)
nbk Posts: 197 Rating: (3)	With my little understanding on this subject , I could reach the nearest explanation (whichis still to be verified by this forum)as under: Since the timer is updated every 10ms (considering the lowest time resolution / time base), there is no way "A T59" will be "true" in the original logic. However, in the re-arranged codes , when the CPU returns to scan the codes next time (in a new scan cycle) , the timer status will be already updated by now , so that "A T59" is true to set M1.0. Will someone plz comment back on this?
nbk Posts: 197 Rating: (3)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on