Author Topic: Communication and Run-time errors  (Read 11664 times)

philipjoseph

  • Jr. Member
  • Posts: 57
    • View Profile
Communication and Run-time errors
« on: March 13, 2009, 07:57:42 PM »
Hi,
I have a T100MD1616 r33 with the RTC MODULE that has been working OK for a long time, now I try to change the program and set the E-mail function to get reports it does not accept and program. Right now the machine is working since I had another one in stock so I just loaded with the program.
In my office now I am testing the one that is failing and have these problems.
First the PAUSE LED was on. I switch Dip4=on, transfer the program (9800 Baud) Ok but none of the Output were working.
Change the BAUD to the normal 38400 checked no luck.
I download a simple program to test it:
I1 activate dcuf1 and i2 activate dcfn2.
dcfn1:
C$ = "SET-OUT3"
G$=C$
IF STRCMP (G$,C$)=0 THEN
SETBIT OUTPUT[1],2
CLRBIT OUTPUT[1],3
ENDIF
dcuf2:
C$ = "SET-OUT4
IF STRCMP (G$,C$)<>0 THEN
SETBIT OUTPUT[1],3
CLRBIT OUTPUT[1],2
ENDIF

Transfer the program ok.
When I try to monitor it, I have:

If I activate I1, Warning: Run time error in Fn#1 ERROR.Illegal memory access
If I activate I2, Warning: Run time error in Fn#2 ERROR.Illegal memory access
I close those warnings and then shows:
no response from node 3, Please check the following:
1 PLC ID=03 is connected to server
2 Check that the ID is correct.
I am using the COM1 and if I test the serial comms everyting ok.

I did remove the RTC MODULE and did again all the tests. Now I have THE PLC GOES TO PAUSE EVERYTIME I TRY TO RUN THE PROGRAM AND SHOWS:
Warning: PLC Program  failed checksum test (corrupted) please re-transfer the program to PLC.
I did a few times with the same result, later, I have:
Warning: Runtime error FN#1 Error: Illegal OPCODE- Please inform to the Manufacturer.

Is it any way to fix this plc?

Thanks
PHILIP
Philip.

support

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3174
    • View Profile
    • Internet Programmable PLCs
Re:Communication and Run-time errors
« Reply #1 on: March 13, 2009, 09:40:17 PM »
r33 firmware means that the PLC is probably more than 10 years old. I suspect some components on the device is faulty. Another possibility could be that the old firmware may not support some of the newer TBASIC commands. You may want to try to pure ladder logic to check if the PLC works. E.g. transfer the Demo.pc6 program to the PLC and see if it will work.
Email: support@triplc.com
Tel: 1-877-TRI-PLCS