Jump to content

hotwires

Members
  • Content count

    120
  • Joined

  • Last visited

  • Days Won

    11

hotwires last won the day on October 13

hotwires had the most liked content!

Community Reputation

32 Excellent

1 Follower

About hotwires

  • Rank
    UniGuru
  • Birthday 03/29/1981

Profile Information

  • Gender
    Male
  • Interests
    land mobile radio, amateur radio, flying single engine aircraft

Recent Profile Visitors

1,139 profile views
  1. agree with Flex, you need to "one shot" the toggle coil (per event). otherwise it will toggle every scan for the durtion of the event.
  2. I recall the old simplex school clocks synchonizing from a master clock that sent out a 19kHz signal over the AC building wiring. It controlled the bells also. Maybe some BASIC STAMPS and DTMF codes (master send, slaves selectivly or collectively receiving). would be easier if devices were DC powered, a bias tee to inject signalling AC. Just thinking cheap. Not off the shelf there are protocols out there for such: https://en.m.wikipedia.org/wiki/Power-line_communication however unknown on compact, low cost hardware. Sounds like something an audrino, raspberry pi, or parallax basic stamp could be programmed to do. I generally loath anything that is "trendy".
  3. Remote Operator Issues

    I have had the same issue with socket getting stuck open after remote operator app users do a clean disconnect. Had to keep an alternate socket and reboot PLC periodically. Most prominent case of that issue was on a V1210 with very poor quality DSL internet service. Item two: I have observed two V430's (different sites and unique programs) go into black screen/STOP MODE pressumably when trying to send an email. My substainsiation for this theory: first V430 I ever used ran over a year with ZERO problems, the trouble began when I put it on the internet and started using email. Also have had poor reliability on success of email transmissions. I think I finally got the bugs out with changes in how the emails are sequenced and triggered. I had to construct logic to command the SMTP socket connect a second time if not connected after 10 seconds at one of my sites. It sends a test text message to me everyday at noon as a primative 24 hour periodical watchdog. So far there have been no BSOD's or failed emails on the two V430's, only after a major overhaul of email trigger and socket logic. I beleive the frozen Sockets with remote operator app usage had NOTHING to do with firewall or ISP. tweaked the SI's for timeouts and retries. ended up putting in unistream before i ever definatively resolved the frozen socket issue on V1210. Did have one instance where the Unistream stopped sending emails but could still be reached by VNC and online mode, meaning it had WAN connectivity but something went wrong with email sends for about two weeks. PLC reboot resolved issue. moral of the story: don't put to much faith in email to text alerts. I've thought of using a Raspberry Pi as a secondary email sender. I never get the time to,sit down and do some R&D on it. would get you SSL email capability. I have done some stand alone RPI email alerters (temperature vs. setpoint and discrete input triggers). would have to get the communication interface between PLC and RPI figured out. Hope to do some experiments with an RPI as a TCP MODBUS slave soon. Are you using any XB's in your code?
  4. Trends

    I tried ladder snippet in photo on a V430 (online mode). Using an MI as "C" result only shows a "D#2", I had to use an ML to get 2300 (derived from -0.0023). If you need MI just drop a STORE block with A=ML202, B=MI202. This will give you a baseline MI that will go up or down proportionally to the MF. If you want to preserve the negative sign then omit the ABS function block. The middle FB is found in MATH, FLOAT, CONVERT, INV (A+B/n). Hope this helps!
  5. Windows 8.1 invalid class

    I did get photo of screen, to big to upload here. I have Nvidia Quadro K2000D video card, core i3 intel, 8GB, HP factory MoBo. MS updates where caught up. I tried several uninstalls and reinstalls of UniL. VisiL installed and ran okay. Perhaps a dependency issue like Saragani suggested.
  6. Windows 8.1 invalid class

    Success on Windows 10 home 64 bit. Not sure what official Windows 8 compatibility is, it failed for me.
  7. Windows 8.1 invalid class

    Yes, ran as administrator. Tried version 1.19.83_XP also, no avail. Thanks for the free Win10 upgrade link (I was not aware of that). Running 10 upgrade now. Might as well gear up for Win10, like it or not.
  8. Windows 8.1 invalid class

    I attempted to install latest version of Unilogic on Windows 8.1 x64 OS. When I launch I get invalid class message, then nothing. Any suggestions?
  9. Problem with analog output

    Report your findings to Unitronics support. Success with 0402N would prove it's not a coding problem. i don't have a WBC1 to try with.
  10. The toggle bits change at the end of each polling cycle and transport via serial MODBUS to toggle O9 in the slave (an MB could also be used), PTC/NTC contacts keeps TE3 alive, O9 loops back to an input on the slave the is read by the master (call it a hairpin or loopback), the same scheme is used again in the master to monitor the echo of the toggle bits. it's fairly fool proof. If the toggle bit gets stuck in either state for longer than the timers preset then a bit will go true on both the master and the slave.
  11. Problem with analog output

    oo, I don't have time tonight to load this into my Unistream with UIA-0006, drag the scope out, and live test this. Going from your results here is what I would try: 1- Change the frequency.frequency100mS contact in Rung one to a PTC "-[P]-" contact 2- Change the frequency.frequency100mS contact in Rung two to a NTC "-[N]-" contact 3-Tag the B side of the two STORE blocks directly to the AO register. UniL will allow it, I tried. Unless you have a reason you need to intermediate the values. 4- disable rung 3 5-Download and test Should work as follows: ON rising edge of 50% duty cycle 100mS time base #7000 will load in the AO's register, on the falling edge #700 will load to AO reg. You're over doing it by reloading the same value every scan for each 50 mS, It's a retentive register not a charge pump. Rung 3 seems redundant in the context of the rungs displayed. I'm not seeing your entire program. Please share the results of this simple logical alteration. IF this still gives erratic results as seen on scope THEN post and I'll try to recreate. Have you contacted Unitronics support team yet? Hopefully this post will get some more exposure and suggestions soon. dB
  12. Peter, I have implemented a fairly basic com fail detection scheme I used in serial MODBUS RTU's. As Joe T. stated this is a heartbeat the master sends to the slave (and also can be echoed back for loss detection at the master). Toggle bit each time the MODBUS master's R/W function is called, that bit is sent to slave (in write coil), branch PTC and NTC contacts (HB bit) to a TOF timer in the slave ladder. Each time the heartbeat bit changes states in slave, the timer OFF delay is kept from expiring. set TOF time base according to how many cycles you want to allow it to miss before expiring, Use an inverted contact linked to TOF.out, that can drive an MB coil that is your com failure signalling bit (which in turn can zeroize outputs or whatever you want to happen). I use SB2 branched in with PTC and NTC of heartbeat bit, this prevents the TOF from being expired at power up (depending on where the master is in the polling cycle the slave may not see an HB bit transition at the slaves POWER UP. Hope this helps. If it's still clear as mud I can try to dig up a redacted code example for you. Hotwires
  13. All testing (successful) I have conducted with bidirectional asynchronous serial communications have used Unitronics MJ10-22-CS25 and terminal programs with flow control "OFF".
  14. If you have specific questions (or unexpected results) please post. My strong suit is with modbus. If you are developing a custom communications model then serial PROTOCOL method is probably the correct approach.
  15. Files to big to attach here.
×