1
00:00:00,799 --> 00:00:03,040
Welcome back to The Automation Podcast, the world's

2
00:00:03,040 --> 00:00:05,839
number one industrial automation product and technology show

3
00:00:05,839 --> 00:00:08,639
thanks to you, our audience of highly skilled

4
00:00:08,639 --> 00:00:09,779
automation professionals.

5
00:00:10,160 --> 00:00:11,679
Thank you for being a member of our

6
00:00:11,679 --> 00:00:13,519
audience, and thank you for tuning back in

7
00:00:13,519 --> 00:00:14,964
this week. And if you're new to the

8
00:00:14,964 --> 00:00:16,804
show, my name is Sean Tierney from Insights

9
00:00:16,804 --> 00:00:17,464
and Automation.

10
00:00:18,004 --> 00:00:20,244
And in this week's episode, I meet up

11
00:00:20,244 --> 00:00:24,085
with Johan Cortez from Rockwell Automation to learn

12
00:00:24,085 --> 00:00:25,785
all about what's new in FactoryTalk

13
00:00:26,164 --> 00:00:28,904
Vue version fifteen and sixteen.

14
00:00:29,359 --> 00:00:30,560
But before we get to that, I have

15
00:00:30,560 --> 00:00:31,620
a couple of announcements.

16
00:00:32,079 --> 00:00:34,960
If you are a member at, YouTube or

17
00:00:34,960 --> 00:00:37,280
the automation blog or you're a student in

18
00:00:37,280 --> 00:00:39,700
my VSC course over at the Automation School,

19
00:00:39,920 --> 00:00:42,079
because this episode is not sponsored by the

20
00:00:42,079 --> 00:00:45,105
vendor, you will be getting an extended version

21
00:00:45,245 --> 00:00:46,385
of this episode

22
00:00:47,005 --> 00:00:49,245
commercial free. So I wanna thank all of

23
00:00:49,245 --> 00:00:51,565
you who are members or who have purchased

24
00:00:51,565 --> 00:00:54,365
my VSC course over at The Automation School.

25
00:00:54,365 --> 00:00:56,679
I actually have some new information coming in

26
00:00:56,679 --> 00:00:58,679
that VSC course, so keep an eye on

27
00:00:58,679 --> 00:01:00,200
that. You may wanna visit in the next

28
00:01:00,200 --> 00:01:02,039
week or two to check that out to

29
00:01:02,039 --> 00:01:04,439
learn what's coming for that course. Now that

30
00:01:04,439 --> 00:01:07,000
said, another public service announcement I have is

31
00:01:07,000 --> 00:01:10,334
that I'm actually holding programmable controller training here

32
00:01:10,575 --> 00:01:13,135
the week of April 21. So this is

33
00:01:13,135 --> 00:01:15,715
the first training I'm doing publicly open enrollment,

34
00:01:16,494 --> 00:01:16,994
for,

35
00:01:17,375 --> 00:01:19,854
classes right here. And it's I think I'm

36
00:01:19,854 --> 00:01:21,614
doing something unique that you will not find

37
00:01:21,614 --> 00:01:23,775
anywhere else. You can choose whether you wanna

38
00:01:23,775 --> 00:01:25,780
do one to four days, and you can

39
00:01:25,780 --> 00:01:26,840
also choose

40
00:01:27,299 --> 00:01:29,219
which PLC you wanna learn on each of

41
00:01:29,219 --> 00:01:30,659
those days. So you could come and learn

42
00:01:30,659 --> 00:01:31,399
on CompactLogix

43
00:01:31,859 --> 00:01:33,859
all week, or you could choose two days

44
00:01:33,859 --> 00:01:36,259
of CompactLogix and two days of Microw 800.

45
00:01:36,259 --> 00:01:37,939
I actually have one student who's just coming

46
00:01:37,939 --> 00:01:39,780
for two days of Microw 800. That's all

47
00:01:39,780 --> 00:01:41,784
he needs to know. And, you could choose

48
00:01:41,784 --> 00:01:43,545
s seven twelve hundred. You could even mix.

49
00:01:43,545 --> 00:01:44,745
You could do a day of s seven

50
00:01:44,745 --> 00:01:46,504
twelve hundred, a day of micro 800, and

51
00:01:46,504 --> 00:01:47,405
a day of CompactLogix.

52
00:01:48,185 --> 00:01:50,344
So the equipment is limited. I do have

53
00:01:50,344 --> 00:01:51,885
eight setups of everything,

54
00:01:52,344 --> 00:01:54,520
but I'm limited on computers and space, so

55
00:01:54,520 --> 00:01:56,200
I can't have 24 people here at the

56
00:01:56,200 --> 00:01:58,520
same time. So if you're interested in some

57
00:01:58,520 --> 00:02:00,859
hands on training, we're one hour East

58
00:02:01,319 --> 00:02:03,960
of Albany, New York. Okay? So two and

59
00:02:03,960 --> 00:02:06,359
a half hours West of Boston. So if

60
00:02:06,359 --> 00:02:08,680
you're in the Greater Albany area or you're

61
00:02:08,680 --> 00:02:11,905
in Southern Vermont, Southern New Hampshire, Western Mass,

62
00:02:12,044 --> 00:02:13,824
you know, Eastern New York,

63
00:02:14,204 --> 00:02:15,965
we've even had people come as far as

64
00:02:15,965 --> 00:02:18,525
way as, Pittsburgh to come here. So if

65
00:02:18,525 --> 00:02:20,625
you're within driving distance, please,

66
00:02:21,084 --> 00:02:23,245
consider coming to that course if or sending

67
00:02:23,245 --> 00:02:25,080
somebody who works for you to the course.

68
00:02:25,319 --> 00:02:27,080
If you'd have somebody who needs to get

69
00:02:27,080 --> 00:02:29,639
some hands on with PLCs. I will also

70
00:02:29,639 --> 00:02:31,319
be doing lectures. This is not a dump

71
00:02:31,319 --> 00:02:33,000
and run where you sit in front of

72
00:02:33,000 --> 00:02:34,840
a computer all day with a lab manual,

73
00:02:34,840 --> 00:02:37,639
and you're not gonna get any valuable insights

74
00:02:37,639 --> 00:02:39,435
into the product. I will be doing lectures.

75
00:02:39,435 --> 00:02:41,375
I actually set up a second office here

76
00:02:41,435 --> 00:02:43,194
just to do the lectures. So when I'm

77
00:02:43,194 --> 00:02:45,355
doing Allen Bradley lectures, the Stevens guys can

78
00:02:45,355 --> 00:02:47,375
do their hands on and vice versa.

79
00:02:47,675 --> 00:02:49,995
So check that out over at the automationschool.com.

80
00:02:49,995 --> 00:02:51,675
And with those PSAs out of the way,

81
00:02:51,675 --> 00:02:53,375
let's go ahead and learn what's new

82
00:02:53,750 --> 00:02:54,489
in FactoryTalk

83
00:02:54,870 --> 00:02:56,650
Vue fifteen and sixteen.

84
00:02:57,669 --> 00:02:59,989
Johan, thank you for coming back on the

85
00:02:59,989 --> 00:03:03,189
Automation Podcast and Show. I'm really looking forward

86
00:03:03,189 --> 00:03:05,269
to getting this update on FactoryTalk Vue, and

87
00:03:05,269 --> 00:03:07,634
I know we had a great, episode when

88
00:03:07,634 --> 00:03:09,495
you came on to talk about Vue 14.

89
00:03:09,794 --> 00:03:11,235
And, of course, now we have fifteen and

90
00:03:11,235 --> 00:03:13,474
sixteen out. So I really appreciate you coming

91
00:03:13,474 --> 00:03:14,834
back on the show. And and for those

92
00:03:14,834 --> 00:03:16,514
who may not have caught that last episode

93
00:03:16,514 --> 00:03:18,194
we did together, could you just take a

94
00:03:18,194 --> 00:03:20,280
moment and introduce yourself to our audience?

95
00:03:20,599 --> 00:03:22,599
Sure. Yes. Thank you, Sean. And thank you

96
00:03:22,599 --> 00:03:24,520
for inviting me back to speak about what

97
00:03:24,520 --> 00:03:26,699
is new in Faculte VU software portfolio.

98
00:03:27,959 --> 00:03:28,919
As you noted,

99
00:03:29,240 --> 00:03:30,699
my name is Johan Kotsa.

100
00:03:31,080 --> 00:03:33,639
I am a product manager for Faculte VU

101
00:03:33,639 --> 00:03:36,965
site edition, Machine Edition, Viewpoint and Alarms and

102
00:03:36,965 --> 00:03:37,465
Events.

103
00:03:38,324 --> 00:03:40,645
I have been with Rockwell Automation for just

104
00:03:40,645 --> 00:03:43,625
over seventeen years. I actually began my career

105
00:03:43,764 --> 00:03:45,544
as a project engineer in

106
00:03:45,925 --> 00:03:48,724
South Africa within the system and solution business,

107
00:03:48,724 --> 00:03:51,439
which is now called our lifecycle Services business.

108
00:03:52,300 --> 00:03:53,920
And in 2016,

109
00:03:54,139 --> 00:03:56,879
I moved to The United States and joined

110
00:03:57,020 --> 00:03:59,020
the Plant PX team. So those that are

111
00:03:59,020 --> 00:04:00,960
familiar with the Plant PX team

112
00:04:01,260 --> 00:04:04,060
and the process libraries, I basically served as

113
00:04:04,060 --> 00:04:06,314
the Plant PX library architect for

114
00:04:06,635 --> 00:04:09,514
several years, in fact. And then later I,

115
00:04:10,875 --> 00:04:13,354
was part of the PlantPX system architect for

116
00:04:13,354 --> 00:04:16,074
around a year. And when you basically when

117
00:04:16,074 --> 00:04:17,055
we spoke last,

118
00:04:17,834 --> 00:04:20,860
I had just recently joined the visualisation business

119
00:04:20,860 --> 00:04:22,800
as the product manager for the visualisation

120
00:04:23,180 --> 00:04:23,680
software.

121
00:04:24,460 --> 00:04:26,860
I've been in this role now for going

122
00:04:26,860 --> 00:04:28,460
two and a half years. And,

123
00:04:29,180 --> 00:04:31,819
as I say, time goes by fast, right?

124
00:04:31,819 --> 00:04:33,120
So when you're having fun.

125
00:04:33,675 --> 00:04:35,454
So I'm just going to dive into

126
00:04:35,834 --> 00:04:36,954
the slides here.

127
00:04:38,555 --> 00:04:40,634
As I mentioned earlier, the last time we

128
00:04:40,634 --> 00:04:42,555
spoke, we reviewed what was new, in fact,

129
00:04:42,555 --> 00:04:44,014
at Talkview version 14.

130
00:04:44,954 --> 00:04:47,194
At the time, we described that release as

131
00:04:47,194 --> 00:04:49,230
one of the most feature rich updates,

132
00:04:49,710 --> 00:04:51,650
we had delivered in a long while.

133
00:04:52,110 --> 00:04:54,509
So today, I want want to highlight some

134
00:04:54,509 --> 00:04:56,430
of the key updates. In fact, Adobe Vue

135
00:04:56,430 --> 00:04:58,210
versions fifteen and sixteen.

136
00:04:59,069 --> 00:05:01,170
You will notice several common themes.

137
00:05:02,254 --> 00:05:04,274
We built on version 15 capabilities

138
00:05:04,654 --> 00:05:07,134
that resonated with our users and extended them

139
00:05:07,134 --> 00:05:09,055
to deliver more value in their day to

140
00:05:09,055 --> 00:05:09,714
day use.

141
00:05:11,055 --> 00:05:14,274
This session will really only scratch the surface,

142
00:05:14,334 --> 00:05:15,120
by the way.

143
00:05:15,519 --> 00:05:18,100
Both releases included many additional enhancements.

