Ausman

MVP 2016
  • Content count

    321
  • Joined

  • Last visited

  • Days Won

    26

Ausman last won the day on May 8

Ausman had the most liked content!

Community Reputation

47 Excellent

1 Follower

About Ausman

  • Rank
    UniGuru

Profile Information

  • Gender
    Not Telling
  • Interests
    Love/Hate waking up with a solution to a problem. Thanks brain....for not sleeping properly!

Recent Profile Visitors

3,564 profile views
  1. Exactly, JohnR. Visco, remember my comment about sometimes things can be simple, sometimes complex. A major part of programming is pinning down exactly what you need to achieve, and then finding the easiest way to do it. I often put all my known methods into the washing machine called the brain, and ages later I still end up with something not even considered in the first place! It is a constant learning curve. cheers, Aus
  2. Hey Cara, do I get a prize for being the Lucky 1000th post on this forum? Ha Ha, Aus.
  3. Have you got a differential set up on the setpoint? Without this a change of +/- 1 might trip things incessantly. cheers, Aus
  4. Hi Adam, Have not done an LX350. However, I'd first be throwing things at the printer via your PC using any of the serial port software out there like Hercules, to check that it is indeed working as expected via the serial line connections you've done. And also to check that that command structure works as expected. Then check what the PLC is doing by monitoring it's outputs. Somewhere between these two operations you'll likely find the stumbling block and be able to correct things. If it has indeed worked in the past, I would initially be suspicious of your total wiring config to the printer. Extra connections needed onto odd pins is not uncommon, or perhaps it is something as simple as a 2 & 3 switch. You may even end up needing to use a breakout box to help figure things out. cheers, Aus.
  5. Monitor your Com ports in Device Manager during hookup. cheers, Aus
  6. Hi Visco and all, I'm not completely sure what you're trying to do here, Visco, as your input being an MI is a bit self-regulating for possible amounts. Doesn't my screenshot below do it easily? But if you put 1000 into MI0, your result here will be 1, without any dec point. So this raises my question of what exactly are you trying to do with the result? Is it simply maths, displaying etc? cheers, Aus
  7. Hi again, vehicles are notoriously noisy electrical environments, so I had always assumed that you were running a buck/boost with heavy filtration as the power supply, and protecting the PLC with shielding in an appropriate box. It would be an easy thing to also have this configured as a UPS, with it's own very small battery done appropriately into the main system so that it only connects once the engine is running and stable. As an aside, I once had a very stable computer system go absolutely haywire at the crucial 24 hour team relay circuit race I had built a dedicated laps monitoring program for. It worked fine during extensive testing, but once at the track, in the tower 15m from the nearest approach point, certain vehicles would play havoc with it. Ended up having to move it into an underground room much further away for the race duration...very annoying!! But we are talking an Amiga 500. Ahhh...how times change! cheers, Aus
  8. Hi Flex, Not really as good. Drum is much better due to the inbuilt timer system. The process needs the timeouts to forcibly progress if needed and sometimes these steps are not very long. If I was using a SM, I would still have trouble monitoring things easily. If I could actually have everything showing realtime in the drum configuration window it would be very useful. For example, in the linearisation config, you can directly monitor the values. I want much the same in the drum config. I can't see that it would be too hard to do. cheers, Aus
  9. Hi all, would it be possible to have live drum checking? I am working with a reasonably complex one. It is hard to keep up with the steps by referring to my screenshot of the drum layout and then cross-referencing it back to the only way of seeing where it is up to by looking at the index number. It would be much easier if I could have a means to "open" the drum configuration when on line, with it showing where it is up to and also the timer counts if used. Please, please, please! cheers, Aus
  10. Yes, but only after doing some trials on the innate accuracy of the method. Like I said, in theory it is accurate and will work ok, it's meant to be a precise 2.5 or 1.25. If it is ok through extended testing, you would set it up so that you can easily match it to the master and go from there. I'm wondering whether the error you currently get is due to the firmware not reading the RTC info every scan? Alex? Saragini? cheers, Aus
  11. Hi all, just quickly looking at this and it is something I've done way in the past when I was young and heavily involved in club motorsport. I had an inductive on a non-driven wheel giving me distance info into my system, which I'm assuming you have involved as well. I don't have a Samba to run your ladder on, so can only comment on what I see. 2 things quickly: 1). I found many placements in your ladder which I would be separating out, or alternatively combining into one rung. eg 3 , 5. I have times where this has solved an issue that shouldn't happen, but does. There might be scan sequence issues. 2). Have you thought of using the time based interrupt, like I posted here: It could be worth experimenting with this and comparing it to the RTC over time, as it will give you much more accuracy having things down to much smaller time intervals. You may even be able to convert it into your own "RTC", rather than the inbuilt version. However, I have always assumed with Unitronics gear, (and am happy to be told otherwise) that the RTC and the time based SBs are independent. I have thought that the RTC is from a dedicated chip, and the SBs are from the system's time base. For that reason there can be discrepancy over time, and I take trouble to create separate controls if I need to relate things to real time, or a virtual time count. cheers, Aus
  12. I can't look at this in depth at present, busy. Others jump in, please. cheers, Aus
  13. If you are getting into Analogue values on a PLC, or anything that uses Analogue I/Os, you are much better off buying a signal generator to physically test things. Google "4-20mA/0-10V Signal Generator" and you will have myriad choices of how much you want to spend. Points to look for: self-powered, easy to setup/connect, easily adjust amounts on the fly, easily change type etc. cheers, Aus
  14. Hi Pal, can you please post your code, preferably the whole program if it isn't too proprietary. Otherwise screen shots of relevant code and configurations. cheers, Aus
  15. OK. The usual thing of something seeming simple but not necessarily so. Thanks for your efforts. cheers, Aus