Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Joel Moore

Pages: 1 [2] 3 4
16
Technical support / Communications Watchdog
« on: July 26, 2006, 01:03:38 PM »
Has anyone successfully implemented a communications watchdog using ladder logic?  I'm trying to ensure that our PLC isn't able to do anything it shouldn't if our HMI loses communications with it.

What I do now is the following:



The ResetWDog CusF contains:
Quote
TIMERPV[1] = 50
TIMERBIT[1] = 0
CLRIO WatchDog

From our HMI we repeatedly set the WatchDog relay using "Force Set/Clear Single I/O Bit" command ("Wbnnnnxx").  This causes the ResetWDog custom function to be called which resets the timer and clears the WatchDog relay.  This timer is constantly counting down thanks to the Norm.On input.  If the timer counts down to "0" the WDExpired custom function gets called which performs the appropriate actions (currently resetting the PLC which puts it in a "frozen" startup state).

This works 95% of the time but once in a while the timer inexplicably expires.  Monitoring my HMI doesn't reveal any obvious communication delays.  The timer is currently set to 5 seconds and the HMI is probably resetting the WatchDog relay 10 times a second.

So maybe I'm going about this all wrong.  Has anyone else tried to achieve a similar goal following a different path?

17
Technical support / Looking for MORE advice with 2-wire switches
« on: July 26, 2006, 10:42:22 AM »
On our machine we have a couple of different 2-wire switches wired into T100MD888+ PLCs.  One has problems and one works fine.  Here are some specs:

Switch #1: Pressure switch (SMC part # PS1000)
Load voltage: 12-24 VDC (we're running at 24V)
Load current: 5-40 mA
Leakage current: < 1 mA
Internal voltage drop: < 5 V
On voltage measured at PLC input: 3 V
Off voltage measured at PLC input: 15.2 V

Switch #2: Proximity switch (SMC part # D-C73)
Load voltage: 24 VDC
Load current: 5-40 mA
Leakage current: not specified
Internal voltage drop: < 2.4 V
On voltage measured at PLC input: 1.6V
Off voltage measured at PLC input: 19.3V

Switch #1 is the one that doesn't work properly.  If I power up the PLC and the switch is already on (i.e. air pressure is on) the PLC reads the input as on.  If I turn down the pressure until the switch goes off, the input goes off as well (so far so good).  However, if I now increase the air pressure until the switch turns on, the input doesn't turn back on again.  The only way to get the PLC to read the input as on is to power up the PLC while the pressure is on.

I tried the two suggestions mentioned in this thread but neither achieved anything.

I know this really isn't a TriPLC issue but I was hoping you might have some insight into this since you are more familiar with the design of your PLCs.  Plus, you've been very helpful with questions like this in the past. ;)

18
Technical support / Can't configure ICP I-7018 with TriPLC
« on: May 08, 2006, 08:44:50 AM »
I realize this probably isn't a TriPLC question specifically but I'm sure many people here use ICP's modules so hopefully someone can provide some advice.

We've been unable to configure our I-7018 modules from the T100 PLC.  I tried putting the following line:

A$ = NETCMD$(3,"%0101OF0600" + CHR$(13) + "~")

in the 1st.Scan circuit but I don't get a response from the module (i.e. A$ is empty).  I know communications are working because I am getting responses in the circuit that reads the inputs.  The module just seems to refuse to respond to the configuration command.

I've tried moving the config command to another circuit that I can trigger manually while monitoring (thinking maybe the 1st.Scan happens to soon after powerup and the ICP module isn't ready yet) but that resulted in nothing as well.  I finally resorted to breaking out my RS485 adapter and configuring it using Hyperterminal but it would be nice if we didn't have to do that in the future.

Any ideas on what I could be doing wrong?  Is anyone else successfully configuring their ICP modules from the TriPLC?