144
00:05:18,479 --> 00:05:21,040
My goal today is to cover a few

145
00:05:21,040 --> 00:05:24,079
highlights and demonstrate several features live during the

146
00:05:24,079 --> 00:05:24,579
session.

147
00:05:26,000 --> 00:05:27,704
So for those that may not

148
00:05:28,185 --> 00:05:31,404
be familiar, we released Facitalk v version 15

149
00:05:32,024 --> 00:05:33,675
in September

150
00:05:33,675 --> 00:05:35,084
2024.

151
00:05:35,865 --> 00:05:38,104
And the areas we will focus on today

152
00:05:38,104 --> 00:05:41,224
include support for external influx DB and influx

153
00:05:41,224 --> 00:05:42,365
DB cloud serverless,

154
00:05:43,310 --> 00:05:44,610
MQTT support,

155
00:05:45,389 --> 00:05:46,449
performance improvements,

156
00:05:47,629 --> 00:05:49,889
factory talk alarms and events, email notifications,

157
00:05:50,509 --> 00:05:53,709
and the runtime navigation menu support for,

158
00:05:54,750 --> 00:05:56,370
a multiple navigation menus.

159
00:05:56,750 --> 00:05:58,589
Yeah. And just to reiterate what Johan just

160
00:05:58,589 --> 00:05:58,964
said,

161
00:05:59,524 --> 00:06:01,204
there's a lot more things on this slide.

162
00:06:01,204 --> 00:06:03,044
So if you're listening, there's a lot more

163
00:06:03,044 --> 00:06:05,605
things on the fifteen and sixteen slide that

164
00:06:05,605 --> 00:06:07,125
we just can't get, you know, get to

165
00:06:07,125 --> 00:06:08,245
in one show. So,

166
00:06:08,564 --> 00:06:10,564
if you are listening, check out those two

167
00:06:10,564 --> 00:06:12,564
slides at the beginning of the presentation, and

168
00:06:12,564 --> 00:06:14,185
I'll turn it right back to you, Johan.

169
00:06:14,430 --> 00:06:16,830
Thank you, Sean. The same thing here. For

170
00:06:16,830 --> 00:06:18,990
those that may not be familiar, we're is

171
00:06:18,990 --> 00:06:22,039
Packetalk v version 16 in October

172
00:06:22,039 --> 00:06:22,930
2025.

173
00:06:23,470 --> 00:06:26,350
And, again, today, I will focus on several

174
00:06:26,350 --> 00:06:27,970
key areas of this release.

175
00:06:28,975 --> 00:06:32,574
First are new control objects. These include a

176
00:06:32,574 --> 00:06:35,615
toggle switch control and a linear gauge object

177
00:06:35,615 --> 00:06:37,154
with an integrated sparkline.

178
00:06:37,854 --> 00:06:40,354
And next are streamline navigation options.

179
00:06:40,899 --> 00:06:43,860
These updates include a runtime navigation sidebar that

180
00:06:43,860 --> 00:06:45,379
can be docked to the left and the

181
00:06:45,379 --> 00:06:46,360
right hand side

182
00:06:46,740 --> 00:06:49,720
and a new horizontal dock navigation submenu.

183
00:06:51,379 --> 00:06:54,279
We also introduced an enhanced system status portal.

184
00:06:54,615 --> 00:06:57,435
This allows, you to monitor Facetalk View Historian

185
00:06:57,495 --> 00:07:00,694
AC server statuses, which was introduced in version

186
00:07:00,694 --> 00:07:01,194
15,

187
00:07:01,654 --> 00:07:04,454
as well as Facetalk asset center server and

188
00:07:04,454 --> 00:07:05,435
agent status

189
00:07:06,055 --> 00:07:08,074
that was introduced in version 16.

190
00:07:08,479 --> 00:07:10,560
And then finally, what we're gonna focus on

191
00:07:10,560 --> 00:07:12,720
is what was added in version 16 as

192
00:07:12,720 --> 00:07:15,620
DataLog Pro integration with Influx DB three core

193
00:07:16,000 --> 00:07:16,819
and enterprise.

194
00:07:17,839 --> 00:07:20,079
Maybe just before I dive into the slides,

195
00:07:20,079 --> 00:07:21,839
something I just wanna note. I know this

196
00:07:21,839 --> 00:07:23,745
is sort of gonna be some people might

197
00:07:23,745 --> 00:07:24,805
not have the visuals.

198
00:07:25,185 --> 00:07:26,704
But if you do look at the visuals

199
00:07:26,704 --> 00:07:28,704
and there's a slide, you'll notice there's some,

200
00:07:29,185 --> 00:07:30,725
icons here at the bottom.

201
00:07:31,425 --> 00:07:33,345
So this is really where it's gonna show

202
00:07:33,345 --> 00:07:35,040
you in which product,

203
00:07:35,520 --> 00:07:36,740
this feature belongs.

204
00:07:37,120 --> 00:07:39,439
And some will have a little circle icon

205
00:07:39,439 --> 00:07:41,360
with a number in it with either 15

206
00:07:41,360 --> 00:07:42,100
or 16

207
00:07:42,560 --> 00:07:44,639
that will indicate in which version it was

208
00:07:44,639 --> 00:07:45,139
introduced.

209
00:07:45,600 --> 00:07:47,055
So I'm gonna try and keep,

210
00:07:47,535 --> 00:07:49,854
the topics, next to each other. So when

211
00:07:49,854 --> 00:07:51,774
I talk about something that was done in

212
00:07:51,774 --> 00:07:54,495
version fifteen and sixteen, those will just follow,

213
00:07:55,214 --> 00:07:57,074
next to each other in the slides.

214
00:07:58,334 --> 00:08:00,095
The one thing I really wanted to show

215
00:08:00,095 --> 00:08:00,595
here,

216
00:08:01,294 --> 00:08:04,430
most audience members here probably go to our

217
00:08:04,430 --> 00:08:06,289
ROQ Automation Literature Library,

218
00:08:06,910 --> 00:08:09,229
to go search for our documentation and download

219
00:08:09,229 --> 00:08:09,729
it.

220
00:08:10,189 --> 00:08:11,870
I'm not sure how many of our audience

221
00:08:11,870 --> 00:08:13,789
members are aware, but if you go to

222
00:08:13,789 --> 00:08:15,490
our ROQ Automation website,

223
00:08:16,014 --> 00:08:18,675
we have this thing called the technical documentation

224
00:08:18,975 --> 00:08:19,475
center.

225
00:08:20,175 --> 00:08:22,194
You can go to specific products.

226
00:08:22,495 --> 00:08:24,654
And actually, if you go to products, all

227
00:08:24,654 --> 00:08:27,235
our documentation would be grouped together there.

228
00:08:28,569 --> 00:08:30,009
So one of the nice things we did

229
00:08:30,009 --> 00:08:32,250
for version 16, well, I hope it's nice

230
00:08:32,250 --> 00:08:34,970
for the audience members, is we've actually now

231
00:08:34,970 --> 00:08:37,769
included our online help that you get when

232
00:08:37,769 --> 00:08:39,929
you install the product as part of this

233
00:08:39,929 --> 00:08:41,230
web page experience.

234
00:08:42,075 --> 00:08:42,575
So,

235
00:08:43,595 --> 00:08:44,575
what's the advantages

236
00:08:45,115 --> 00:08:47,195
of of having these online pages? You don't

237
00:08:47,195 --> 00:08:49,035
have to go create, let's say, a virtual

238
00:08:49,035 --> 00:08:52,235
machine or machine and go install Facadog Vue

239
00:08:52,235 --> 00:08:54,554
anymore to go get online help. You know,

240
00:08:54,554 --> 00:08:56,789
you have to go to help content and

241
00:08:56,789 --> 00:08:59,269
then online help is usually there. And the

242
00:08:59,269 --> 00:09:02,149
second advantage here is if we have to

243
00:09:02,149 --> 00:09:02,629
do,

244
00:09:03,110 --> 00:09:06,009
documentation updates, so online help documentation updates,

245
00:09:06,710 --> 00:09:08,629
we can actually publish it the next day.

246
00:09:08,629 --> 00:09:09,910
So you don't have to wait for the

247
00:09:09,910 --> 00:09:12,774
next release to see those updated, documents.

248
00:09:13,154 --> 00:09:15,154
It's just live the next day when we

249
00:09:15,154 --> 00:09:15,894
do that.

250
00:09:16,274 --> 00:09:16,774
So

251
00:09:17,154 --> 00:09:19,154
I can just quickly show you what this

252
00:09:19,154 --> 00:09:21,554
looks like. So here, I've actually I'm actually

253
00:09:21,554 --> 00:09:23,634
on our Rock Automation website. I went to

254
00:09:23,634 --> 00:09:26,375
our human machine interface software technical documentation.

255
00:09:27,210 --> 00:09:28,970
What you'll notice is here is all our

256
00:09:28,970 --> 00:09:30,509
documentation grouped together.

257
00:09:31,210 --> 00:09:32,889
Even I have to go search for them

258
00:09:32,889 --> 00:09:34,990
individually on the literature library.

259
00:09:36,009 --> 00:09:37,529
What we've added here, like I say, is

260
00:09:37,529 --> 00:09:38,509
the online help.

261
00:09:39,050 --> 00:09:40,649
So let's say, for example, we've got the

262
00:09:40,649 --> 00:09:43,024
fact that you online help here. I'm just

263
00:09:43,024 --> 00:09:44,804
gonna open this as a new page.

264
00:09:45,585 --> 00:09:46,085
Yeah.

265
00:09:46,705 --> 00:09:48,945
Now this is online. I can go something

266
00:09:48,945 --> 00:09:49,764
like trends,

267
00:09:50,465 --> 00:09:52,945
and maybe I can do something like the

268
00:09:52,945 --> 00:09:53,845
trained interface.

269
00:09:54,779 --> 00:09:57,019
So here's the online help where in the

270
00:09:57,019 --> 00:09:59,279
past, you had to go to the physically

271
00:09:59,419 --> 00:10:00,480
into studio,

272
00:10:00,940 --> 00:10:02,399
go to help, content,

273
00:10:02,860 --> 00:10:05,179
fact of view, and you would have gotten

274
00:10:05,179 --> 00:10:08,000
the same thing, by clicking on the trends

275
00:10:08,139 --> 00:10:09,360
and interface.

276
00:10:10,394 --> 00:10:12,654
Moving on to my next topic,

277
00:10:13,034 --> 00:10:16,955
performance enhancements. So as everybody know with with

278
00:10:16,955 --> 00:10:18,174
any software package,

279
00:10:18,794 --> 00:10:20,955
every time we do a new release, there's

280
00:10:20,955 --> 00:10:24,095
more content. So either the installation media grows,

281
00:10:25,120 --> 00:10:27,059
doing the installation takes longer,

282
00:10:28,480 --> 00:10:30,879
opening up your projects becomes longer and your

283
00:10:30,879 --> 00:10:33,120
runtime clients are doing the same thing. So

284
00:10:33,120 --> 00:10:35,860
we really try to focus on version 15

285
00:10:36,480 --> 00:10:38,684
to enhance this experience and make sure that

286
00:10:38,684 --> 00:10:40,304
we, get some performance,

287
00:10:40,764 --> 00:10:41,584
out of it.

288
00:10:41,964 --> 00:10:44,065
So what will you see when you install

289
00:10:44,125 --> 00:10:46,065
FactoryTalk for you a version 15?

290
00:10:46,924 --> 00:10:49,424
When you do the installs, it's actually significantly

291
00:10:49,804 --> 00:10:51,884
faster now to do the install on your

292
00:10:51,884 --> 00:10:52,384
machine.

293
00:10:53,039 --> 00:10:53,779
Number two,

294
00:10:54,240 --> 00:10:57,840
specifically, well, not specifically, but typically for larger

