Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by MalSnaize

  1. Yes good news indeed! Thanks for your advice and guidance Kartmel and for your support and ideas throughout the resolution process. Kind regards Mal
  2. HI all As I had already ordered a replacement unit I thought I'd wait for that to arrive before following up with support team. It seems that in one hit I've resolved both the date/time reset issue and the other thread on peripeheral devices not registering. I simply unboxed the new V1210, (did a quick date/time on power cycle test) then loaded my software and it ran first time. Power cycle doesnt touch the clock! All sorted - thatnks for all of your input folks regards Mal
  3. Hi Ausman yes I I do recall getting a message about updating but I have to say I thought it was relating to the OS rather than the visilogic program. I ordered a new V1210 which will hopefully arrive today. Hopefully the clock issue will not exist and it will also have the previous OS installed and everything will work. If not I will use Swapper. Do I need to be online for Swapper to work? (the plC is installed in an isolated location) cheers Mal
  4. Will do guys thanks for guidance. As an update, I have purchased another unit to see if it does the same thing - my supplier tells me the others in stock do not so If I load my code and it starts doing it then we know its my code. See my latest fun and games in my post about PLC not being able to communicate with EAX and TO16x cheers Mal
  5. HI All - I seem to have all the quirky ones (see my clock issue So this issue: I have a V1210 + Expansion Module + 2xTO16 - all was working fine for client; I recently recovered the set up to develop and implement new features. On returning the setup today I (for the first time) connected everything up only to find that the expansion module is not communciating with the PLC. : 1. On startup there are some brief flashes on teh comms LED 2. the TO16 just keep flashing. I loaded my empty test programme which is set up for same hardware config. No change until I did an Iniatlise/Reset (Thanks Ausman) and behold evryting was talking again. I reloaded my client's software and nope, it will not see the perpheral devices. Tried Initailise reset - still no joy. I have checked and rechecked the hardware config and it is correct. Is it possible to somehow disable hardware in code? The only thing I can think of is that I did update tle PLC OS on Joe's advice (relating to the clock issue); If I update the OS do I need to do something else to ensure compatibility? Man this PLC is jinxed ! (see my clock issue) Many thanks in advance of any ideas on this. Cheers mal
  6. Thanks Simon - I assumed that would be the case; was trying to strike up a dialogue with Unitronics to see if they had any thoughts on this other than perhaps a manufacturing problem.
  7. Hey Aus - sorry, yep I did check but juggling all the great ideas being provided I missed the specifc response to you. Agreed - I've escalated to my supplier in Auckland who has promised top followup with Unitronics - Does anyone know - is there a direct line to Unitronics where I can provide a Serial Number and they can tell me if ther was an issue with the batch? For me its been 2 out of 2 failures. Cheers Mal
  8. Hi Kratmel - I tried setting the dates to pre-2006. 2005 - ok 2000 - ok 1999 - resulted in 2099 I set to 2000, cycled power and it reverted to 2006. All pretty consistent. I woldnt be surprised if we find there is a design flaw around the RTC for this batch and there is a floating input somewhere that is casuing the clock to be reset on power cycle. I'll wait for Unitronics to come back. On your suggestions of getting external time, the PLC is totally isolated so no network access and no GSM access.
  9. Ah Gabriel - So Initialise/Reset Clear MI values - keeps SI values Reset - has no impact on MI values - Keeps SI values Power Cycle RETAINS MI values but LOSES SI Value (well the clock settings) So what does that tell me? - something is resetting the clock only at power up but leaving MIs alone. This has happened with two separate V1210 units but likely out of the same batch given their consecutive serial numbers It cant be my code as it does this with a totally blank programme. I feel we are getting closer!
  10. HI Ausman, Kratmel and DanT - a wee update... I've spoken to my supplier and he's taking the serial number back to Unitronics to see if there is a known issue with that batch. That got me checking and I see that the first unit I had which exhibited the same problem and was replaced turns out to be the one immediately off the production line (or at least their serial numbers are consecutive). Am am now leaning to it being a hardware problem (in line your thoughts Simom) - UNLESS someone can point me at a flag that says "clear the clock at power up but not at reset or initialise" Now that would be magical if there were one and mine was set the wrong way. DanT thanks for all the trouble you went to tracing the board. I was tempted as I have all the right tools but I'm one of those folks that knows enough to be dangerous so probably best I dont go fiddling inside the box! As soon as I hear back from supplier I'll post an update Cheers All! regards Mal
  11. Hi Simon - thanks for your comments - yeah I'd have said the same except that when bought the first V1210 for my client I had the same problem. Spent ages checking batteries, voltages, etc and finally convinced my supplier to replace the unit. So this is the same problem with a different V1210 - SOFTWARE! I hear you cry.... but i have the same problem with a blank programme that does nothing. Same story - set the time, cycle power and the time gets zapped Its really quite strange (or I am REALLY unlucky having two faulty units) I've explained the problem to my client and we are now looking at a small UPS solutution - which would be a terrible waste but as a forum we'vce spent a lot of man-hours on this.. Still - I hold my breath for a flash of inspiration from someone.
  12. HI Kratmel - I did your tests, the RTC stayed valid until I did a power cycle. Ausman - as requested here are some screen shots. I did 1. after program load and set time 2. after visilogic console reset 3. after power cycle My feeling is that the power cycle is resetting the clock., Any thoughts your side? Cheers Mal
  13. HI Kratemel - amazing thinking given I was just typing about the RTC values in the visilogic interface! I have a full build and download running now so will try that when it finishes.... I'm out of time as I need to leave in 40 minutes to show customer., will have to come clean about the clock!
  14. Hi Ausman - I have to say I was using the direct bit access to do the Init/Reset however I've now used the interface. Same story No insult my friend; the obvious is obvious to everyone except the operator! Yep I've rechecked its location and orientation and also the tested the voltage which is sitting at 3.3V Just a point, - in the (visilogic interface) would I be right in saying the SET RTC value is the PC's RTC and GET RTC VALUES show the PLC? The former show the correct date/time. Just trying another full download and reset then will try the battery out but I need to deliver to customer for demo so suspect I wont have time.. Cheers Mal
  15. Oh I also tried the dumb - literally totally empty app. Set the date/time which it held. Cycled the power and date/time gone.. I'd like to say its a battery or hardware problem but I had exactly the same issue with the first 1210 but after replacing the battery I had the unit replaced by the supplier. Really bizarre!
  16. OK so I've done the reset and initialise (tried both SB300 and SB24) and downloaded the code. Date is set fine. Try resets and date / time is retained. If I pull the power then I lose the date/time Completely baffled..
  17. Hi Kratmel - I see that the bit is low and seraching for that SB shows there is no (direct) reference to it - so I suspect that other than my recent attempts as per Ausman's guidance, I dont touch it - nice thought though, Isakovic, thanks for the suggestion but no, I dont grab network time nor do I have card installed. Cheers Mal
  18. Hi Flex, thanks for the offer, unfortunately I am bound by some strict confidentiality agreements so am not allowed to (its a government department and whilst its not a super-secret project, I still have a failry standard govt contract that I signed). That did trigger another thought that I should try a very simple bit of code and see if it does the same. Ausman, thanks for your ideas too - I'll give those a try if after I've done the dumb-code test I still see the same behaviour We have a great community here! cheers Mal
  19. Panic over! (well it was only me panicking !) Thanks for advice Joe - Unfortunately that didnt crack the original nut - I still lose time/date on power off. Its not a biggie as customer can enter date time via the little interface I wrote bit would be nice if it didnt lose it.. Cheers Mal
  20. Oh this looks bad... Am I doomed - do I restart the PLC do you think?
  21. Thanks Joe I'm on 4.0(19) am trying to update but the wizard tells me I must use COM1 and no matter what physocal USB I use, it shows as connected via COM3. Does this matter? cheers Mal
  22. Hi Again all - I had the PLC replaced by my supplier and used that. I also wrote a "user friendly" date/time setup just in case. Just recently I got the PLC back from my cusomer to do some enhancements and I find that in fact the system is still dropping the date time on power-up. Must have been happening for the customer and they havent mentioned it (unless they have never powered off) So I've now tried new PLC, new batteries - the only thing that remains consistent is my code. Is it possiblt that somehow I am somehow resettting the PLC date time? Does any one know of a system bit that would do this and I am somehow bouncing it? Actually as soon as I wrote that I realise that if that is the case it can only be in y initialisation routines - I'll have a look in those but if anyone does come up with an bright thought I'd be really happy! thanks Mal
  23. Thanks Gabriel - yes I too previously used one bit to trigger a number of text fields. The problem arose when I increased the number of text fields significantly (one screen has 16 x 20 character fields plus a whole load of static information. The other screen has 40 fields of 6 characters. So I'm thinking maybe theres a limit to how much data can be refershed in one scan (has to be, right?) Supporting that, following Joe's advice and introducing individual trigger bits it has fixed the issue - I guess the OS simply looks after it nd determins how much it can referesh in one cycle then comes and finishes off the rest in subsequent cycles (thats just a guess) anyway end of the story is that it now works! thanks all
  24. Hi Again Joe - worked a treat thanks - the table now displays nice and smoothly too At the moment I trigger on each cycle for each label as the table of text is built; I wonder would it be better (or indeed worse) to build all of the data and then write all the triggers at once? Just a thought.
  • Create New...