Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Simulate clock restart in SoftComfort

Created by: WaltD at: 3/20/2008 12:58 AM (6 Replies)

Rating (4)

Thanks 0

7 Entries

3/20/2008 12:58 AM	Rate (0)
WaltD Member Joined: 3/19/2008 Last visit: 1/25/2019 Posts: 7 Rating: (2)	In Logo! SoftComfort, how can I simulate the clock restart after a long power loss as described here from the manual?: "When you switch the device on again the clock is set to "Sunday 00:00 January 1". The time stands still and flashes. The LOGO! device is in the state that it was in before the power supply was interrupted. In the case of RUN the time switches parameterized with the time above are processed. But the clock still stands still." My application is that I wish to detect the loss of clock memory and flash a warning light. I think I can do this using the yearly and weekly timers but need a way to test the solutions. In particular I need to test if the weekly timer will set ON at 00:00 when set to 12:00 AM...... Or is there an easier way to detect the clock memory loss? As a last resort I will just have to leave the module unpowered for a week.

Suggestion To thank Quote Answer

3/20/2008 3:41 AM	Rate (2)
rosa Bronze Member Joined: 12/13/2006 Last visit: 9/8/2017 Posts: 191 Rating: (57)	Hi!! i´ll try using the retinteve memory.. the attachmentworks on the simulator this way - when you start the simulator the message appears and the output flashes - if you simulateunpluging and pluging the LOGO! ( icon at theright of the Q output ) theoutput stops flashing. - to simulate a loss of retentive memory, just turn off the simulator and turn it on again. Hope this helps! ROSA Attachment lost.zip (45 Downloads)

Suggestion To thank Quote Answer

3/20/2008 5:09 PM	Rate (0)
WaltD Member Joined: 3/19/2008 Last visit: 1/25/2019 Posts: 7 Rating: (2)	Rosa, Thank you for the reply, your example is interesting. What you seem to be saying is that when the clockbackup is lost so is retentivity of the block states. Are we sure this is true?Either way it is a useful tool. One issue is certain - starting SoftComfort is not the same as the long term power loss since the clock comes up running when SoftComfort starts. So the question remains:Is there a way to simulate the clock failure?

Suggestion To thank Quote Answer

3/20/2008 5:52 PM	Rate (0)
rosa Bronze Member Joined: 12/13/2006 Last visit: 9/8/2017 Posts: 191 Rating: (57)	Well... the only way we can be 100% sure of this is testing it.. i alredy have a Logo with the program, i´ll be checking it and as soon as i havean answerill post. ROSA

Suggestion To thank Quote Answer

3/31/2008 9:12 PM	Rate (0)
rosa Bronze Member Joined: 12/13/2006 Last visit: 9/8/2017 Posts: 191 Rating: (57)	the solution i posted is not working!!! i tested it on a LOGO.. today the clock lost its time, but the retentive memorystill has the count, it didnt lost it!! you will have to find another way to detect the clockreset. ROSA

Suggestion To thank Quote Answer

4/1/2008 2:37 AM	Rate (0)
WaltD Member Joined: 3/19/2008 Last visit: 1/25/2019 Posts: 7 Rating: (2)	I set up a test to see if combinations of year and week timers will detect the stalled clock. Unfortunately restarting after 168 hours without power gave a correct date and an incorrect time. The clock was not stalled. Atabout 5 PM the clock read 00:14 on startup(not 00:00, an interesting result in itself).This result seems to mean that the restart is not to be trusted, it is possible to get something other than either the correct time or a stalled clock.I will try to reproduce this result and will post the results in a week. At this point I am probably just going to detect the M8 bit and flashing a "check clock" message whenever there is a restart.

Suggestion To thank Quote Answer

4/9/2008 5:07 PM	Rate (2)
WaltD Member Joined: 3/19/2008 Last visit: 1/25/2019 Posts: 7 Rating: (2)	An "anded"combination ofa week timer and a year timer detecting January 1st, 00:00 Sunday does detect the clock stall. On time is 00:00, off time 00:01. On date 01:01, off date 01:02. The output stays high until the clock is restarted manually.The output will also be high for one minute every seven years or so. If this is a problem for you add some circuitry to also detect the M8 bit. In my application I don't care. The glitch I described in my previous postingmay still be a problem butI don't have the time or energy to try to reproduce it.

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on