Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Technical support / Implementation of a Stack or LIFO in TBASIC
« Last post by garysdickinson on January 06, 2020, 11:31:35 PM »
This post shows how to implement a stack or Last In First Out data structure in TBASIC.

This example builds the stack in DM32[]. 
The size and location of the stack is controlled by entries in the #Define table.
Separate custom functions to initialize, push data and pop data are written to be as small and fast as possible.

The Stack.PC6 file is attached to this post. This is test bed code that will run in the i-TRiLOGI  simulator. This code should be easily adaptable for many uses.

The next post will have post a bit of documentation on how the stack operates.

Best regards,

Gary Dickinson
12
Technical support / Re: MT8050i to a FMD88-10 missing file called TRI_FX.si ?
« Last post by mikmet on January 02, 2020, 04:28:04 PM »
Got it from KEP!
13
Technical support / MT8050i to a FMD88-10 missing file called TRI_FX.si ?
« Last post by mikmet on January 02, 2020, 03:25:14 PM »
I'm having some trouble here connecting a MT8050i to a FMD88-10 with a CABLE-6050 via RS-232 on a prototype system.
I can connect to both units with ethernet.  I can download to both.  PLC is running program and is also talking to LCD. 
I installed the drivers and have the TRI_FX loaded local, so everything looks good.
I do get an error on the download to HMI about a file called TRI_FX.si
It appears I am missing this file from local drive, and it it not in the driver package that I downloaded from TRI in a zip file.
Does anyone have this file?
14
Technical support / Re: Custom Function Editing Window Issue
« Last post by DW_Microsys on December 17, 2019, 03:14:24 PM »
With DP cable, it works better, but still has massed up screen.
The card you tested is GTX, not RTX; and GTX is q quite old graphic card.
I have another laptop with GTX1060, it works smoothly never give an issue.
So there must be something between card driver and the java version you use.

15
Technical support / Re: Custom Function Editing Window Issue
« Last post by support 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?


16
Technical support / Re: Custom Function Editing Window Issue
« Last post by DW_Microsys on December 14, 2019, 09:07:13 PM »
More update:
My laptop has both HDMI port and mini Display Port.
I purchased a high quality DP-HDMI cable and connect to 4k Samsung TV.
So far it works without issue for about 3 hours.
I will post some update tomorrow or Monday.
When you test 4k monitor, did you test via HDMI, or DP?
Strange.
17
Technical support / Re: Custom Function Editing Window Issue
« Last post by support 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.
18
Technical support / Re: Custom Function Editing Window Issue
« Last post by DW_Microsys on December 13, 2019, 04:53:48 PM »
I did more investigation - looks like it related to the "mouse over" function. Please check.

Best regards,
19
Technical support / Re: Custom Function Editing Window Issue
« Last post by DW_Microsys on December 13, 2019, 03:58:23 PM »
Keep the window on Laptop is not ideal solution - the font size is too small compare to 55" 4k monitor.
Since it only happens with Trilog, I would think still there is something on your side. Loos like the function editing window got massed up when the window tries to referesh.

Please check on your side to find a solution.

You do need to get a RTX2060 cards on your site to test.

Best regards,

Daniel
20
Technical support / Re: TBASIC Input On/Off Question
« Last post by garysdickinson on December 11, 2019, 11:19:34 PM »
Jeff,

Good to see that you got something that works for you.

If this code is something that has to be maintained, I’d suggest using the "names" of things rather than the numbers.  As an example TIMER #9 was assigned the name "GndrTmr" in the "I/O Table tab in the i-TRiLOGI app.

So TimerPV[9] and TimerPV[GndrTmr] are equivalent.  The second version makes more sense.  The other reason for using the Itepms name rather than the number is that it is possible to re-arrange the Timers in the I/O and then TimerPV[9] may no longer refer to the GndrTmr.

The same goes for GetTimerSV(15).  Which timer is #15?  Use the name and not the number.

You will find that this convention of numbers and names for references includes things like custom functions, COUNTERS, TIMERs and several other things.

The use of “then" is optional.  It was probably put into TBASIC for the same reason as was the optional "let" keyword.  I suspect that this made TBASIC look more like Dartmouth BASIC from 1964 or Apples integer BASIC from the 1970s...  There is no reason to include this useless keyword.

The use of the "refresh" statement is interesting.  TRI has only documented the refresh statement in terms of updating both the internal copy of the physical INPUTs and making the internal copy of the OUTPUTs become the physical OUTPUTS.  This is normally handled by the before the first line of ladder logic is executed (INPUTSs) and after the last line of ladder logic is executed for the OUTPUTs. 

There is no mention  in TRIs documentation about refresh affecting the State of RELAYs.  You may be on to something!

Gary D
Pages: 1 [2] 3 4 ... 10