(It did just occur to me that we probably shouldn't be sending the configure command in the 1st.Scan rung anyway since that probably causes the ICP module to write to its EEPROM.)

19
Technical support / Can COM3 comm issues disrupt COM1?
« on: April 20, 2006, 08:32:40 AM »
I'm having communication problems with a T100MD888+ PLC.  The TLServer keeps disconnecting with an error stating:

Quote
Bad Network Performance

Please check the following:

1. None of the slave nodes are sending data on RS485
2. Long network is properly terminated and biased

We have an ICP module connected to the RS485 port on this PLC and this is the first time we've done this.  We don't have biasing resistors on the port (simply because we can't add another power supply to our system) but regardless of the potential problems caused by that we are communicating with the PLC using the RS232 port.  Could communication errors on the RS485 port cause failures on the RS232 port?

20
Technical support / Is NETCMD$ "atomic"?
« on: April 13, 2006, 04:40:05 AM »
If I call NETCMD$ on the same port from multiple locations in my program, will this cause problems?  Does one NETCMD$ call block others from accessing the port and force them to wait until the first one receives a response or times out?

21
Technical support / Stepper jogging
« on: October 19, 2005, 04:57:15 AM »
I've implemented a jog feature in our 888 program by sending large values to STEPMOVE and issuing a STEPSTOP when the jogging is done.  However we recently uncovered a problem with this technique that somehow escaped our notice before.  If the speeds are too high suddenly stopping the motor with STEPSTOP results in the motor skipping a number of steps (due to momentum) which knocks the position off.

One solution is to limit jog speeds but this is very unsatisfactory since the speeds would be too slow to be useful in our application.

So consider this post an enhancement request for future versions of the Triplc firmware.  I'd like to either see some jog functions added (maybe even simplifying the use of an analog input for speed control) or at the least add a deceleration parameter to the STEPSTOP command where obviously a decel of "0" would make it work as it does now.

22
Technical support / Multiple webservers?
« on: October 10, 2005, 11:35:42 AM »
I was surprised to find out that I can't run a second instance of TLServer so I can connect to two PLCs simultaneously.  What is the reason for preventing this?  If it's a TCP port issue couldn't it just take the next available port (9081)?

It won't matter in my application as I don't use TLServer normally but during development it's handy.

23
Technical support / Oscilloscope probe
« on: September 09, 2005, 12:39:16 PM »
Does anyone have any ideas for interfacing a 50 ohm oscilloscope probe with a Triplc's analog inputs?  Maybe there's a signal conditioner or something that can be used?

edit: I didn't know if this should be in the General forum.  I figured here since it could be of interest to other Triplc users.

24
Technical support / I2C
« on: September 06, 2005, 11:15:32 AM »
I've only started looking into I2C this past weekend so I'm not even sure if this question makes sense but is there a simple way to interface with I2C devices using the 888 PLC?

I've seen adapters for communicating with I2C devices using RS232, USB, and parallel ports and some seem pretty simple.  Isn't there a way to use the I/O on an 888 to do the same?

And if there isn't, maybe that's something your PLCs could offer in the future?  An I2C header somewhere on the board?

25
Technical support / Lead Free?
« on: August 24, 2005, 12:09:14 PM »
Are your PLCs manufactured lead-free?  We're hoping to start shipping machines to Europe and ROHS requires them to be lead-free.

26
Technical support / Power reversed on T100MD1616+
« on: April 01, 2005, 05:41:07 PM »
Someone hooked up the 24V backwards and I failed to notice for a few seconds.  The only visible damage is the diode at DP6 but the board powers up and I can communicate with it OK (so far).  Outputs are working (haven't tested any inputs yet).

Did I just get lucky?  Can you suggest any components that I should probably replace to avoid a failure down the road?  I suppose that diode is one.

27
Technical support / Replacement voltage regulator?
« on: March 29, 2005, 11:44:44 AM »
We broke a voltage regulator off one of our MD888's.  The part # is KA7810.

The only place that sells these (that we frequent) is Mouser.  We'd like to order something from Allied since we already buy other stuff from them.  Is there another part we can use in place of this that might be more common?

28
Technical support / ASCII 255 inserted in response after powerup
« on: October 07, 2004, 11:26:46 AM »
I've noticed recently that the first time I communicate with a T100MD888+ controller after it's been powered up, the response is prepended by an ASCII 255 character.

Has this always been the case and my old communications code was just able to ignore it or is this something new?

And is it intentional?  Can I rely on it to detect a powerup condition?

29
Technical support / Using PWM for halogen brightness control
« on: September 29, 2004, 10:12:19 PM »
Can I use the Triplc's (T100MD888+, specifically) PWM outputs as dimmers for halogen lighting?  Has anyone tried this?

A 24VDC, 50 Watt bulb will draw just over 2A at full on so it falls within the PWM output's capabilities.  

What about the concept of using PWM for halogen dimming?  Is this even a valid technique?  If so, what's the lowest frequency I can run the PWM at without the bulbs flickering or pulsing?  And can I drive the bulbs with the same power supply I use for the Triplc or is that a bad idea?

I know I can probably answer most of these questions experimentally (and I probably will) but I just wanted to be a little confident that I'm not going to fry a plc before I try it.

30
Technical support / Upload program to PLC w/o using Trilogi
« on: June 30, 2004, 02:18:11 PM »
We are currently using the T100MD888+ PLC in a simple machine we sell.  We've written our own Windows application that communicates with the PLC (and some other devices) using serial ports.  We're not using TLServer since we have no need for it (and we want to simplify things as much as possible).

However, one thing we can't do easily is upgrade the PLC's program if required.  The only way to do that now is to use TLServer and Trilogi however it would be nice to make the upgrade transparent to the customer.  When we send a software patch or upgrade they simply install it like they would any Windows program and then when they start our application it handles updating the TriPLC if necessary.

I sniffed out what was going on over the COM port and noticed that the commands used during the transfer are simply undocumented Host Mode commands.  It doesn't seem like it would be a major feat for our program to follow these same steps (with the help of some tips and guidance by you).  However we'd obviously need Trilogi to output some sort of compiled binary file that our main application can upload.

Any thoughts on this?  Any other users out there who think this would be useful?

Pages: 1 [2] 3 4