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 - support

Pages: 1 ... 198 199 [200] 201 202 ... 212
2986
Technical support / Re: E10-npn RS232 Communication
« on: April 10, 2003, 06:43:23 AM »
T100MD+ has two comm ports: comm1 is RS232 and comm3 is RS485. ?There is no comm2 for T100MD+ (comm2 is only available on T100MX+).

So your statement should be

Print #1 "ATO" ? ?'Initial Communication with Modem
Print #1 "ATDT6567418892" 'Dials to call ?Singapore

Of coure you need to add the outgoing international calling code (011 in USA) before you can call an international number such as the above.

The PLC will send the above string out via the COMM1 port to the modem. We have sample program in the "usr\samples\FileService_modem" folder that connect the PLC to a remote TLServer via modem. Please check out the following link for more info:

http://www.tri-plc.com/TLeval/Help/plc2modem.htm


 


2987
Technical support / Re: E10-npn RS232 Communication
« on: April 08, 2003, 04:53:58 PM »
That's right. E10-npn RS232 port is only meant for programming via our proprietary software. There isn't a published set of communication protocol for the E10.

The T100MD+ PLC can operate at 12 to 24VDC.


2988
Technical support / Re: E10-npn RS232 Communication
« on: April 08, 2003, 02:49:11 PM »
Modem don't usually send AT command to the PLC. It is the PLC that send AT command to the modem.

A $199  T100MD888+ can format whatever AT command needed and send via the serial port to the modem. It can also interpret any incoming text string or binary data in whichever way you want.  It is fully under control by your TBASIC program.


2989
Technical support / Re: E10-npn RS232 Communication
« on: April 08, 2003, 11:44:55 AM »
E10 is not suitable for the applications that you described. Try a T100MD888+. It is extremely versatile and can easily handle what you want to do.

2990
Technical support / Re: About timer...
« on: April 10, 2003, 05:07:12 PM »
You can use a 1 minute clock "Clk:1min" to toggle a down counter with preset value of 30. So the counter will count down every minute and when it reaches zero, its contact is turned ON. That can be used just like a timer.

2991
Technical support / Re: "dual Modbus Master/Slave
« on: April 14, 2003, 12:14:39 PM »
Yes, as long as the PLC program is not actively sending any modbus command out of COM1, the communication port is immediately available as a slave port. i.e. the same comm port can work both as a master and a slave.

You will have to take care of the "arbitration" issue, meaning that you have to ensure that the PLC will not talk on the COM1 when it is supposed to listening to incoming command. Otherwise a collision will occur and both incoming and outgoing command will be lost.

2992
Technical support / Re: Calculation with decimal point
« on: April 14, 2003, 12:27:05 PM »
You can use fixed point arithmatics. Assuming every unit represents 0.01:

T = 2557 - 1249*A/100000

(Make sure that  you multiply by A first before dividing by 100000)

The resulting value T is x 100.

You can store value of T in timer #1 S.V using SETTIMERSV.

You can store it in timer #1 P.V (present value using  TIMERPV[1] = T.

If you define timer #1 as High speed timer then each unit of T represent 0.01s.

2993
Technical support / Re: ACS II Command of Wireless Modem
« on: April 14, 2003, 08:28:50 PM »
For control character ASCII table, check the followings:

http://www.cs.tut.fi/~jkorpela/chars/c0.html

2994
Technical support / Re: ACS II Command of Wireless Modem
« on: April 14, 2003, 06:36:51 PM »
Use CHR$(n) to send non printable character. For what you want to do, execute the followings:

E.g. Print #1 "AT+CMGS=1, 1234567"+CHR$(13)+CHR$(10)+ CHR$(26)

2995
Technical support / Re: Host Communication
« on: April 15, 2003, 08:20:45 AM »
I checked your program, you should change all the custom functions to differentiated format. i.e. use the {dCusF} and not the {CusFn}.

When you use {CusFn}, every time when it executes, it continuously write to the EEPROM using the SETTIMESV command. This is very bad for the EEPROM because you can overwrite it for more than 100,000 times very quickly and wear out the EEPROM.

Secondly, when the EEPROM is being written, the system interrupt is turned OFF to protect the integrity of the data. This explains why you have no communication because the PLC communication interrupt is also turned OFF and would not accept serial command.

When you use the {dCusF} command, the SETTIMERSV only executes once when the logic is true and this will not have any impact on the communication because the interrupt is only turned off briefly.

Regards,
support@tri-plc.com


2996
Technical support / Re: Host Communication
« on: April 14, 2003, 08:12:01 PM »
Is your program sending out data out of the COMM1 port? (i.e. execution of PRINT, OUTCOMM, NETCMD$, READMODBUS or WRITEMODBUS commands).  That will interfere with the PC trying to talk to the PLC.  Did you execute SETBAUD command has changed the COMM1 settings?

2997
Technical support / Re: Host Communication
« on: April 14, 2003, 12:22:26 PM »
Please describe your experience more clearly.

1) What software are you using to send the "ASCII" command?

2) Are you using TLServer to send the command? TLServer only accept the "multi-point" host link command (except "IR*" command, which is point-to-point) of the format "@nnHHxxxxff*". You will have to configure the command correctly and send to the PLC.

The T100MD PLC accepts a few different protocols:

a) Native hostlink command (as described above)
b) MODBUS RTU command
c) MODBUS ASCII command

You have to send command in the format acceptable by the PLC in order to get a response.

3) You have to check to ensure that the COM port is correct, the PLC is not currently writing out of COM port using PRINT, OUTCOMM or NETCMD$.  All these are factors that can affect the communication.

Are you able to perform online monitoring and program transfer using TRiLOGI software?

2998
Technical support / Re: WRITEMODBUS command
« on: April 17, 2003, 06:45:48 AM »
READMODBUS uses function code 03 to read 16-bit register from a MODBUS slave.

Note that if your slave is RTU, the COMM port number to use is 11 for communicaiton via COMM1 and 13 for communication via COMM3.

2999
Technical support / Re: WRITEMODBUS command
« on: April 16, 2003, 06:41:23 PM »
Sorry, the WRITEMODBUS command only send out using MODBUS function 16 and not function 05.  Please consult your RTU supplier on how to address the DO using function 16 which is the most generic form of MODBUS command and should be supported by any RTU claimed to be MODBUS compliant.

If you are able to compute the CRC16, then you can also choose to send out MODBUS command using the OUTCOMM. First store the bytes inside the DMs and then use a FOR..NEXT loop to send out one byte at a time.


3000
Technical support / Re: cant run tl51edu
« on: April 18, 2003, 04:45:12 PM »
jbuilder may have its own JVM but we are not sure whether it is able to run .jar file directly. Why don't you just install the JRE from sun website and try again?

Pages: 1 ... 198 199 [200] 201 202 ... 212