295
00:10:57,840 --> 00:10:58,340
applications,

296
00:10:58,799 --> 00:11:00,580
if you now open up Vue Studio,

297
00:11:01,120 --> 00:11:03,779
you should see a 30% to 40%

298
00:11:03,840 --> 00:11:06,580
increase in speed of opening up that application

299
00:11:06,799 --> 00:11:07,539
as well,

300
00:11:08,495 --> 00:11:09,554
which is significant.

301
00:11:10,495 --> 00:11:12,914
As well if you open up your runtime

302
00:11:12,975 --> 00:11:13,475
client,

303
00:11:14,894 --> 00:11:18,835
especially again with large applications and multiple HMI

304
00:11:18,894 --> 00:11:22,115
applications in that, HMI service in that application,

305
00:11:23,019 --> 00:11:25,339
you'll see a 30 to 40% boost there

306
00:11:25,339 --> 00:11:27,919
as well, opening up that runtime client.

307
00:11:28,620 --> 00:11:30,460
And then lastly is probably going to be

308
00:11:30,460 --> 00:11:32,379
a once off for the audience members. But

309
00:11:32,379 --> 00:11:35,440
if you are doing migrations, let's say from

310
00:11:35,565 --> 00:11:38,845
a v 10 application to a v 15

311
00:11:38,845 --> 00:11:39,345
application,

312
00:11:39,965 --> 00:11:41,904
you should see an increase of

313
00:11:42,284 --> 00:11:45,644
on about 50% faster doing that migration over

314
00:11:45,644 --> 00:11:47,825
to, let's say, v 15.

315
00:11:48,990 --> 00:11:51,309
One of the things which was really great

316
00:11:51,309 --> 00:11:53,230
to hear when I was at automation fair,

317
00:11:53,230 --> 00:11:55,070
we actually had a couple of customers come

318
00:11:55,070 --> 00:11:57,629
up to us and say they really appreciate

319
00:11:57,629 --> 00:12:00,450
this. They could could see the performance increase.

320
00:12:02,054 --> 00:12:05,355
So, my recommendation to anybody that's still struggling,

321
00:12:05,495 --> 00:12:07,174
do I go to version 14? Do I

322
00:12:07,174 --> 00:12:08,394
go to version 15?

323
00:12:09,174 --> 00:12:11,434
This is one of those easy decision makers.

324
00:12:11,735 --> 00:12:14,235
The just be because of the performance enhancement,

325
00:12:15,149 --> 00:12:16,289
go to v 15,

326
00:12:16,750 --> 00:12:18,829
because you'll have a better experience at the

327
00:12:18,829 --> 00:12:19,730
end of the day.

328
00:12:21,070 --> 00:12:21,570
Alright.

329
00:12:22,190 --> 00:12:24,450
Let's go on to the next topic. So,

330
00:12:25,629 --> 00:12:27,535
some of our audience members might not be

331
00:12:27,535 --> 00:12:29,695
familiar with what we did in version 14,

332
00:12:29,695 --> 00:12:31,615
so I'm just gonna talk through that. In

333
00:12:31,615 --> 00:12:33,075
version 14, we introduced

334
00:12:33,535 --> 00:12:36,815
a new data log, logging system, which we

335
00:12:36,815 --> 00:12:39,715
basically call data log, pro with InfluxDB.

336
00:12:40,690 --> 00:12:43,430
It's basically logging to a time series database,

337
00:12:43,970 --> 00:12:45,029
far from InfluxDB.

338
00:12:45,570 --> 00:12:47,190
In version 14, we were

339
00:12:47,570 --> 00:12:49,970
telling you you could only, lock the data

340
00:12:49,970 --> 00:12:52,230
onto your local local HMI server,

341
00:12:52,945 --> 00:12:54,804
which also supported redundancy.

342
00:12:55,345 --> 00:12:57,184
So if you had a redundant system, you

343
00:12:57,184 --> 00:12:59,664
just had to install that same database on

344
00:12:59,664 --> 00:13:01,524
your secondary HMI server

345
00:13:01,985 --> 00:13:04,004
and you got that redundancy support.

346
00:13:04,625 --> 00:13:07,024
Now, obviously, we're trying to keep off with

347
00:13:07,024 --> 00:13:08,004
user requirements

348
00:13:08,379 --> 00:13:09,899
and we're trying to keep up with the

349
00:13:09,899 --> 00:13:12,639
technologies that InfluxDB is putting out there.

350
00:13:13,019 --> 00:13:14,699
So this was an easy one for us

351
00:13:14,699 --> 00:13:17,179
because being able to connect to an external

352
00:13:17,179 --> 00:13:17,679
InfluxDB

353
00:13:18,459 --> 00:13:21,439
and connect to something like InfluxDB cloud serverless,

354
00:13:21,899 --> 00:13:22,559
the workflows

355
00:13:23,100 --> 00:13:25,445
were very similar. So now we have that

356
00:13:25,524 --> 00:13:26,345
those capabilities.

357
00:13:27,365 --> 00:13:29,225
The one thing I just want to mention

358
00:13:29,684 --> 00:13:31,764
that everybody asks all the time, well, what

359
00:13:31,764 --> 00:13:34,485
if I lose my connection to my external

360
00:13:34,485 --> 00:13:34,985
InfluxDB?

361
00:13:36,084 --> 00:13:37,945
The nice thing is we just automatically

362
00:13:38,960 --> 00:13:41,200
start logging to our local DB once we,

363
00:13:41,600 --> 00:13:44,800
that connection is lost. And once that connection

364
00:13:44,800 --> 00:13:45,460
is reestablished,

365
00:13:46,160 --> 00:13:48,399
it will actually just backfill the data to

366
00:13:48,399 --> 00:13:49,860
the external influx DB,

367
00:13:50,240 --> 00:13:51,620
so you will have no,

368
00:13:52,080 --> 00:13:52,580
losses.

369
00:13:53,235 --> 00:13:54,914
The one thing that you will notice if

370
00:13:54,914 --> 00:13:57,815
you now open up that Datalog Pro configuration

371
00:13:57,955 --> 00:14:00,134
menu from version 14 to 15

372
00:14:00,514 --> 00:14:02,754
is now you have the capability of either

373
00:14:02,754 --> 00:14:05,075
selecting your local database which is your on

374
00:14:05,075 --> 00:14:08,230
your HMI server or connecting to that remote

375
00:14:08,230 --> 00:14:08,730
database

376
00:14:09,110 --> 00:14:10,170
out out there.

377
00:14:11,190 --> 00:14:12,790
In the past, if we go way into

378
00:14:12,790 --> 00:14:14,629
the past, right, we were typically if we

379
00:14:14,629 --> 00:14:16,710
just wanted to create some, you know, quick

380
00:14:16,710 --> 00:14:18,790
historical trends, we'd use the data log with

381
00:14:18,790 --> 00:14:20,814
the built in file sets. And then, you

382
00:14:20,814 --> 00:14:23,174
know, if we're doing something more that we

383
00:14:23,174 --> 00:14:25,014
really needed data in a database, we're using

384
00:14:25,014 --> 00:14:25,514
ODBC.

385
00:14:26,054 --> 00:14:27,414
A lot of times, we'd go to SQL

386
00:14:27,414 --> 00:14:29,975
Server Express because it's it's you know, there's

387
00:14:29,975 --> 00:14:32,054
already instances installed, so you can install another

388
00:14:32,054 --> 00:14:33,419
instance on the same box.

389
00:14:33,740 --> 00:14:35,259
But it sounds like what you're saying is

390
00:14:35,259 --> 00:14:37,259
there's been a lot of demand for influx

391
00:14:37,259 --> 00:14:39,740
in the in the from your customers. So

392
00:14:39,740 --> 00:14:41,440
in '14, you added that support.

393
00:14:42,299 --> 00:14:43,120
And now,

394
00:14:43,740 --> 00:14:45,579
and what that gave you was the ability

395
00:14:45,579 --> 00:14:46,159
to also,

396
00:14:46,654 --> 00:14:49,315
not only do a local influx DB,

397
00:14:49,615 --> 00:14:51,934
but also a remote connection. And that brings

398
00:14:51,934 --> 00:14:53,774
us to this slide where you're talking about

399
00:14:53,774 --> 00:14:56,095
the new Datalog Pro features. So let me

400
00:14:56,095 --> 00:14:57,715
just pitch it right back to you, Johan.

401
00:14:58,415 --> 00:15:00,035
Yeah. That's exactly correct.

402
00:15:00,415 --> 00:15:00,915
So,

403
00:15:01,720 --> 00:15:03,879
the feature was was driven into the product

404
00:15:03,879 --> 00:15:06,700
because of customer requests and the popular, popularity

405
00:15:06,840 --> 00:15:09,799
of Airflowx DB. Again, coming from version 14

406
00:15:09,799 --> 00:15:12,040
to 15, we had a lot of interest

407
00:15:12,040 --> 00:15:14,040
in, in this feature. So there was some

408
00:15:14,040 --> 00:15:16,764
additional ask or enhancements requests. So this is

409
00:15:16,764 --> 00:15:18,304
what this slide is all about.

410
00:15:18,924 --> 00:15:21,964
One of those enhancements were, hey, how do

411
00:15:21,964 --> 00:15:24,464
I know if my connection to my InfluxDB

412
00:15:25,004 --> 00:15:28,365
is still healthy? Right? So what you've now

413
00:15:28,365 --> 00:15:30,705
introduced is if you go to your functions

414
00:15:31,110 --> 00:15:33,269
and go to developer pro, there's a new,

415
00:15:33,669 --> 00:15:35,929
function called DB connection state,

416
00:15:36,309 --> 00:15:38,549
which basically gives you four states. So what

417
00:15:38,549 --> 00:15:40,070
you can either do here is you can

418
00:15:40,070 --> 00:15:42,250
either go and animate something on your HMI

419
00:15:42,389 --> 00:15:43,990
with a state to say, well, you've lost

420
00:15:43,990 --> 00:15:44,649
your connection.

421
00:15:45,164 --> 00:15:47,485
Or you can actually create an alarm, which

422
00:15:47,485 --> 00:15:48,845
will come up in alarm banner and say,

423
00:15:48,845 --> 00:15:50,865
well, you've lost your connection. Please go investigate,

424
00:15:51,884 --> 00:15:52,784
why that connectivity,

425
00:15:53,964 --> 00:15:54,945
has been lost.

426
00:15:55,325 --> 00:15:55,825
So,

427
00:15:56,445 --> 00:15:57,504
that was a pretty

428
00:15:58,205 --> 00:16:00,840
good feature to add. The same thing here

429
00:16:00,840 --> 00:16:03,000
was if you are familiar with data lock

430
00:16:03,000 --> 00:16:05,120
models, if you go click on the right

431
00:16:05,320 --> 00:16:07,720
right click on the data model, you had

432
00:16:07,720 --> 00:16:09,799
a context menu where you could stop and

433
00:16:09,799 --> 00:16:11,980
start that data that data lock.

434
00:16:12,754 --> 00:16:14,914
Now we didn't have that in version 14

435
00:16:14,914 --> 00:16:16,595
on our data lock pro, so that was

436
00:16:16,595 --> 00:16:17,654
like a small enhancement.

437
00:16:18,595 --> 00:16:20,355
Instead of going to the command line and

438
00:16:20,355 --> 00:16:22,754
starting and stopping the data locks, can you

439
00:16:22,754 --> 00:16:25,495
have that same context menu on there?

440
00:16:26,029 --> 00:16:28,910
And because we've had such a big interest

441
00:16:28,910 --> 00:16:29,389
in,

442
00:16:29,790 --> 00:16:32,509
this new Datalog Pro feature, people were asking,

443
00:16:32,509 --> 00:16:35,870
well, how can I migrate my current Datalog

444
00:16:35,870 --> 00:16:36,910
models to,

