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]
16
Technical support / Re:Cascading expansion boards
« on: October 10, 2012, 09:52:21 AM »
Ok figured it out.  Once I reached output 40 in the program, the hardware skips the next 16 bits, so I can't use outputs 41 to 56, however, output 57 and up do work!  I guess the first 16 bits are reserved for a PLC's I/O even though the expansion is connected to another expansion?  

I wonder what happens to a PLC with less or more than 16?

At least I have it working with my program now  ;D

17
Technical support / Re:Cascading expansion boards
« on: October 10, 2012, 07:58:47 AM »
I have even tried deleting everything in my program and only leaving code that turns on an output for the second board.  It still doesn't work???  However, if I start a new program it does.  Is there something to reset the I/Os I don't know about?

18
Technical support / Re:Cascading expansion boards
« on: October 10, 2012, 06:17:06 AM »
I've tried a blank program and forcing outputs,  both expansions work.

I've tried a very simple program that turns on an output, both expansions work.

In my main program, the first expansion operational, but the second expansion still does not function.  I've even placed a line of code that simply turns on an output to the second board, and still nothing turns on, although the online monitioring screen shows the output as being on.  Really scratching my head on this one  ???

19
Technical support / Cascading expansion boards
« on: October 09, 2012, 05:36:55 AM »
I am using a FMD1616-10 with two EXP4040, however, the second expansion board is not operating.  The power light is on for both expansion boards and each works fine individually with the PLC, just not together.  

Is there something I need to do to the code to allow it to recognize the I/O beyond 40?

20
Technical support / Re:Saving space
« on: October 01, 2012, 08:19:03 AM »
That's a neat little trick, unfortunately,  I inserted the code as
CALL 1, CALL 2, etc.... to save additional space and the trick doesn't work unless I use the name.

21
Technical support / Re:Saving space
« on: September 25, 2012, 09:48:06 AM »
Makes the program a little bit harder to follow, but it saved a significant amount of space.  Thank you  ;D

22
Technical support / Saving space
« on: September 24, 2012, 04:52:46 AM »
I have a very large program, however, there are a lot of areas that have repeat commands such as:

SETLCD 0,0, CHR$(1)
SETLCD 1,1,A$

Is there anyway to put the entire "SETLCD...." into a string?

Or any other tips for space saving would be appreciated.

23
Technical support / Re:Triggering the sequencer
« on: September 20, 2012, 07:48:01 AM »
Figured it out, I used the CTRPV[1]= to set the value of the counter after each CusFn was satified, thus, providing the sequence I need.

Hope that helps someone :)

24
Technical support / Triggering the sequencer
« on: September 20, 2012, 04:36:12 AM »
I've been having troubles with setting up a sequencer.  
I have the basic arrangement in the ladder logic, however, I want the sequence to change each time one of the CusFn of each rung completes and I am unsure what code I can place in there to make this happen.  I tried a SetIO xxxx, CLRIOxxxx at the end of the code, but it doesn't seem to be working.  All I need is some bit to go from on to off to trigger the AVseq.  Any help would be appreciated.  

25
Technical support / Re:Monitoring and comparing IO
« on: September 18, 2012, 10:04:23 AM »
 ::) Oops nevermind, I put the wrong hexidecimal number in  :P

26
Technical support / Re:Monitoring and comparing IO
« on: September 18, 2012, 09:41:20 AM »
I've noticed that even when input #3 is on and inputs 1# to #16 are off, the message...

  SETLCD 0,0, CHR$(1)
  SETLCD 1,1,"SHORT CIRCUIT BETWEEN"
  SETLCD 2,1,"PIN A3 &"

...still remains, should it not disappear?

27
Technical support / Re:Monitoring and comparing IO
« on: September 18, 2012, 05:36:49 AM »
Awesome!  I didn't realize that (INPUT[1],2) corresponded to input #3, I thought it was #2.  The mask out info helped as well.  If works now, thank you very much  ;D

28
Technical support / Re:Monitoring and comparing IO
« on: September 17, 2012, 11:27:34 AM »
Thank you, it sort of works, but there is still an issue.  My code looks like this:

IF TESTBIT (INPUT[1],2) THEN
 IF INPUT[1] & HFFFE THEN
  SETLCD 0,0, CHR$(1)
  SETLCD 1,1,"SHORT CIRCUIT BETWEEN"
  SETLCD 2,1,"PIN A3 &"
  CALL 8:
  DELAY 1000
ENDIF
END IF

CALL 8 LOOKS LIKE THIS....

IF TESTIO(A1_CS)=1 THEN
 SETLCD 3,1,"PIN A1"
 DELAY1000
ENDIF
IF TESTIO(A5_CS)=1 THEN
 SETLCD 3,1,"PIN A5"
 DELAY1000
ENDIF
IF TESTIO(A7_CS)=1 THEN
 SETLCD 3,1,"PIN A7"
etc......

The problem now is the messages only appear if the first A5_CS occurs.  If the other inputs are ON, they cycle, which is fine, however, if A5_CS is gone, the rest will not display their message.

29
Technical support / FMD1616-10 repair?
« on: September 17, 2012, 04:13:41 AM »
A while ago an accident occured where something happend to an output and one of the sink driver chips ULN2803APG fried.  I swapped out the chip with a new one, however, now all the outputs 9-16 simply remain on.  

Is there anything I could change to fix them problem or is the PLC toast?

30
Technical support / Monitoring and comparing IO
« on: September 17, 2012, 03:55:22 AM »
I am using a T100MD1616+ and a MMI6050 and have run into a few issues with my project.

I want to monitior and compare inputs.  For example, if input 1 is on and any other input or combination of inputs turns on, I want to be able to distinguish this and output an error message.  Is there a command line to compare and monitor all the inputs?  
TESTIO (1-20) something like that.  


Pages: 1 [2]