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.


Messages - TTCSR

Pages: [1] 2
1
Technical support / Re:Continuous counting display
« on: March 20, 2014, 04:13:46 AM »
That's just AWESOME  ;D
Worked perfectly and I am monitoring 8 seperate signals that go up to 999,999,999 each.
Thank you very much!

2
Technical support / Continuous counting display
« on: March 19, 2014, 07:19:29 AM »
I am setting up a test rig to cycle a switch and want to display it's number of cycles in the millions, however, the values I display are limited.  Is there anyway to display numbers in the millions or greater?

3
Technical support / Re:Easybuilder MMI6070H and FMD1616-10
« on: January 17, 2014, 10:08:46 AM »
I assumed the CD that came with the touchscreen was the latest version of easybuilder, it came with V4.65.02.
I downloaded v4.65.08 from the website and TRI_PLC now shows up  ;D

4
Technical support / Easybuilder MMI6070H and FMD1616-10
« on: January 17, 2014, 07:04:43 AM »
I am currently using the 7” touch screen MMI6070H with a Triangle Research PLC FMD1616-10, however, Easybuilder8000 says does not support device type.  I looked through the setup as well and the PLC is not listed.  
I have used the smaller screen MMI6050 in the past without any issues, however, I needed to download a driver.  
Are there any drivers for the MMI6070H I would need to have it work for the Triangle Research PLC FMD1616-10?  

5
Technical support / Re:Message display
« on: January 22, 2013, 09:18:49 AM »
I figured it out with a timer.  I placed a timer on each test.  If the test remains active for longer than 2 seconds, the timer bit triggers an output bit that I use to enable a display on my HMI.  I had to create 50 timers, one for each test, but it works perfectly.  ;D

I agree the coding has limited my options, however, it was necessary due to the application.

Thank you for all the input and feedback!

6
Technical support / Re:Message display
« on: January 22, 2013, 03:49:12 AM »
My sequence is advanced by each cutom function via an IF THEN ELSE statement (shown below).  Each completion of a test sets the CTRPV to the next sequence for the next test, hence, I cannot use a clock pulse for advancement.  However, I am not sure how I could use a timer though?

IF TESTBIT (INPUT[1],1) THEN
   IF INPUT[1]+INPUT[2]+INPUT[3]+INPUT[4]+INPUT[5] & &HFFFD THEN    'CHECK IF ANY OTHER INPUT #1 TO #16) IS ON
      CALL 2:
      SETLCD 2,1,D$+"A3 &"      
      CALL 8:
   ELSE
      IF CTRPV[1]=1 THEN
         CTRPV[1]=2
         SETLCD 0,0,CHR$(1)
      ELSE
         CTRPV[3]=10
         SETLCD 0,0,CHR$(1)
      ENDIF
   ENDIF
ENDIF

7
Technical support / Re:Message display
« on: January 21, 2013, 10:53:32 AM »
That is helpful, however, it still won't work for my application as there will still be times that an error message will be displayed for a brief moment, every five seconds.  I will definitely use this for future programs on other projects.

I do have another question.  I have a sequence that advances every 1 second unless an error occurs.  Is there a way to monitor the sequence and set a bit on if the sequence does not advance for more than a second?  If there is a way, it will totally solve my issue since I can use that bit in my HMI to change screens when that bit turns on.

8
Technical support / Re:Message display
« on: January 18, 2013, 10:38:32 AM »
Close yes.  The PLC is a part of a diagnostic tool I've designed.  
The diagnostic tool is attached to a piece of equipment that requires testing. When the user sees an error occur, they fix the equipment.  When fix is complete, the PLC sees the error disappear and the program continues.  The next test does not occur until the current fault is eliminated.  When all the tests within the program pass, that indicates the equipment is good.

My issue is during the testing, the error messages are displayed for a brief moment, so a successful test, which takes a couple minutes, cycles through error messages every split second until it says "Test successful".  The program is able to perform the task well, but the display is not ideal for the end user.

9
Technical support / Re:Message display
« on: January 18, 2013, 09:39:49 AM »
Each test is performed in sequence and look similar to the sample I've shown. If the test is successful, the program moves forward to the next test, if there is an error, the error message is displayed continuously until the problem is resolved.  