445
00:16:37,230 --> 00:16:37,730
InfluxDB

446
00:16:38,350 --> 00:16:38,670
Yeah?

447
00:16:39,365 --> 00:16:41,605
Or Datalog Pro. So we try to make

448
00:16:41,605 --> 00:16:43,605
that easier. So we do now have a

449
00:16:43,605 --> 00:16:44,745
migration option.

450
00:16:45,605 --> 00:16:47,225
How this is handled essentially

451
00:16:47,605 --> 00:16:49,284
is you have to go add all the

452
00:16:49,284 --> 00:16:51,784
tags that you are using in your Datalog

453
00:16:51,845 --> 00:16:54,850
models into your Datalog Pro. Once that's done,

454
00:16:54,850 --> 00:16:56,850
you click on the migration button. You go

455
00:16:56,850 --> 00:16:57,669
to the database,

456
00:16:58,129 --> 00:16:59,429
for the data lock models.

457
00:16:59,809 --> 00:17:02,049
Click on that DB file and you just

458
00:17:02,049 --> 00:17:04,369
say migrate. And then that basically backfills all

459
00:17:04,369 --> 00:17:05,190
your data,

460
00:17:06,369 --> 00:17:08,470
to your new data lock,

461
00:17:09,245 --> 00:17:10,305
flow with InfluxDB

462
00:17:10,924 --> 00:17:11,424
and,

463
00:17:13,085 --> 00:17:16,205
you basically can just automatically switch over to

464
00:17:16,205 --> 00:17:17,345
that logging mechanism.

465
00:17:17,725 --> 00:17:19,245
So No, I think that that could take

466
00:17:19,245 --> 00:17:20,605
a long time if you had a very

467
00:17:20,605 --> 00:17:23,640
large database that you're moving, right? Correct. It

468
00:17:23,640 --> 00:17:25,080
it could take some time,

469
00:17:25,559 --> 00:17:27,500
but I think the benefits of it

470
00:17:27,920 --> 00:17:28,420
is

471
00:17:28,840 --> 00:17:30,680
still is still valuable if you want to

472
00:17:30,680 --> 00:17:31,559
go to the new,

473
00:17:31,960 --> 00:17:33,180
or to newer technologies.

474
00:17:33,799 --> 00:17:35,215
Yeah. And we won't get into this today.

475
00:17:35,215 --> 00:17:36,494
But if you guys wanna look up the

476
00:17:36,494 --> 00:17:38,575
difference between a relational database and a time

477
00:17:38,575 --> 00:17:39,475
series database,

478
00:17:40,015 --> 00:17:42,494
relational databases are not the best for the

479
00:17:42,494 --> 00:17:44,255
kind of data that we collect with with

480
00:17:44,255 --> 00:17:46,835
a SCADA system or an HMI system. So,

481
00:17:47,455 --> 00:17:49,055
I could tell stories about that, but I'll

482
00:17:49,055 --> 00:17:51,029
I'll pitch it back to you, Johan. Maybe

483
00:17:51,029 --> 00:17:53,029
maybe something to mention to the audience here

484
00:17:53,029 --> 00:17:53,610
as well.

485
00:17:54,150 --> 00:17:54,650
Licensing.

486
00:17:55,509 --> 00:17:57,269
This is all free, by the way. So

487
00:17:57,269 --> 00:17:59,029
if you're using the if you're using the

488
00:17:59,029 --> 00:18:02,250
local database, there's no additional licensing cost there.

489
00:18:02,390 --> 00:18:04,390
But if you are logging to something like

490
00:18:04,390 --> 00:18:04,970
an external

491
00:18:05,974 --> 00:18:07,035
external influx database,

492
00:18:07,734 --> 00:18:10,455
like an enterprise, influx DB, or like the

493
00:18:10,455 --> 00:18:12,775
cloud, obviously there's cost of services,

494
00:18:13,174 --> 00:18:14,234
associated with that.

495
00:18:15,174 --> 00:18:17,654
But that's something outside of you. That's how

496
00:18:17,654 --> 00:18:18,134
you,

497
00:18:18,535 --> 00:18:21,670
license those products internally in your organisation.

498
00:18:22,690 --> 00:18:25,809
But essentially using this feature is no licensing

499
00:18:25,809 --> 00:18:28,070
cost, it's free out of the box experience

500
00:18:28,369 --> 00:18:29,670
that you can just use.

501
00:18:30,049 --> 00:18:30,549
Nice.

502
00:18:31,090 --> 00:18:32,769
And the last one here that I just

503
00:18:32,769 --> 00:18:34,125
going to talk, I'm not going to talk

504
00:18:34,204 --> 00:18:36,285
a lot about this, but again, I mentioned

505
00:18:36,285 --> 00:18:36,785
earlier,

506
00:18:37,164 --> 00:18:39,724
we're trying to keep up with InfluxDB and

507
00:18:39,724 --> 00:18:40,625
all the technologies

508
00:18:41,005 --> 00:18:43,664
or services that they are providing out there.

509
00:18:43,884 --> 00:18:46,204
So last year, I believe, I think it

510
00:18:46,204 --> 00:18:48,869
was in November or December, they released InfluxDB

511
00:18:49,090 --> 00:18:50,549
three core and enterprise.

512
00:18:51,410 --> 00:18:53,650
This the workflow to connect to these are

513
00:18:53,650 --> 00:18:54,789
exactly the same.

514
00:18:55,250 --> 00:18:57,730
There's no there's no difference in the connection

515
00:18:57,730 --> 00:18:58,230
properties.

516
00:18:59,234 --> 00:19:01,434
It's just we now can log to Influx

517
00:19:01,434 --> 00:19:04,015
DB three core and enterprise with no issues.

518
00:19:04,795 --> 00:19:07,134
The one thing here just to note is,

519
00:19:08,394 --> 00:19:10,634
we recommend if you are gonna connect to

520
00:19:10,634 --> 00:19:13,214
an Influx DB three core or an Influx

521
00:19:13,799 --> 00:19:14,859
DB enterprise,

522
00:19:15,480 --> 00:19:17,980
deploy those on a Linux operating system.

523
00:19:18,440 --> 00:19:20,359
It does work on Windows, but we've seen

524
00:19:20,359 --> 00:19:22,839
some stability issues with which we are working

525
00:19:22,839 --> 00:19:25,964
with Influx DB, to help resolve those. But

526
00:19:25,964 --> 00:19:28,285
from their point and stance, they say, well,

527
00:19:28,285 --> 00:19:30,525
it's better to actually just deploy those on

528
00:19:30,525 --> 00:19:31,904
Linux operating systems.

529
00:19:32,765 --> 00:19:34,285
Hey, guys. I just wanna break in here

530
00:19:34,285 --> 00:19:35,884
quickly for a minute to thank our members

531
00:19:35,884 --> 00:19:38,460
over on YouTube and the automationblog.com

532
00:19:38,539 --> 00:19:41,839
and my VSC students over at the automationschool.com.

533
00:19:42,059 --> 00:19:44,460
You all will be receiving an extended version

534
00:19:44,460 --> 00:19:45,440
of this unsponsored

535
00:19:45,740 --> 00:19:48,779
episode in appreciation for your $5 a month

536
00:19:48,779 --> 00:19:50,399
or for rolling in my course

537
00:19:50,855 --> 00:19:51,355
because,

538
00:19:51,734 --> 00:19:53,815
this this episode was not sponsored by the

539
00:19:53,815 --> 00:19:56,535
vendors. So really appreciate you guys. Check that

540
00:19:56,535 --> 00:19:58,295
out. You should be seeing it very quickly

541
00:19:58,295 --> 00:20:00,295
if you're a member. The automation school will

542
00:20:00,295 --> 00:20:01,894
come a little bit later because I have

543
00:20:01,894 --> 00:20:03,789
some traveling to do, and and it's actually

544
00:20:03,789 --> 00:20:05,309
gonna be part of a lot of other

545
00:20:05,309 --> 00:20:06,990
things you're gonna be getting in that BSC

546
00:20:06,990 --> 00:20:09,150
course. So keep that out. Thank you both

547
00:20:09,150 --> 00:20:10,750
very much. And now let's get back into

548
00:20:10,750 --> 00:20:12,609
learning what's new with FactoryTalk

549
00:20:12,910 --> 00:20:14,930
Vue version fifteen and sixteen.

550
00:20:15,244 --> 00:20:16,845
So I got a couple questions for you.

551
00:20:16,845 --> 00:20:17,744
I mean, InfluxDB,

552
00:20:18,125 --> 00:20:20,205
I'm seeing a lot of usability features that

553
00:20:20,205 --> 00:20:22,945
I like in what you're showing versus, like,

554
00:20:23,005 --> 00:20:25,404
SQL Server Express. So I can see why

555
00:20:25,404 --> 00:20:28,045
some people, especially corporate wide, would be using

556
00:20:28,045 --> 00:20:28,545
InfluxDB,

557
00:20:29,240 --> 00:20:31,080
And and, of course, it's time series not

558
00:20:31,080 --> 00:20:31,580
relational.

559
00:20:31,960 --> 00:20:32,460
But,

560
00:20:33,240 --> 00:20:35,559
it also seems like Datalog Pro, one of

561
00:20:35,559 --> 00:20:37,500
the advantages is per tag

562
00:20:38,119 --> 00:20:40,200
scan rates or data collection rates, I should

563
00:20:40,200 --> 00:20:42,775
say. Like, I don't remember that as being

564
00:20:42,775 --> 00:20:44,375
a feature. It was your data log model

565
00:20:44,375 --> 00:20:45,975
was set up to be either you know,

566
00:20:45,975 --> 00:20:47,335
it was the whole model. You you had

567
00:20:47,335 --> 00:20:48,855
to get all the data at a particular

568
00:20:48,855 --> 00:20:50,775
rate. Am I correct about that, or is

569
00:20:50,855 --> 00:20:53,095
am I missing something? You are very correct

570
00:20:53,095 --> 00:20:54,775
in that stating that. That seems like a

571
00:20:54,775 --> 00:20:55,595
huge advantage.

572
00:20:56,140 --> 00:20:57,359
That is a huge advantage.

573
00:20:58,059 --> 00:20:58,559
Obviously,

574
00:20:59,500 --> 00:21:01,839
we are currently saying, if I remember correctly,

575
00:21:02,059 --> 00:21:05,119
you can log 50,000 tags per scan,

576
00:21:05,900 --> 00:21:07,200
on your deadlock models,

577
00:21:07,660 --> 00:21:09,920
but that's either one scan interval.

578
00:21:10,315 --> 00:21:12,555
Obviously, if you the more tags you have

579
00:21:12,555 --> 00:21:14,255
with a smaller interval,

580
00:21:14,875 --> 00:21:16,095
the smaller that,

581
00:21:16,715 --> 00:21:18,955
the on scan tags, will become at the

582
00:21:18,955 --> 00:21:21,434
end of the day. But 50,000 tags on

583
00:21:21,434 --> 00:21:23,755
scan, is quite a lot for for a

584
00:21:23,755 --> 00:21:26,039
lot of users out there. Well, that brings

585
00:21:26,039 --> 00:21:27,559
up another point. I know with the data

586
00:21:27,559 --> 00:21:29,319
log models for years and years, it's always

587
00:21:29,319 --> 00:21:31,319
been, you can have up to 20 data

588
00:21:31,319 --> 00:21:32,059
log models,

589
00:21:32,440 --> 00:21:34,279
you know, in under your in your data

590
00:21:34,279 --> 00:21:36,279
logs, and you can run well, on the

591
00:21:36,279 --> 00:21:38,119
p w plus was always something different. Machine

592
00:21:38,119 --> 00:21:39,579
edition was different. In SC,

593
00:21:39,904 --> 00:21:41,184
you could run them all or just run

594
00:21:41,184 --> 00:21:42,384
some of them. You could I guess you

