Hello,
Maybe someone can help?
When I create a shortcut with Ignition Client Launcher and use that shortcut, the hrDisplay opens with incomplete data (first screenshot). It may begin with full data for a moment and then go to the wrong display again.
When I launch the app inside Vision Launcher, it works properly (second screenshot). But we need to use a shortcut to launch it automatically with the startup folder.
In your Vision Client Launcher, are there any client tag overrides present for that project? The shortcut in the folder might not have those overrides included.
Without any other information on how exactly your screen in configured, its going to be difficult to provide specific help.
Are there any errors or warnings in the vision client logs when you launch via the shortcut? You can check via the diagnostics menu when the client is running by pressing Ctrl + Shift + F7.
Nothing was open when I use Ctrl+Shift+7
I also tested and rarely it opens normally with shortcut, but 99% is doesn't. It opens normally via shortcut just at the beginning for a 2-3 seconds, but then it go to this screen again. And this behaviour observed on all our computers (desktops, laptops, mini-PCs) running Windows 10 or Windows 11.
I have an access to the designer. Can I check something over there?
Designer is isolated from the clients so you wont be able to view logs or anything diagnostic. Are there any startup scripts on the project or page? What drives the tables normally?
For the time being, you can adjust the project properties to show the built in client menu bar to be able to access the diagnostic menu.
This is the only script I see in the root container
if event.propertyName == 'allData':
allData = system.dataset.toPyDataSet(event.source.allData)
# do math to find correct length of split datasets
rowCt = len(allData)
tablePartitionLen = rowCt/3
leftoverRows = rowCt - (3*tablePartitionLen)
ds2AddRow = False
ds3AddRow = False
ds1Len = tablePartitionLen
ds2Len = tablePartitionLen
ds3Len = tablePartitionLen
if leftoverRows == 1:
ds1Len += 1
ds2AddRow = True
ds3AddRow = True
elif leftoverRows == 2:
ds1Len += 1
ds2Len += 1
ds3AddRow = True
# create datasets
emptyRow = [None, None, None, None, None, None]
tbl1Data = system.dataset.toDataSet(allData[:ds1Len])
tbl2Data = system.dataset.toDataSet(allData[ds1Len:(ds1Len+ds2Len)])
if ds2AddRow:
tbl2Data = system.dataset.addRow(tbl2Data, emptyRow)
tbl3Data = system.dataset.toDataSet(allData[(ds1Len+ds2Len):])
if ds3AddRow:
tbl3Data = system.dataset.addRow(tbl3Data, emptyRow)
event.source.getComponent('tbl1').bufferedData = tbl1Data
event.source.getComponent('tbl2').bufferedData = tbl2Data
event.source.getComponent('tbl3').bufferedData = tbl3Data
event.source.currentStartRow = 0
The script itself doesn't seem to have any issues.
I'd venture a guess that the driving query for allData is not returning the rows expected/configured on the table (capitalization matters). The client is loading in with the values from the designer, then the query finishes and has different columns than expected. Not sure why this would happen only for something launched via shortcut.
Just double checking, this is the only view in this project? Did you try rebuilding the shortcuts? (delete and create new via launcher)
I tried to rebuild the shortcuts, it didn't help.
I agree, I would expect if there was a problem with the shortcut then either Vison would not launch, or it would not be able to find the project. Since that is not happening, I tend to agree with your assessment that something is wrong with the query.
@anzhelika.jumangit how is the binding on the table configured?
There is no binding.
Our scheduling clerks are updating the .csv file on the shared drive, and after updating, the data populates to the client automatically.
We have had this issue for a long time already, but there is no solution yet, except to manually reopen it from inside the launcher.
The weird thing is that it opens normally via shortcut for a few seconds. Sometimes, but very rarely, it stays in the correct display via shortcut. But when opening hrDisplay from inside the Vision Launcher, it works properly all the time.
I tried cleaning the cache, reinstalling the app, restarting the computer, re-creating a shortcut, and editing the shortcut properties to maximize the window, but nothing worked.
This is always going to be fragile. You should use a database, not a CSV.
2 Likes
Thank you, I will let our Automation & Control Team know. I am an IT support, and I am not managing the Ignition.