Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


hotwires last won the day on October 13

hotwires had the most liked content!

Community Reputation

32 Excellent

1 Follower

About hotwires

  • Rank
  • Birthday 03/29/1981

Profile Information

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

Recent Profile Visitors

1,080 profile views
  1. 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!
  2. 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.
  3. Windows 8.1 invalid class

    Success on Windows 10 home 64 bit. Not sure what official Windows 8 compatibility is, it failed for me.
  4. 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.
  5. 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?
  6. 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.
  7. 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.
  8. 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
  9. 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
  10. All testing (successful) I have conducted with bidirectional asynchronous serial communications have used Unitronics MJ10-22-CS25 and terminal programs with flow control "OFF".
  11. 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.
  12. Files to big to attach here.
  13. Serial Protocol function block. Unless computer is running SCADA software that is already MODBUS oriented. What model of Vision are you using? There is an example program for hyperterminal to PLC communication. I have a modified example for V430 that is bidirectional (scan and send FB's) serial comms PC runs realterm (or hyperterminal if your OS is old enough).

    I've never lost a program during an OS update. If everything goes by the book, no worries. Anything can happen. Always have 3 backups of complex PLC program that took anything over a day to develop. Preferably on three different media types and in three unique physical locations not under the same roof.
  15. Mark S. Thanks you, the screen shot you provided helps bring the picture of the third party hardware into focus. Still intrigued by the 300,001 and 400,001 decimal MODBUS address. I'll have to process this for a while. I'm sure the addition info you posted will accelerate an answer to your troubles. Please clarify: "When I read the analog Inputs I use the read input registers (4) and use a value of 0 and I get back the value that is in register 300001. The offset because the module uses one as the first register." where you say "value of 0" do you mean address of 0? have you tried registers periodic, write, (16), address 40001? Or 40000 accounting for offset. Unilogic's valid MODBUS address range is 0 to 65535, so the 400001 is out of the question. Modscan is great idea. It's referenced in the automation direct manual (see photo). This is an @Joe Tauser question. My best battles are fought and won with gear that is at my fingertips. Or someone lifetime of real world experience.... which I'm still working on.