595
00:21:42,384 --> 00:21:44,384
could have 20 running at a time. But

596
00:21:44,384 --> 00:21:46,464
with Datalog Pro, it looks like you have

597
00:21:46,464 --> 00:21:49,264
one configuration to one Influx database. Is that

598
00:21:49,264 --> 00:21:49,764
correct?

599
00:21:50,065 --> 00:21:50,565
Correct.

600
00:21:51,105 --> 00:21:53,585
Okay. Great. So that that's a differentiator as

601
00:21:53,585 --> 00:21:54,085
well,

602
00:21:54,710 --> 00:21:56,390
and something that the audience needs to know

603
00:21:56,390 --> 00:21:56,890
about.

604
00:21:57,430 --> 00:21:59,589
Yeah. Well, thanks for bringing that up. Yeah.

605
00:21:59,589 --> 00:22:02,089
Thank you. No. Appreciate it. Alright.

606
00:22:03,589 --> 00:22:05,509
I'm gonna switch gears and go to the

607
00:22:05,509 --> 00:22:06,250
next topic.

608
00:22:08,095 --> 00:22:10,815
So I don't know our audience members how

609
00:22:10,815 --> 00:22:12,515
far they are down with the MQTT,

610
00:22:13,375 --> 00:22:15,715
journey. I know a lot of people request

611
00:22:16,095 --> 00:22:18,495
the functionality for MQTT, but once you actually

612
00:22:18,495 --> 00:22:19,775
talk to them and say, well, are you

613
00:22:19,775 --> 00:22:20,995
actually doing the implementation?

614
00:22:22,670 --> 00:22:25,390
My experience is no, they haven't really touched

615
00:22:25,390 --> 00:22:27,950
it or they're not really have implemented on-site.

616
00:22:27,950 --> 00:22:29,970
It's only on their testbeds at the moment.

617
00:22:31,069 --> 00:22:32,750
But what we try to do here in

618
00:22:32,750 --> 00:22:35,585
version 15 is make MQTT support a little

619
00:22:35,585 --> 00:22:36,404
bit easier,

620
00:22:36,865 --> 00:22:40,224
for our, user base out there. Now you

621
00:22:40,224 --> 00:22:41,204
can do MQTT

622
00:22:41,744 --> 00:22:43,924
today in, let's say, version 14.

623
00:22:44,544 --> 00:22:46,704
The catch there just is is everything is

624
00:22:46,704 --> 00:22:48,250
done in VBA. You have to go create

625
00:22:48,250 --> 00:22:50,669
your own VBA code to make this support.

626
00:22:51,210 --> 00:22:52,509
Now in vision 15,

627
00:22:52,890 --> 00:22:55,450
it's still VBA in the background. What we

628
00:22:55,450 --> 00:22:57,849
try to simplify this for you, we try

629
00:22:57,849 --> 00:23:00,429
to, to reduce the amount of VBA code

630
00:23:00,634 --> 00:23:02,255
that you have to use and,

631
00:23:02,795 --> 00:23:05,035
give you examples of exactly how to do

632
00:23:05,035 --> 00:23:07,615
this. So in version 15, we actually,

633
00:23:09,434 --> 00:23:11,134
support MQTT clients,

634
00:23:11,674 --> 00:23:12,174
for

635
00:23:12,875 --> 00:23:15,595
supporting publisher and subscribers. We do not support

636
00:23:15,595 --> 00:23:16,095
brokers.

637
00:23:16,880 --> 00:23:20,019
And we're basically giving you integrated VBA libraries.

638
00:23:21,599 --> 00:23:24,399
The nice thing about these libraries is it

639
00:23:24,399 --> 00:23:27,679
does support TCP and WebSocket with optional TLS

640
00:23:27,679 --> 00:23:29,539
for reliable secure messaging

641
00:23:30,045 --> 00:23:32,605
and also works with MQTT version five dot

642
00:23:32,605 --> 00:23:35,164
o and three dot one for, a broad

643
00:23:35,164 --> 00:23:35,664
system,

644
00:23:37,164 --> 00:23:38,545
for broad system user

645
00:23:38,845 --> 00:23:39,345
capability.

646
00:23:39,965 --> 00:23:42,625
Alright. Gonna move on to the next one.

647
00:23:43,640 --> 00:23:46,059
Facatalk alarms and events email notifications.

648
00:23:46,920 --> 00:23:49,660
Now I actually always started with this.

649
00:23:50,680 --> 00:23:53,160
So this is really not intended to go

650
00:23:53,160 --> 00:23:55,660
and replace your third party solutions,

651
00:23:56,275 --> 00:23:59,015
which already does your email notification systems.

652
00:24:00,115 --> 00:24:03,095
This is really for those users out there

653
00:24:03,795 --> 00:24:05,474
that don't want to spend the money on

654
00:24:05,474 --> 00:24:06,375
an email notification

655
00:24:06,674 --> 00:24:09,255
system. They just want something that's very basic.

656
00:24:09,890 --> 00:24:12,230
An alarm comes in and they get notified

657
00:24:12,289 --> 00:24:12,789
over

658
00:24:13,169 --> 00:24:14,069
email. So,

659
00:24:15,169 --> 00:24:17,750
again, this is not intended to replace that,

660
00:24:17,809 --> 00:24:20,529
but just support on those customers that don't

661
00:24:20,690 --> 00:24:22,149
either don't have the funds,

662
00:24:22,884 --> 00:24:25,365
or don't want to spend the money on,

663
00:24:25,605 --> 00:24:27,845
something like this. So this is gonna be

664
00:24:27,845 --> 00:24:30,184
a very, very limited functionality.

665
00:24:31,365 --> 00:24:33,525
Obviously, we we get requests all the time

666
00:24:33,525 --> 00:24:35,444
to do enhancements, so we take those into

667
00:24:35,444 --> 00:24:35,944
consideration

668
00:24:36,244 --> 00:24:38,309
and we'll see how we can do this

669
00:24:38,309 --> 00:24:39,509
in the future. The one thing I do

670
00:24:39,509 --> 00:24:41,669
want to mention, this is not dependent on

671
00:24:41,669 --> 00:24:44,230
FactoryTalk View, it's actually dependent on FactoryTalk Service

672
00:24:44,230 --> 00:24:44,730
platform.

673
00:24:45,029 --> 00:24:47,429
So if you're running version 13 today and

674
00:24:47,429 --> 00:24:49,829
you update your FactoryTalk Service platform to six

675
00:24:49,829 --> 00:24:51,529
fifty, you will get this functionality.

676
00:24:51,990 --> 00:24:53,504
Hey, guys. Just breaking in here quickly to

677
00:24:53,504 --> 00:24:54,784
pay some bills, and I wanna tell you

678
00:24:54,784 --> 00:24:56,464
about some of the unique features of this

679
00:24:56,464 --> 00:24:59,264
course I'm holding right here, April 21 through

680
00:24:59,264 --> 00:25:00,244
the twenty fourth.

681
00:25:00,704 --> 00:25:02,304
When you sign up, you're gonna be picking

682
00:25:02,304 --> 00:25:05,345
what hardware you wanna work on, CompactLogic's micro

683
00:25:05,345 --> 00:25:08,049
800 or s seven twelve hundred. But then

684
00:25:08,049 --> 00:25:09,730
when you're here, you're gonna be able to

685
00:25:09,730 --> 00:25:12,849
choose from four different labs. Okay? So we

686
00:25:12,849 --> 00:25:14,150
have PLC basics.

687
00:25:14,450 --> 00:25:15,990
We have beyond basics.

688
00:25:16,289 --> 00:25:19,170
We have mastering applications with factory IO. That's

689
00:25:19,170 --> 00:25:20,849
right. I have factory IO installed on all

690
00:25:20,849 --> 00:25:22,394
the computers in there. So you'll be able

691
00:25:22,394 --> 00:25:24,955
to do that and actually solve some pretty

692
00:25:24,955 --> 00:25:26,095
complicated applications.

693
00:25:26,715 --> 00:25:29,355
And then the fourth option is distributed IO.

694
00:25:29,355 --> 00:25:31,615
I got nine distributed IO options here.

695
00:25:31,914 --> 00:25:33,615
I have more in the other room.

696
00:25:34,250 --> 00:25:36,250
Some are Siemens only, some are Rockwell only,

697
00:25:36,250 --> 00:25:38,170
some will work with both. But in any

698
00:25:38,170 --> 00:25:39,850
case, you'll be able to sit here in

699
00:25:39,850 --> 00:25:42,009
a nice safe environment and try plugging in

700
00:25:42,009 --> 00:25:44,490
and connecting all kinds of different distributed IO

701
00:25:44,490 --> 00:25:46,570
to your PLC. Of course, you're gonna have

702
00:25:46,570 --> 00:25:48,410
to put your lab number down on top

703
00:25:48,410 --> 00:25:50,264
of the device that you're using so somebody

704
00:25:50,264 --> 00:25:51,704
else isn't trying to connect to it at

705
00:25:51,704 --> 00:25:54,284
the same time. But with over a dozen

706
00:25:54,585 --> 00:25:56,764
different distributed IO options,

707
00:25:57,384 --> 00:25:58,904
hopefully, not too many people will be trying

708
00:25:58,904 --> 00:26:00,264
to use the same exact one at the

709
00:26:00,264 --> 00:26:01,880
same time. In any case,

710
00:26:02,180 --> 00:26:04,339
so that's gonna be something unique. So that,

711
00:26:04,339 --> 00:26:06,279
in addition to be able to solve applications

712
00:26:06,339 --> 00:26:07,940
with FactorIO, you don't have to go out

713
00:26:07,940 --> 00:26:09,859
and spend a few $100 to buy a

714
00:26:09,859 --> 00:26:11,700
license. You can actually just do it here

715
00:26:11,700 --> 00:26:14,440
for the day, and it's all self paced.

716
00:26:14,775 --> 00:26:17,174
So you can go from the basics, beyond

717
00:26:17,174 --> 00:26:20,134
basics, factory IO, distributed IO, and whatever are

718
00:26:20,134 --> 00:26:22,615
you want. You're just reserving which hardware you're

719
00:26:22,615 --> 00:26:25,115
gonna use that day when you sign up

720
00:26:25,255 --> 00:26:27,575
for that course on April 21 through the

721
00:26:27,575 --> 00:26:29,640
twenty fourth. Again, you could choose one day,

722
00:26:29,640 --> 00:26:31,640
two day, three days, or four days, but

723
00:26:31,640 --> 00:26:33,559
the seats are limited. So if you wanna

724
00:26:33,559 --> 00:26:35,660
come, again, we're one hour east of Albany.

725
00:26:36,119 --> 00:26:38,360
If you wanna come, please sign up right

726
00:26:38,360 --> 00:26:40,519
away over at the automation school dot com

727
00:26:40,519 --> 00:26:43,065
forward / live. And with that, let's get

728
00:26:43,065 --> 00:26:45,625
back to learning what's new in FactoryTalk Vue

729
00:26:45,625 --> 00:26:48,045
SE version fifteen and sixteen.

730
00:26:48,585 --> 00:26:50,505
Alright. I'm gonna move on to the next

731
00:26:50,505 --> 00:26:51,005
one.

732
00:26:51,625 --> 00:26:53,944
This is actually been probably one of the

733
00:26:53,944 --> 00:26:56,339
most popular features that we've had since the

734
00:26:56,339 --> 00:26:58,200
introduction of version 14.

735
00:26:58,740 --> 00:27:00,740
So for our audience members out there that

736
00:27:00,740 --> 00:27:03,720
don't know, about this feature, we introduced,

737
00:27:04,419 --> 00:27:07,299
this capability called the runtime navigation meeting. Now,

738
00:27:07,299 --> 00:27:08,039
you know,

739
00:27:08,865 --> 00:27:10,464
today if you want to go build out

