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

2987
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.

2988
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.

2989
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.

2990
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

2991
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)

2992
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


2993
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?

2994
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?

2995
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.

2996
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.


2997
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?

2998
Technical support / Re: PulseFrequency & Input #3
« on: April 21, 2003, 03:12:54 PM »
No, if the input is used as pusle measurement then it cannot be used as high speed counter anymore. You can feed the input from to both input #3 and #5 and use the second channel of HSC for counting distance.

There is no simulation for pulse measurement function. Input #3 on the TRiLOGI is purely a digital input only. On the M-series PLC the it happens to share the pulse measurement input with input #3 but in other PLCs design in future this may not always be the case.

2999
Technical support / Re: recieving ASCII charcters
« on: April 21, 2003, 09:42:10 AM »
Contrary to your statement, the T100MD888+ PLC is fully capable of receiving binary data using the INCOMM command. It will return whatever binary data it receive one character at a time until buffer is empty and then it will return -1.

Do you have an LCD display? If not, how are you going to show the characters received by the PLC? You can't use the same COMM port for receiving character from the 68HC12 and use it for on-line monitoring because the TRiLOGI software online monitoring sends commands continuously to the PLC and will fill up the buffer quickly.

For what you tried to do (i.e. to have the PLC received the ASCII character for "5" followed by a CR), you can use a clock pulse to periodically check the serial port input and find out if you receive the string "5". If so, turn on an output:
   Clk:1.0s                     Fn_#1
|--||----------{dCusf}

within Fn_#1:

A$ = INPUT$(1)
IF LEN(A$)<> 0
   IF VAL(A$)=5  
        SETIO  OUT1
   ENDIF
ENDIF

If the PLC receive the string "5" it will convert it into integer if it finds that the value received is indeed equals 5 it will turn on the output with label name "OUT1". (You need to define an output with the label name "OUT1" for the program to compile properly.)

There are also many factors to consider for a successful communication. The baud rate and communication format settings must be the same for both the PLC and your 68HC12 board.  You have to make sure that everything are set up properly before trying to verify the communication result.


3000
Technical support / Re: T100MD2424+ & DC Motor Noise
« on: April 25, 2003, 06:52:29 AM »
Did you add any snubbing capacitor across the power terminal of the brush motor to absorb the spark that could occur during the rotation? This not only could resolve the problem but will protect the brush contact in the motor.

If the PLC is not sending out pulses to the stepper controller but yet the stepper motor starts turning when the motor turns, then the noise is actually picked up by the stepper driver and  not by the PLC. Most likely the noise is either picked  up by the connecting wire between the PLC and the stepper driver or from the power supply. Is the 24V power supplied shared by the PLC, the motor and the stepper driver?

Does your stepper controller have an optocouple to isolate the signal? If the stepper driver uses TTL signal for its control signal then it is more suspectible to noise pick up than optocouple type.

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