We have several SQLbridge modules - “distributed”, and “main” one SQLBridge and VisionModule, all works in one LAN
“Distributed” SQLBridge function:
1)is to gateway between two OPC-servres using DBtags. (trying also transaction groups w/o success). 2)here we use only one SQL DB driven Tag provider.
3)Tag configuration stores only here in DB
“Main” one function:
Connected to “distributed” DB
Using Real Time DB provider it wokrs with “distributed” Tags
Problem 1
We configured “distributed” functions, but just we starting to use “distibuted” tags on “main” server all tags goes to “Stale” state and it looks like it stoped to execute on “distributed” machines cause OPC-gateway dont work.
Problem 2
We try to import tags from csv format, but the Designer appears to start creating some of the tags, but then after a few seconds progress will stop with “Waiting for Gateway”. The request will eventually timeout after 60 seconds.
Once the timeout occurs the database tag provider on the gateway appears to be hung. If the tag referesh icon is selected, the Tag Provider only displays the “Waiting” icon until the gateway once again times out after 60 seconds.
This problem is similar to viewtopic.php?f=72&t=7302&p=22078&hilit=Driving+Provider#p22078 but it occurs in 7.3.2
So, to clarify, the tags provided by the remote Ignition appear stale when viewed from the central Ignition? Do they look correct when viewed on the Ignition that is driving them? Do you see the values changing?
The staleness is calculated based on the information in the “sqlth_sci” table. Depending on the database and on the time zones of the two machines, problems can sometimes arise. Which database are you using, and are the two machines (and the database, if it’s on a 3rd machine) in different time zones?
[quote="Colby.Clegg"]Hi,
So, to clarify, the tags provided by the remote Ignition appear stale when viewed from the central Ignition? Do they look correct when viewed on the Ignition that is driving them? Do you see the values changing?
[/quote]
From central ignition: tags are stale
Driving tags machine: tags are good quality, but not changable - write timeout, values not updates from OPC
MySQL
DB hosted on the Driving Tag Machine
TimeZone is the same
On the driving machine, do you have errors in the console section of the gateway?
Also, make sure that the driver names are correct: in each of your driving providers, you need to specify a driver name (the default is “ignition”, but it must be different for each driving provider). And then, the tags from each system must be configured to use that driver name.
What are the values that are currently in the “sqlt_drv” table? Also, when you view the “sqlt_sci” table, do you see the “lastexec” timestamp increasing? Finally, how many tags are there in each system?
[quote]On the driving machine, do you have errors in the console section of the gateway?
[/quote]
actually i need stable local system on tag driven machine and reconfigure Ignition with internl tag provider...
all is fine
i have 3 columns (Driver name, Ip address, port):
Floor4
192.168.90.140
5500
How i can open this table? I use the MySQL Workbench it cannot open this table because it doesnt have a primary key.
So, tags on driving machine executed and are GOOD Quality. In the sqlt_sci i have see the “lastexec” increasing. On the local machine i have stale tags. Day and time of each machine need to be sincronized or may be i need set some “time settings” in DB?
On the local machine, try running this query and see what the result is:
select sc_id,drivername, nextExec-CURRENT_TIMESTAMP from sqlt_sci;
If the time difference is negative, something must be strange. The system that monitors staleness actually gets the database time, and then loads the scan classes, and compares them… so the time on your local machine should actually make a difference.
Is there any way you can give me access to the database over the internet? I can’t see why the tags would be stale, there must be something that just isn’t lining up correctly. If you can put the box on the internet, you can create a login for me with just access to that schema or the sqlt_* tables, and PM me the details. If you can’t, that’s ok, we’ll just have to try something else.
Even though the values are stale, do you see the value changes coming through?
I cant give you remote accsess today, becouse the IT department is absent. I need to speak with them to configure the firewall for remote accsess. Maybe we can do something before tomorrow?
Yes i see the values changes even the tags are stale
I think i can give you the remote accsess via RDP to the main server. From it you can get the remote accsess to the tag driving machine. Is this a way?
The cause of this was a problem that has come up before, and I thought was fixed: the tag provider name for the consuming side (not the driver) was named the same as the “driver name” setting. This causes problems, as the non-driving provider thinks it’s responsible for the tags, when obviously it can’t “drive”. We’ll get this fixed, but in the mean time you can work around it by simply giving your tag provider a different name.