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] 2 3 ... 207
1
Technical support / Re: Custom Function Editing Window Issue
« on: December 14, 2019, 09:34:29 PM »
The following links is a screen capture of an external 4K monitor connected to a 4K screen laptop with a GTX960M graphic card. Connection was via a HDMI cable.

https://www.triplc.com/smf/attachments/20191214/external4Kscreenshot.jpg

The i-TRiLOGI runs properly on either 4K monitors. We have tried different settings and font sizes on i-TRiLOGI and also mouse-over the buttons (see popup tooltip) but the function panels was never messed up like on your screen shot. 

Question - what display scaling did you use on your 4K monitor? We were using 125% and 100% scaling without any issue. Can you try with 100% scaling and see if it works for you?



2
Technical support / Re: Custom Function Editing Window Issue
« on: December 13, 2019, 11:32:00 PM »
You can change the font size of text in the Custom Function editor by pressing the F11 and F12 key, or hold down the "Ctrl" key and roll the mouse wheel. That should get you going for now until there is resolution.

We have developed the iTRiLOGI software on a 4K monitor and it has not shown any messing up of the windows so it is hard to conclude that there is a software problem - otherwise it should happen to every 4K monitor, not just a specific graphic card. We will try to test with other 4K monitors that we can get hold of to see if we can repeat your case, but do understand that it is not possible for us to chase every graphic card available on the market since 4K support on Windows is often a touch and go and is not officially supported by our software even though we have do what we can to make it simpler for 4K user.

3
Technical support / Re: Custom Function Editing Window Issue
« on: December 11, 2019, 01:02:08 AM »
No it should be 32-bit JRE. I thought you may have installed 64-bit JRE which won't work properly.

For graphic card RTX2060 - unfortunately we don't have such a graphic card handy. If the graphic card driver screws up the display there is very little we can do on the Java source code side to mitigate it since it is not a programming issue but a glitch in the underlying interaction between the O/S, JRE and Java bytecode. Perhaps the glitch can be reported to the graphic card manufacturer to see if they have an updated driver software that will address the issue.

Meanwhile, you may want to keep the editing done on your laptop screen if it works well in the HD mode.
 

4
Technical support / Re: TBASIC Input On/Off Question
« on: December 10, 2019, 06:28:10 PM »
Without fully understand your program, we would like to jump in with some comments about using SETTIMERSV - this command changes the Set Value of the timer when it is activated, but does not activate the timer when it is executed.

On Nano-10 and FMD PLC we don't recommend sprinkling this function all over your TBASIC program as the set value change are not backed up in flash memory unless specifically forced to do so by the program. Timers' and counters' are normally preset during program transfer but TBASIC allows you to perhaps use a HMI to make changes when needed, but it is not meant to be changed all the time by a program.

If you want to two different timer values for an action you could use two separate timers. Alternatively, you can start a timer with a desired count down value anytime by assigning the time-out value to the TIMER[n] variable and clearing the timer contact. You do not need to change its Set Value using the the SETTIMERSV command.  Please check the following FAQ thread for explanation:

https://triplc.com/smf/index.php?topic=1046.0

5
Technical support / Re: TBASIC Input On/Off Question
« on: December 10, 2019, 04:58:31 AM »
Hi Gary,

Thanks for the excellent explanation. We couldn't have done it any better than what you did.

Just add a note to someone new to TBASIC - the variables represented by INPUT[] and OUTPUT[] are stored in internal memory and they are normally only synchronized to the physical I/Os at the end of the ladder logic scan. So it will be a mistake to monitor an input inside a TBASIC loop because these internal memory do not change state:

E.g.
WHILE 1
   IF TESTIO(IN5) EXIT: ENDIF
ENDWHILE

The PLC program will be stuck in the WHILE loop because IN5 will never be turned ON.  You can force the internal I/O to be updated using the REFRESH statement:

WHILE 1
   IF TESTIO(IN5) EXIT: ENDIF
   REFRESH
ENDWHILE

REFRESH statement will update the memory INPUT[] to the states of the associated 16 physical inputs. There is a penalty of I/O scan time being used each time you run the REFRESH statement (about 2ms for a FMD or Fx PLC, shorter for Nano-10) so you want to use it only when necessary.  Letting the ladder logic monitor changes in input and use it to trigger custom functions for TBASIC processing will normally be a lot more efficient than monitoring it inside a WHILE loop.


6
Technical support / Re: Fx2424 PLC backwards compatible with T100MD2424
« on: December 10, 2019, 12:08:45 AM »
Fx2424 is NOT a drop-in replacement for T100MD2424. In most cases you can get by with small modifications if you want to use Fx2424 to replace T100MD2424+. Note the following differences:

1) Output 7 and 8 on T100MD2424 are PNP type (ON = 24VDC, OFF = 0V DC).  All outputs on Fx2424 are NPN types (ON = 0V, OFF = open circuit (with weak pull up to 24VDC)

2) On T100MD2424+ the Analog output 1 and 2 shared the pins with analog input 7 & 8.  On Fx2424 the analog outputs are on their own dedicated pins.

3) On T100MD2424+ the PWM channel 1 and 2 are on output 7 and 8.  On Fx2424 the PWM channel 1 to 4 are occupying output 5 to 8

These difference may or may not be applicable to your applications, depending on whether you are using these features or output 7 & 8.

The exact same program that ran on the T100MD2424+ however can be compiled and transfer to the Fx2424. You just need to ensure that the special I/Os are wired to the correct terminals.

7
Technical support / Re: Custom Function Editing Window Issue
« on: December 10, 2019, 12:06:23 AM »
We have never encountered the issue you showed on your screen shot.

It is likely has something to do with the graphic driver.

You mentioned that the TRiLOGI screen display fine on your laptop screen. Does your laptop has 4K screen built-in or it is driving an external 4K monitor? Does it happen when you move the iTRiLOGI windows from your laptop screen to the 4K screen when resolution changed?

You may want to try to disable some graphic acceleration in graphics card as these sometime introduce incompatibility.

Are you using 32-bit Java JRE?


8
Technical support / Re: Custom Function Editing Window Issue
« on: December 04, 2019, 01:08:38 AM »
What is your iTRiLOGI version?

Try to upgrade to the latest version by following the "Help-> Upgrade TRiLOGI" link in your existing iTRiLOGI software and upgrade to version 6.6 or 7.2 which support 4K display on the 4K laptop that we tested.

If you already have the latest i-TRiLOGI and still having trouble with the Custom Function editor in 4K monitor, please post a screen shot of the custom function so that we can see what can be done.

9
Technical support / Re: web page 0.htm DM32 value display
« on: October 08, 2019, 06:34:21 AM »
If you have two 16-bit value, say lower 16-bit in DM[1] and upper 16-bit in DM[2], then you can form a 32-bit number by defining a variable in Javascript such that:

var data32 = DM[2]<<16 + DM[1]

You will need to know some javascript and jquery so that you can insert the value of the variable "data32" into the 0.htm page from the javascript file M.JS (in particular the refreshScreen() function) so that it will display on the 0.htm page.

10
Technical support / Re: Programming to PLC
« on: September 30, 2019, 03:21:01 AM »
You mentioned in one of your emails that you have T100MD+ PLC which is EOL 8 years ago.

Anyway, it sounds like either someone has put a password in the PLC or the EEPROM is corrupted or damaged. You can try to use TRiLOGI software to transfer a program into the PLC and it will ask you if you want to delete the password and select yet. After you have transferred the program you can turn power off to ON again and see if the new program works. If the new program is not retained then the EEPROM is damaged and you may need to purchase a replacement.

12
Technical support / Re: Max frequencies on regulare input
« on: September 26, 2019, 11:29:10 PM »
The FMD1616 PLC has an I/O scan time of 2ms. The program scan time depends on how your program is written and can vary.

If you only run a couple of rungs of ladder program and it does nothing more than just count pulses it may be able to handle up to 200 Hz. But if you have custom function that may take up long time (e.g. communicating with 3rd party devices via serial or Ethernet port) then the time varies. It is best if you use a separate FMD88-10 which has 4 interrupt inputs and 4 regular inputs and if this slave PLC does simple counting you should be able to handle your 30 to 50Hz pulse inputs.

13
General Discussions / Re: Double debounce design
« on: September 20, 2019, 03:21:27 AM »
Looks like a good circuit. We would have done it similarly.

One other way is to use custom function and sample the input change with refresh and DELAY statement. You want to ensure that once an input is turn ON it last for at least 100ms without changing state.  It will use less ladder logic but with more codes in custom function. Also the scan time is longer using a custom function since the CPU blocks at the CF that samples the input. So ladder circuit with timer is still the most efficient way to achieve this.

14
Technical support / Re:User written Modbus RTU example code
« on: June 19, 2019, 03:14:39 PM »
Thanks for the great contribution to the community!

15
Each time when you make a Modbus TCP connection to the (3rd party) Modbus TCP server you have to wait for the connection to be made before you can run the READMODBUS or WRITEMODBUS command successfully.

Since you have two Modbus TCP server devices and there is only one client port on the FMD PLC, you have to make a connection, check that the connection is successful, the perform the READMODBUS or WRITEMODBUS command, then check STATUS(2) to ensure that you get a good result. Finally close the connection. You then connect to the second device and you must do the same by checking that the connection is made then READ or WRITEMODBUS command, check the communication status, then close the port.

It can be done on the fly reasonably fast especially the the devices are all on a LAN.


Pages: [1] 2 3 ... 207