740
00:27:10,464 --> 00:27:10,964
navigations

741
00:27:11,265 --> 00:27:12,244
on your application,

742
00:27:12,625 --> 00:27:14,545
it's a very tedious task, right? You have

743
00:27:14,545 --> 00:27:16,224
to go create buttons, you have to go

744
00:27:16,224 --> 00:27:18,224
put the commands in. If you want to

745
00:27:18,224 --> 00:27:20,625
do some bread crumbing on there, there's some

746
00:27:20,625 --> 00:27:22,464
additional animation that you have to put on

747
00:27:22,464 --> 00:27:24,779
there. So it's a very tedious process to

748
00:27:24,779 --> 00:27:26,859
build that out. So what we did in

749
00:27:26,859 --> 00:27:28,960
version 14 is giving you the capability

750
00:27:29,500 --> 00:27:30,319
of structuring

751
00:27:30,859 --> 00:27:32,480
your displays in a hierarchy.

752
00:27:32,940 --> 00:27:34,640
Once you open this runtime navigation,

753
00:27:35,419 --> 00:27:38,000
configuration, you just drag and drop that hierarchy,

754
00:27:38,815 --> 00:27:41,215
click the save button, and your navigation is

755
00:27:41,215 --> 00:27:42,434
built out for you automatically.

756
00:27:43,455 --> 00:27:45,795
It's really simple and really easy.

757
00:27:46,575 --> 00:27:47,875
You also have the capability

758
00:27:48,494 --> 00:27:49,795
of doing bread crumbing

759
00:27:50,095 --> 00:27:52,015
by selecting your scope of your alarms and

760
00:27:52,015 --> 00:27:52,755
your events,

761
00:27:53,109 --> 00:27:54,970
as well as a search capability.

762
00:27:55,349 --> 00:27:57,829
So I have the capability of click on

763
00:27:57,829 --> 00:27:58,889
the search icon,

764
00:27:59,509 --> 00:28:00,649
type an attack.

765
00:28:01,269 --> 00:28:02,869
If you double click on attack, it will

766
00:28:02,869 --> 00:28:04,950
actually navigate to that display where that tag

767
00:28:04,950 --> 00:28:07,029
is being used and it will highlight that

768
00:28:07,029 --> 00:28:07,690
for you.

769
00:28:08,265 --> 00:28:09,785
So that was just a recap for those

770
00:28:09,785 --> 00:28:11,644
that do not know what the runtime navigation

771
00:28:11,785 --> 00:28:13,644
is. In version 15,

772
00:28:14,904 --> 00:28:17,384
there was a requirement from customers. We only

773
00:28:17,384 --> 00:28:20,205
limited to build out one of those navigation

774
00:28:20,265 --> 00:28:20,765
menus.

775
00:28:21,150 --> 00:28:23,869
Now you have the capability of, building up

776
00:28:23,869 --> 00:28:26,029
multiple navigation menus. You can have as many

777
00:28:26,029 --> 00:28:26,769
as you want.

778
00:28:27,070 --> 00:28:29,390
And the use case here is really, well,

779
00:28:29,390 --> 00:28:31,710
I've got client one and client two. I

780
00:28:31,710 --> 00:28:34,190
want the navigation menus to look different for

781
00:28:34,190 --> 00:28:35,570
the two different operators.

782
00:28:36,269 --> 00:28:38,644
So that's the reason why one of the

783
00:28:38,644 --> 00:28:41,384
reasons why they want multiple navigation menus.

784
00:28:42,565 --> 00:28:44,724
It seems like you're showing another example where

785
00:28:44,724 --> 00:28:46,025
they have four monitors.

786
00:28:46,404 --> 00:28:48,644
Right? And they wanted a different menu for

787
00:28:48,644 --> 00:28:50,244
each monitor, which I think is cool as

788
00:28:50,244 --> 00:28:50,609
well.

789
00:28:51,650 --> 00:28:53,509
Yeah. I think that is the edge cage

790
00:28:54,450 --> 00:28:56,369
cage edge edge case, by the way. I

791
00:28:56,369 --> 00:28:58,450
don't know how many people really want different

792
00:28:58,450 --> 00:29:01,170
navigation menus on the multi monitor display, but

793
00:29:01,170 --> 00:29:01,910
it is possible,

794
00:29:02,690 --> 00:29:03,970
to do that. So,

795
00:29:05,015 --> 00:29:06,615
I might be wrong as I need to

796
00:29:06,615 --> 00:29:08,634
add each case, but I think it's more

797
00:29:09,015 --> 00:29:10,795
relevant to different operating stations.

798
00:29:11,735 --> 00:29:13,355
Alright. So, again,

799
00:29:14,375 --> 00:29:15,995
like I said, it's a very popular

800
00:29:16,695 --> 00:29:17,195
feature,

801
00:29:17,670 --> 00:29:20,570
and we've had multiple requests to make enhancements.

802
00:29:21,430 --> 00:29:23,029
So a lot of our customers have come

803
00:29:23,029 --> 00:29:24,710
to us and say, well, we don't like

804
00:29:24,710 --> 00:29:27,529
docking our navigation menu at the top or

805
00:29:27,590 --> 00:29:28,410
at the bottom.

806
00:29:28,789 --> 00:29:31,765
They want to save that vertical space. So

807
00:29:31,765 --> 00:29:32,964
they want to be able to dock it

808
00:29:32,964 --> 00:29:34,744
to the left and to the right.

809
00:29:35,204 --> 00:29:38,404
So in version 16, we introduced support for

810
00:29:38,404 --> 00:29:40,644
that, that you can do that. It's very

811
00:29:40,644 --> 00:29:41,144
configurable.

812
00:29:42,164 --> 00:29:43,605
I know you might not be able to

813
00:29:43,605 --> 00:29:45,684
see the slide here, but you have the

814
00:29:45,684 --> 00:29:46,184
ability

815
00:29:46,960 --> 00:29:49,120
to specify you only want to show the

816
00:29:49,120 --> 00:29:49,620
icon

817
00:29:50,000 --> 00:29:52,240
of the navigation menu or you can want

818
00:29:52,240 --> 00:29:54,340
to show the icon and the text.

819
00:29:55,440 --> 00:29:58,080
So it's very configurable at that point in

820
00:29:58,080 --> 00:29:58,580
time.

821
00:29:59,575 --> 00:30:01,815
Moving on to the next one. So I'm

822
00:30:01,815 --> 00:30:03,494
not sure how many of you are Plant

823
00:30:03,494 --> 00:30:05,815
PX users, but if you are a Plant

824
00:30:05,815 --> 00:30:07,735
PX user, you will know there's something called

825
00:30:07,735 --> 00:30:08,955
the graphical framework.

826
00:30:09,654 --> 00:30:11,335
And that's an easy way to build out

827
00:30:11,335 --> 00:30:12,555
a navigation menu

828
00:30:13,015 --> 00:30:14,875
using the Plant PX standards.

829
00:30:16,269 --> 00:30:18,589
Now how that navigation menu works. Instead of

830
00:30:18,589 --> 00:30:20,130
having, like, a fly out,

831
00:30:21,309 --> 00:30:24,190
a menu menu, like like, if you do

832
00:30:24,190 --> 00:30:26,130
a on your Windows start bar,

833
00:30:26,430 --> 00:30:28,674
they want the ability to stack

834
00:30:29,054 --> 00:30:31,054
the navigations on top of each other. So

835
00:30:31,054 --> 00:30:32,974
if I can try and give you a

836
00:30:32,974 --> 00:30:36,115
visual representation, you will have a navigation menu

837
00:30:36,174 --> 00:30:38,575
level one with buttons. If you click on

838
00:30:38,575 --> 00:30:40,829
one of the level one buttons, it will

839
00:30:40,829 --> 00:30:43,950
stack second row of navigation menu items on,

840
00:30:44,349 --> 00:30:46,509
at the bottom of that level one, which

841
00:30:46,509 --> 00:30:48,509
is in your level two navigation. And if

842
00:30:48,509 --> 00:30:50,130
you click on that level two navigation,

843
00:30:50,670 --> 00:30:51,970
it will stack another,

844
00:30:52,429 --> 00:30:55,230
one of these navigation bars underneath that level

845
00:30:55,230 --> 00:30:55,730
two,

846
00:30:56,325 --> 00:30:58,025
to go to your level three navigations.

847
00:30:58,724 --> 00:31:00,804
The Plant PX team really want to use

848
00:31:00,804 --> 00:31:03,044
our built in run to that navigation menu

849
00:31:03,044 --> 00:31:05,304
and get rid of the graphical framework,

850
00:31:05,924 --> 00:31:08,404
or keep it in legacy support at that

851
00:31:08,404 --> 00:31:09,304
point in time.

852
00:31:11,559 --> 00:31:12,539
So we basically,

853
00:31:13,720 --> 00:31:16,539
introduced this thing now called supported docked horizontal

854
00:31:16,679 --> 00:31:17,419
sub menus.

855
00:31:18,599 --> 00:31:19,099
Again,

856
00:31:19,559 --> 00:31:22,440
it's difficult for you just for the people

857
00:31:22,440 --> 00:31:24,460
that doesn't have visuals to see it,

858
00:31:25,974 --> 00:31:27,015
but it's the same concept.

859
00:31:28,694 --> 00:31:30,954
You have the ability to stack your navigation

860
00:31:31,015 --> 00:31:33,355
menus as many levels deep as you want.

861
00:31:33,815 --> 00:31:36,054
So this demo, we're gonna show three levels.

862
00:31:36,054 --> 00:31:37,034
But just remember,

863
00:31:37,399 --> 00:31:40,440
the more levels you have, the less vertical

864
00:31:40,440 --> 00:31:41,720
space you get at the end of the

865
00:31:41,720 --> 00:31:42,220
day

866
00:31:42,679 --> 00:31:44,700
to to work with. But again,

867
00:31:45,720 --> 00:31:47,319
if you click on the level one display,

868
00:31:47,319 --> 00:31:48,779
you'll get a drop down,

869
00:31:49,159 --> 00:31:51,720
which then basically stacks underneath that level one,

870
00:31:51,720 --> 00:31:53,804
then it's your level two. Click on level

871
00:31:53,804 --> 00:31:55,744
two, it'll stack another navigation

872
00:31:56,365 --> 00:31:58,544
below that, which will be your level three.

873
00:31:59,484 --> 00:32:02,044
Moving on to the next one here is

874
00:32:02,044 --> 00:32:03,825
just small usability enhancements.

875
00:32:04,365 --> 00:32:05,585
We've got some feedback.

876
00:32:05,970 --> 00:32:08,289
So when you do the navigation menu today,

877
00:32:08,289 --> 00:32:09,890
if you click on it and do the

878
00:32:09,890 --> 00:32:11,569
flyer, it will give you a little bit

879
00:32:11,569 --> 00:32:12,150
of highlight,

880
00:32:12,529 --> 00:32:13,750
to say you are here.

881
00:32:14,289 --> 00:32:16,049
We've got the feedback that it's not that

882
00:32:16,049 --> 00:32:17,809
visible. So what we try to do is

883
00:32:17,809 --> 00:32:20,210
just give a little bar underneath that navigation

884
00:32:20,210 --> 00:32:20,710
menu

885
00:32:21,065 --> 00:32:22,904
to show to give you that we are

886
00:32:22,904 --> 00:32:23,804
here indicator.

887
00:32:24,825 --> 00:32:26,984
Another one was people said, well, they're using

888
00:32:26,984 --> 00:32:29,384
all the space for the runtime navigation menu.

889
00:32:29,704 --> 00:32:31,545
And when that happens, you get the off

890
00:32:31,545 --> 00:32:32,365
page connector

891
00:32:32,984 --> 00:32:35,144
where you there will be a drop down

892
00:32:35,144 --> 00:32:37,119
just to navigate to something else. But let's