In the ladder logic, each rung activates an output for use on the associated custom function test.  The issue is that even if there is no error, I see the error message for a brief instant and then it moves on to the next test with another error message for a brief instant.  

It seems I need a way to only show the errors if they last longer than 1 second.

10
Technical support / Re:Message display
« on: January 18, 2013, 04:14:00 AM »
That would work if all of my tests were happening at the same time, however, each of my 50+ tests happen in sequence and displays an error for a brief moment until it understands it is not an error and skips to the next test in the sequence.  

So calling a function every 5 seconds would only create a delay for this case.  However, this is useful for future programs on other applications for me.

The following is typical code for my custom functions.  I've also attached a *.jpg of the ladder logic, but I am not sure if it will show up....

'A3 OPEN TEST
IF TESTIO(A3_CS)=0 & CTRPV[1]=1 THEN
   CALL 1:
   SETLCD 2,1,B$+"A3" 'Line 2, Column 1
ELSE
   IF TESTBIT (INPUT[1],1) THEN
      SETLCD 0,0,CHR$(1)
   ENDIF
ENDIF
'SOCKET 33 TO A3 - NCS CONNECTOR TO NCS OPEN TEST
IF TESTIO (A3_CS)=0 & CTRPV[3]=9 THEN
   CALL 1:
   SETLCD 2,1,E$+D$+"A3"+G$+"2-A" ' LINE 2, COLUMN 1
ENDIF
'SHORT TEST
IF TESTBIT (INPUT[1],1) THEN
   IF INPUT[1]+INPUT[2]+INPUT[3]+INPUT[4]+INPUT[5] & &HFFFD THEN    'CHECK IF ANY OTHER INPUT #1 TO #16) IS ON
      CALL 2:
      SETLCD 2,1,D$+"A3 &"      
      CALL 8:
   ELSE
      IF CTRPV[1]=1 THEN
         CTRPV[1]=2
         SETLCD 0,0,CHR$(1)
      ELSE
         CTRPV[3]=10
         SETLCD 0,0,CHR$(1)
      ENDIF
   ENDIF
ENDIF

11
Technical support / Re:Message display
« on: January 17, 2013, 11:13:53 AM »
Clock pulse bit?  Is that the delay you are referring to?

My big issue even with that need to have some kind of default display like "testing..." that will stay on unless the errors become true.  It seems as each custom function occur the error is true for a brief moment until the PLC reacts to the inputs provided.

12
Technical support / Re:Message display
« on: January 17, 2013, 11:02:48 AM »
How do I perfrom a delay in the ladder logic?  

I have about 50 custom functions all which call up different variations of error messages if certain conditions are not met, so I would have to place the "delay" on each rung?  If so, what is the delay function?

13
Technical support / Re:Message display
« on: January 17, 2013, 09:42:48 AM »
This is what a typical part of my program looks like:

IF TESTIO(A3_CS)=0 & CTRPV[1]=1 THEN
   CALL 1:
   SETLCD 2,1,B$+"A3"
   DELAY 1000
ELSE
   IF TESTBIT (INPUT[1],1) THEN
      SETLCD 0,0,CHR$(1)
   ENDIF
ENDIF

By the time I get to the clear screen command, the error SETLCD 2,1,B$+"A3" is displayed for a brief moment in time.  I know the delay 1000 may be affecting it, however, without it my error messages flash too quickly.  Is there any way I can delay the message if it exists without delaying the cusfunc?

14
Technical support / Message display
« on: January 17, 2013, 05:44:04 AM »
I have a program that performs a large amount of tests in sequence and displays error messages and pauses the sequence until the error is cleared.

The problem is as the test runs, it displays each error for a short period of time which is something I do not want the user to see as they are not actually errors, they are just the program running.  I would like it to display something like "Testing..." until it has an error for more that 3 seconds which would indicate an actual error found.  Does anyone know how to approach this?  Or is there a function that can do this?

15
Technical support / Re:FMD1616-10 repair?
« on: October 11, 2012, 03:49:37 AM »
Tried that, but the outputs still remain on.  Is there any other chip that I should try changing?

Pages: [1] 2