893
00:32:37,119 --> 00:32:39,679
say there was an alarm in that off

894
00:32:39,679 --> 00:32:40,419
page connector,

895
00:32:41,519 --> 00:32:44,240
it's not visible, right? You can't go click

896
00:32:44,240 --> 00:32:46,000
on it and navigate to where the problem

897
00:32:46,000 --> 00:32:48,099
is. So they wanted us to propagate

898
00:32:48,559 --> 00:32:51,014
those alarm indicators next to that off page

899
00:32:51,014 --> 00:32:51,514
connector.

900
00:32:51,974 --> 00:32:54,075
So that's one of the enhancements we made.

901
00:32:54,454 --> 00:32:56,474
And we spoke about the search capability,

902
00:32:57,815 --> 00:33:00,134
they wanted us to increase the width of

903
00:33:00,134 --> 00:33:02,615
that search bar as well as word wrap,

904
00:33:02,934 --> 00:33:05,419
all the content. So those are just some

905
00:33:05,419 --> 00:33:07,019
of the things we did here for the

906
00:33:07,019 --> 00:33:07,919
runtime navigation.

907
00:33:08,460 --> 00:33:10,140
Alright. Let's move on to some of the

908
00:33:10,140 --> 00:33:12,559
newer things that we did in version 16.

909
00:33:12,940 --> 00:33:15,339
So we tried to introduce some new objects

910
00:33:15,339 --> 00:33:16,240
into the platform.

911
00:33:17,179 --> 00:33:19,099
So one of them is a new toggle

912
00:33:19,099 --> 00:33:21,595
switch object. Right? So again, it's one of

913
00:33:21,595 --> 00:33:22,414
those things,

914
00:33:22,954 --> 00:33:24,875
we don't have those built in in our

915
00:33:24,875 --> 00:33:25,375
products.

916
00:33:25,835 --> 00:33:27,595
So if you want to create something like

917
00:33:27,595 --> 00:33:29,994
a toggle switch or a checkbox or a

918
00:33:29,994 --> 00:33:30,894
radio button,

919
00:33:31,355 --> 00:33:32,795
you know, you have to go build that

920
00:33:32,795 --> 00:33:35,035
out yourself. You have to go overlay multiple

921
00:33:35,035 --> 00:33:37,710
objects on top of each other and do

922
00:33:38,490 --> 00:33:40,750
animation on it to make it to work?

923
00:33:40,970 --> 00:33:42,970
Now we're basically giving you an out of

924
00:33:42,970 --> 00:33:44,029
the box experience

925
00:33:44,409 --> 00:33:46,269
which is basically on off control.

926
00:33:47,609 --> 00:33:50,105
You create that toggle switch. You have different

927
00:33:50,105 --> 00:33:52,525
shapes. You can either do a rectangle shape.

928
00:33:52,664 --> 00:33:54,184
You could do a pull form. You can

929
00:33:54,184 --> 00:33:56,664
do a checkbox or a radio button. One

930
00:33:56,664 --> 00:33:58,444
of the things about the radio button,

931
00:33:58,904 --> 00:34:02,119
it's not really a pure radio button indicator,

932
00:34:02,259 --> 00:34:05,059
but it's still on off. But you can

933
00:34:05,059 --> 00:34:07,140
go make that, like, a group control for

934
00:34:07,140 --> 00:34:07,960
radio buttons.

935
00:34:09,219 --> 00:34:10,360
Well, by go

936
00:34:11,059 --> 00:34:13,140
doing some VBA in the background, and that

937
00:34:13,140 --> 00:34:14,280
VBA is basically

938
00:34:14,579 --> 00:34:15,640
just, well, if,

939
00:34:16,715 --> 00:34:18,735
radio button one is selected, uncheck

940
00:34:19,035 --> 00:34:21,594
radio button two and three. If radio button

941
00:34:21,594 --> 00:34:23,994
two is selected, uncheck radio button one and

942
00:34:23,994 --> 00:34:26,074
three. Right? So you can make that group

943
00:34:26,074 --> 00:34:28,494
control work through some VBA in the background.

944
00:34:29,760 --> 00:34:31,119
You know, I know that a lot of

945
00:34:31,119 --> 00:34:33,039
times when we're doing selective switches, we'll use

946
00:34:33,039 --> 00:34:34,579
either a maintain button

947
00:34:34,880 --> 00:34:36,179
or we'll use a multistate,

948
00:34:37,119 --> 00:34:39,519
object. Right? But this is nice to have.

949
00:34:39,519 --> 00:34:41,440
These are very quick. You have your toggle

950
00:34:41,440 --> 00:34:43,280
left to rights, and you have your checkbox

951
00:34:43,280 --> 00:34:44,260
and radio buttons.

952
00:34:44,594 --> 00:34:46,514
And I can definitely see people liking these

953
00:34:46,514 --> 00:34:48,434
as just, hey. I don't wanna have to

954
00:34:48,434 --> 00:34:49,875
go and made a picture or find a

955
00:34:49,875 --> 00:34:51,954
picture to do the toggle. I just have

956
00:34:51,954 --> 00:34:54,835
this toggle right here. And, the examples you're

957
00:34:54,835 --> 00:34:56,275
showing are are really good as well. So

958
00:34:56,275 --> 00:34:58,054
for anybody listening and not watching,

959
00:34:58,420 --> 00:35:00,260
you just need a toggle button, left to

960
00:35:00,260 --> 00:35:00,739
right,

961
00:35:01,059 --> 00:35:02,760
checkbox, radio button.

962
00:35:03,059 --> 00:35:05,059
It's now a new new object, which is

963
00:35:05,059 --> 00:35:06,199
awesome. Yeah.

964
00:35:06,820 --> 00:35:08,980
Just to mention here as well, this object

965
00:35:08,980 --> 00:35:10,199
does support esignatures

966
00:35:10,659 --> 00:35:11,960
and also auditing.

967
00:35:12,905 --> 00:35:13,405
Nice.

968
00:35:14,585 --> 00:35:17,085
Alright. Moving on to the next one here.

969
00:35:17,625 --> 00:35:19,465
This has also been a very popular one

970
00:35:19,465 --> 00:35:20,684
at automation fair.

971
00:35:21,704 --> 00:35:24,264
So we created this new linear gauge object.

972
00:35:24,264 --> 00:35:26,425
So same concept applied. Today, if you want

973
00:35:26,425 --> 00:35:27,644
to use a linear gauge,

974
00:35:28,239 --> 00:35:29,760
I think we do have one there, but

975
00:35:29,760 --> 00:35:31,619
it's not very, very great.

976
00:35:32,559 --> 00:35:34,320
And you basically have to go build out

977
00:35:34,320 --> 00:35:36,880
your own linear gauge, group objects together, and

978
00:35:36,880 --> 00:35:38,900
do animation to get something to work.

979
00:35:39,280 --> 00:35:41,519
Now we created this linear gauge. We actually

980
00:35:41,519 --> 00:35:44,434
based this on our PlantPX library process objects,

981
00:35:44,894 --> 00:35:47,375
linear gauge that was created because we want

982
00:35:47,375 --> 00:35:48,974
them to switch out to the,

983
00:35:49,614 --> 00:35:52,494
custom build one, without a wand. So we

984
00:35:52,494 --> 00:35:54,494
tried to get as much functionality in here

985
00:35:54,494 --> 00:35:57,349
as well. Now this is a highly configurable

986
00:35:57,569 --> 00:35:57,889
option

987
00:35:58,369 --> 00:36:00,690
object, by the way. You can have as

988
00:36:00,690 --> 00:36:01,190
many,

989
00:36:02,130 --> 00:36:04,769
properties enabled or you can have a few

990
00:36:04,769 --> 00:36:06,609
properties as you want to enable. I know

991
00:36:06,609 --> 00:36:08,694
the audience here really can't see it, but

992
00:36:08,694 --> 00:36:10,554
I do have a Linear Gauge

993
00:36:11,014 --> 00:36:13,594
configured here which basically has an alarm

994
00:36:13,894 --> 00:36:14,394
indicator,

995
00:36:15,014 --> 00:36:16,694
which is an icon that will show up

996
00:36:16,694 --> 00:36:18,474
if it goes above a threshold.

997
00:36:18,934 --> 00:36:21,255
We have the value indicator, we have a

998
00:36:21,255 --> 00:36:24,130
target and expected range here as well. We've

999
00:36:24,130 --> 00:36:26,210
got underneath the object a value and a

1000
00:36:26,210 --> 00:36:26,710
unit.

1001
00:36:27,170 --> 00:36:28,389
We've got the thresholds.

1002
00:36:28,929 --> 00:36:31,329
We've got set points. And we've got something

1003
00:36:31,329 --> 00:36:33,809
that we have a concept of control limits

1004
00:36:33,809 --> 00:36:35,909
in the library of process objects.

1005
00:36:37,204 --> 00:36:39,945
This linear gauge can be in a vertical

1006
00:36:40,085 --> 00:36:42,824
orientation or a horizontal orientation.

1007
00:36:43,605 --> 00:36:45,144
And as well, like I said,

1008
00:36:45,525 --> 00:36:47,864
you can make this as basic as possible.

1009
00:36:47,925 --> 00:36:50,344
I've got another object on my slide here,

1010
00:36:50,450 --> 00:36:53,090
which basically just have the value indicator and

1011
00:36:53,090 --> 00:36:53,590
thresholds.

1012
00:36:54,210 --> 00:36:56,369
So it's very you can make the very

1013
00:36:56,369 --> 00:36:59,730
bare bare minimum or as as complex as

1014
00:36:59,730 --> 00:37:00,390
you want.

1015
00:37:01,730 --> 00:37:04,610
So moving on to an extension of this

1016
00:37:04,610 --> 00:37:05,110
feature.

1017
00:37:05,694 --> 00:37:08,414
So a lot of people want sparklines and

1018
00:37:08,414 --> 00:37:11,135
typically sparklines are used with linear gauges. So

1019
00:37:11,135 --> 00:37:12,894
we said, well, why don't we just create

1020
00:37:12,894 --> 00:37:14,755
a sparkline with the linear gauge?

1021
00:37:15,295 --> 00:37:17,234
So once you go into the properties

1022
00:37:17,699 --> 00:37:19,619
of a linear gauge, you just have a

1023
00:37:19,619 --> 00:37:21,559
checkbox that say enable the sparkline

1024
00:37:22,019 --> 00:37:24,519
and that sparkline will show up. The sparkline

1025
00:37:24,579 --> 00:37:26,039
is also very configurable.

1026
00:37:26,980 --> 00:37:30,105
You can choose to show your threshold lines.

1027
00:37:30,505 --> 00:37:32,844
You can choose your vertical and horizontal

1028
00:37:33,224 --> 00:37:35,304
grids, how many lines you want for that.

1029
00:37:35,304 --> 00:37:37,164
You can choose not to have a grid.

1030
00:37:38,505 --> 00:37:39,405
You can also

1031
00:37:39,704 --> 00:37:41,885
choose not to show the linear gauge,

1032
00:37:42,184 --> 00:37:43,885
you just want to show the sparkline.

1033
00:37:44,650 --> 00:37:45,389
So again,

1034
00:37:46,489 --> 00:37:48,329
people can't really see what's on the slide

1035
00:37:48,329 --> 00:37:50,329
here. We was listening, but I do have

1036
00:37:50,329 --> 00:37:52,909
an object here which has the full configuration

1037
00:37:53,130 --> 00:37:55,050
with the linear gauge and the sparkline with

1038
00:37:55,050 --> 00:37:57,414
the grit and the trench showing up. And

1039
00:37:57,414 --> 00:37:59,094
then at the bottom, I've got one that

1040
00:37:59,094 --> 00:38:01,414
doesn't have the linear gauge, but only shows

1041
00:38:01,414 --> 00:38:03,815
the sparkline. There's no grids. It's really just

1042
00:38:03,815 --> 00:38:05,835
the trends that you are currently seeing.

1043
00:38:06,375 --> 00:38:10,295
And we also support a vertical orientation and

1044
00:38:10,295 --> 00:38:11,194
a horizontal

1045
00:38:11,494 --> 00:38:11,994
orientation

1046
00:38:12,295 --> 00:38:13,230
for this object.

1047
00:38:14,190 --> 00:38:15,550
Yeah. And for those who may not be

1048
00:38:15,550 --> 00:38:17,630
familiar, if you're listening, the sparkline looks like

1049
00:38:17,630 --> 00:38:18,289
a trend.

1050
00:38:18,750 --> 00:38:20,429
And you can you can have it without

1051
00:38:20,429 --> 00:38:22,269
no background and without you can even have

1052
00:38:22,269 --> 00:38:24,429
it without the, with the linear gauge on

1053
00:38:24,429 --> 00:38:26,130
it. So it just looks like the sparkline

1054
00:38:26,190 --> 00:38:28,130
itself. So it's very interesting.

1055
00:38:28,510 --> 00:38:29,010
Yeah.

1056
00:38:29,355 --> 00:38:31,755
So like you said, it's very it's like

1057
00:38:31,755 --> 00:38:33,594
you're gonna have this do with a linear

1058
00:38:33,594 --> 00:38:34,655
gauge and sparkline,

1059
00:38:35,275 --> 00:38:36,255
just the sparkline,

1060
00:38:37,114 --> 00:38:38,574
or just the linear gauge.

1061
00:38:39,594 --> 00:38:41,934
Alright. Moving on to the next one.

1062
00:38:42,980 --> 00:38:44,339
I think this is the last one that

1063
00:38:44,339 --> 00:38:46,339
we're we're last feature that we're going to

1064
00:38:46,339 --> 00:38:47,079
talk about.

1065
00:38:48,579 --> 00:38:50,339
I always try and promote this one because

1066
00:38:50,339 --> 00:38:51,539
I don't think a lot of people are

1067
00:38:51,539 --> 00:38:53,400
aware of the system status portal.

1068
00:38:53,699 --> 00:38:55,460
So for those that do not know what

1069
00:38:55,460 --> 00:38:57,780
the system status portal is, it's basically a

1070
00:38:57,780 --> 00:39:00,554
web page which shows you all your,

1071
00:39:00,954 --> 00:39:03,195
servers and what the health status of it

1072
00:39:03,195 --> 00:39:05,114
is at that point in time. So the

1073
00:39:05,114 --> 00:39:07,695
nice thing is you, go click your application.

1074
00:39:08,155 --> 00:39:10,235
It will show you all your HMI servers.

1075
00:39:10,235 --> 00:39:12,569
It will show you your AlarmNet event servers.

1076
00:39:12,569 --> 00:39:14,429
It will show you your data servers.

1077
00:39:14,969 --> 00:39:17,929
And recently, in version 15, we introduced the

1078
00:39:17,929 --> 00:39:20,109
capability of showing you a Facade Talk historian

1079
00:39:20,250 --> 00:39:21,389
server as well.

1080
00:39:21,929 --> 00:39:24,809
And in version 16, we introduced now being

1081
00:39:24,809 --> 00:39:26,434
able to see the health status of your

1082
00:39:26,434 --> 00:39:29,494
Facade doc asset center server and its agents.

1083
00:39:30,114 --> 00:39:31,715
But you don't have to install this on

1084
00:39:31,715 --> 00:39:33,235
all your machines, by the way. You only

1085
00:39:33,235 --> 00:39:35,335
have to install it on one. We typically

1086
00:39:35,394 --> 00:39:37,715
recommend you install the system status portal on

1087
00:39:37,715 --> 00:39:38,934
your Facade doc directory.

1088
00:39:39,599 --> 00:39:42,180
And when you go create your HMI application,

1089
00:39:42,960 --> 00:39:45,039
you can just do an embedded web,

1090
00:39:45,360 --> 00:39:47,599
page and just point, to that,

1091
00:39:49,360 --> 00:39:49,860
link

1092
00:39:50,480 --> 00:39:51,614
on the Facitoc directory

1093
00:39:52,335 --> 00:39:54,655
basically bring up the system status portal showing

1094
00:39:54,655 --> 00:39:56,434
the overall health of your system,

1095
00:39:57,135 --> 00:39:58,434
at that point in time.

1096
00:39:59,855 --> 00:40:01,474
We made a couple of enhancements

1097
00:40:01,934 --> 00:40:04,369
in version 16 as well. In version

1098
00:40:05,069 --> 00:40:08,190
16, they people want the ability to go

1099
00:40:08,190 --> 00:40:10,609
into dark mode and into light mode.

1100
00:40:11,230 --> 00:40:12,609
And they also

1101
00:40:12,909 --> 00:40:14,369
one of the things that they

1102
00:40:14,829 --> 00:40:16,909
asked us, well, every time you go to

1103
00:40:16,909 --> 00:40:19,425
the system status portal, you have to enter

1104
00:40:19,425 --> 00:40:21,425
your credentials to be able to access the

1105
00:40:21,425 --> 00:40:22,644
information in there.

1106
00:40:22,945 --> 00:40:25,265
Once you navigate away from the system status

1107
00:40:25,265 --> 00:40:27,184
portal and come back, you have to reenter

1108
00:40:27,184 --> 00:40:27,844
those credentials.

1109
00:40:28,305 --> 00:40:30,545
So can you actually give us the keep

1110
00:40:30,545 --> 00:40:31,525
me signed in

1111
00:40:31,825 --> 00:40:32,325
functionality?

1112
00:40:33,400 --> 00:40:35,659
So, we were able to do that,

1113
00:40:36,039 --> 00:40:36,940
in this release.

1114
00:40:37,719 --> 00:40:38,219
And

1115
00:40:38,840 --> 00:40:40,860
moving on to my last slide here,

1116
00:40:41,239 --> 00:40:43,559
I just wanted to talk about support. So

1117
00:40:43,559 --> 00:40:46,199
version 16, we now support Windows Server '20

1118
00:40:46,199 --> 00:40:46,965
20 five.

1119
00:40:48,005 --> 00:40:50,565
Excellent. Excellent. Yeah. This this these charts are

1120
00:40:50,565 --> 00:40:52,724
are key when you, when you're looking to

1121
00:40:52,724 --> 00:40:54,965
install the the software to know which operating

1122
00:40:54,965 --> 00:40:56,025
systems are supported.

1123
00:40:56,885 --> 00:40:58,885
And that's everything I wanted to run through.

1124
00:40:59,285 --> 00:41:01,525
I I hope the information we provided was

1125
00:41:01,525 --> 00:41:02,744
helpful to you as well.

1126
00:41:03,420 --> 00:41:05,039
If you have any questions,

1127
00:41:05,739 --> 00:41:07,599
feel free to contact me directly.

1128
00:41:08,059 --> 00:41:09,659
I don't have my details here, but I

1129
00:41:09,659 --> 00:41:11,659
could probably give it to you, Sean, and,

1130
00:41:12,139 --> 00:41:13,739
people can just reach out to me if

1131
00:41:13,739 --> 00:41:14,239
they

1132
00:41:14,619 --> 00:41:16,859
have any questions or need to reach out

1133
00:41:16,859 --> 00:41:18,284
directly to to us.

1134
00:41:18,844 --> 00:41:20,684
Yeah. I I'll definitely put it on the

1135
00:41:20,684 --> 00:41:21,424
screen here.

1136
00:41:21,804 --> 00:41:23,644
Johan, I wanna thank you for coming on

1137
00:41:23,644 --> 00:41:26,284
the show. I know I mean, we've been

1138
00:41:26,284 --> 00:41:28,224
talking for quite a long time, and you

1139
00:41:28,284 --> 00:41:30,364
obviously can't show all of the new features

1140
00:41:30,364 --> 00:41:31,585
in '15 16.

1141
00:41:32,070 --> 00:41:33,590
But, you know, for those of you who

1142
00:41:33,590 --> 00:41:35,190
want us to know everything that was released

1143
00:41:35,190 --> 00:41:37,349
and updated in those, go back to the

1144
00:41:37,349 --> 00:41:39,110
very beginning where he had those slides up

1145
00:41:39,110 --> 00:41:40,789
with all the the new features. But I

1146
00:41:40,789 --> 00:41:42,809
do appreciate you showing us what you did,

1147
00:41:42,950 --> 00:41:44,469
and that is some really cool,

1148
00:41:45,190 --> 00:41:47,175
innovations. And I think the the one great

1149
00:41:47,175 --> 00:41:49,175
thing is it's you you your team took

1150
00:41:49,175 --> 00:41:51,355
the time to make it faster. And

1151
00:41:51,815 --> 00:41:53,675
I think we all appreciate that because,

1152
00:41:54,375 --> 00:41:56,695
you know, over time, some products get slower.

1153
00:41:56,695 --> 00:41:58,954
And so when the team takes time to

1154
00:41:59,199 --> 00:42:01,760
go through and, optimize the software to make

1155
00:42:01,760 --> 00:42:03,280
it faster, that is such a huge thing.

1156
00:42:03,280 --> 00:42:04,880
And then, of course, to see that you're

1157
00:42:04,880 --> 00:42:07,760
adding new things like the linear gauge and,

1158
00:42:07,760 --> 00:42:10,239
like, you know, the the toggle button, and

1159
00:42:10,239 --> 00:42:11,920
you're adding things to the, you know, to

1160
00:42:12,000 --> 00:42:13,860
just to all the things you covered today,

1161
00:42:14,255 --> 00:42:16,414
especially, you know, expanding the menus, expanding the

1162
00:42:16,414 --> 00:42:16,914
docking.

1163
00:42:17,695 --> 00:42:20,414
I think, the users really, really appreciate that,

1164
00:42:20,414 --> 00:42:22,094
and I know I do. So thank you

1165
00:42:22,094 --> 00:42:23,375
again for coming on the show, and I

1166
00:42:23,375 --> 00:42:25,695
really appreciate it. I appreciate being on the

1167
00:42:25,695 --> 00:42:27,469
show. Thank you. Well, I hope you guys

1168
00:42:27,469 --> 00:42:29,230
enjoyed that episode, and I wanna thank Johan

1169
00:42:29,230 --> 00:42:30,989
for coming on the show and bringing us

1170
00:42:30,989 --> 00:42:32,210
up to speed on FactoryTalk

1171
00:42:32,510 --> 00:42:35,150
Vue fifteen and sixteen. I also wanna thank

1172
00:42:35,150 --> 00:42:37,230
our sponsors, our members over at YouTube and

1173
00:42:37,230 --> 00:42:38,835
theautomationblog.com,

1174
00:42:38,994 --> 00:42:40,855
as well as our students and our VUSC

1175
00:42:40,914 --> 00:42:43,074
course over at The Automation School. We would

1176
00:42:43,074 --> 00:42:44,835
not be able to bring you these type

1177
00:42:44,835 --> 00:42:45,574
of unsponsored

1178
00:42:45,875 --> 00:42:48,355
episodes without your sponsorship, so we really appreciate

1179
00:42:48,355 --> 00:42:51,155
it. Look out for that new extended edition

1180
00:42:51,234 --> 00:42:53,940
ad free extended edition of this episode coming

1181
00:42:53,940 --> 00:42:54,920
your way soon.

1182
00:42:55,300 --> 00:42:57,059
With that said, I wanna thank you all

1183
00:42:57,059 --> 00:42:58,579
for tuning in. I wanna wish you all

1184
00:42:58,579 --> 00:43:00,820
good health and happiness. And until next time,

1185
00:43:00,820 --> 00:43:01,480
my friends.

1186
00:43:02,339 --> 00:43:02,839
Peace.