1
00:00:03,040 --> 00:00:04,320
Like Emily said, I'm Andy.

2
00:00:04,320 --> 00:00:08,240
I'm the product manager for the
all things Red five and in the

3
00:00:08,240 --> 00:00:12,920
HVAC enterprise here
at DIBT, at Delta IBT.

4
00:00:13,205 --> 00:00:17,045
Before I start, I wanna just
see where everybody is with our

5
00:00:17,045 --> 00:00:18,725
product knowledge,

6
00:00:18,725 --> 00:00:20,885
because I don't I wanna make
sure that I can tailor this

7
00:00:20,885 --> 00:00:22,325
depending on who's here.

8
00:00:22,325 --> 00:00:24,645
So if you use your
thumbs up button,

9
00:00:24,645 --> 00:00:28,360
give me a thumbs up for anybody
here that's never heard of

10
00:00:28,360 --> 00:00:30,720
the Red five product line.

11
00:00:32,600 --> 00:00:33,000
Okay.

12
00:00:33,000 --> 00:00:36,120
So either people can't find the
thumbs up or they've all heard of it.

13
00:00:36,120 --> 00:00:38,360
So that's good. Oh, we got
one, and we got a heart.

14
00:00:38,360 --> 00:00:41,280
So I like the I like the
heart. That makes me feel good.

15
00:00:43,235 --> 00:00:44,035
Okay. Good.

16
00:00:44,035 --> 00:00:45,635
So there's a few people
that have never heard of it.

17
00:00:45,635 --> 00:00:48,675
So I'm gonna explain a little
bit of what RED five is,

18
00:00:48,675 --> 00:00:51,675
and I'll give you a
bit of a, background,

19
00:00:52,275 --> 00:00:55,595
where RED five came from
and where we are now.

20
00:00:56,030 --> 00:00:57,590
So today,

21
00:00:58,030 --> 00:01:00,990
we're gonna talk a little bit
about our past that'll help

22
00:01:00,990 --> 00:01:04,950
give you some context, to where
we're going in the future.

23
00:01:05,150 --> 00:01:07,790
And we're gonna talk a little
bit about our Red five pro

24
00:01:07,790 --> 00:01:11,035
program, the Red five field VAV.

25
00:01:11,035 --> 00:01:13,875
Yes. MSTP is still a thing.

26
00:01:13,915 --> 00:01:16,635
Red five edge VAV t one l.

27
00:01:16,635 --> 00:01:20,435
And, I mean, Ethernet on
twisted pair? Get out of here.

28
00:01:21,460 --> 00:01:22,820
Red five unitary,

29
00:01:22,820 --> 00:01:26,420
that's gonna be our brand new
product line coming up in the future.

30
00:01:26,420 --> 00:01:30,420
And, we'll show you a quick road
map of when all these products are

31
00:01:30,420 --> 00:01:33,835
gonna be aligned and
when you can expect them,

32
00:01:33,835 --> 00:01:36,235
and we'll follow it up
with a q and a at the end.

33
00:01:36,235 --> 00:01:38,955
And as Emily said, just please
go ahead and type your chat,

34
00:01:38,955 --> 00:01:40,875
type your question
into the chat,

35
00:01:40,875 --> 00:01:42,715
and we'll address
them at the end.

36
00:01:42,715 --> 00:01:46,795
Normally, I like to address
comments and questions in real

37
00:01:46,795 --> 00:01:49,230
time, but we just have
too many people here.

38
00:01:49,230 --> 00:01:52,150
So it'll be easier just to
address them at the end.

39
00:01:52,990 --> 00:01:56,030
So this is our current
system architecture.

40
00:01:56,030 --> 00:02:00,110
We are going to be playing
around in this area today.

41
00:02:00,110 --> 00:02:03,135
We're not really gonna be
talking too much about system

42
00:02:03,135 --> 00:02:05,815
level controllers or,

43
00:02:07,295 --> 00:02:09,695
you know, enterprise software
or anything like that.

44
00:02:09,695 --> 00:02:14,375
We're gonna be talking about terminal
units and unitary products today.

45
00:02:15,100 --> 00:02:20,300
So that means there are
VAV, VAV, controllers in,

46
00:02:20,300 --> 00:02:24,900
specifically and fan coil
controllers later on today.

47
00:02:26,300 --> 00:02:29,300
But first, I wanna give you
a little bit of history.

48
00:02:29,575 --> 00:02:31,735
So back in the nineties,

49
00:02:31,735 --> 00:02:35,655
we had a VAV line called the
IZC, or if you're from the US,

50
00:02:35,655 --> 00:02:37,255
the IZC.

51
00:02:37,255 --> 00:02:41,095
That stood for the
IntelliZone controller.

52
00:02:41,095 --> 00:02:43,255
IntelliZone with an I.

53
00:02:43,255 --> 00:02:47,560
And this was our old school VAV

54
00:02:47,560 --> 00:02:50,440
controller ran on a
protocol called Micronet,

55
00:02:50,440 --> 00:02:54,080
which was like a twisted
twisted pair cabling,

56
00:02:54,600 --> 00:02:58,200
and it was a predecessor
to the to the old to our

57
00:02:58,200 --> 00:03:01,445
BACnet VAV controller.

58
00:03:01,445 --> 00:03:03,045
So we had that, you know,

59
00:03:03,045 --> 00:03:04,965
running all through the
nineties pretty much until the

60
00:03:04,965 --> 00:03:08,405
early two thousands when
it was superseded by the

61
00:03:08,405 --> 00:03:13,245
DVC v three two two
and v three zero four.

62
00:03:13,280 --> 00:03:18,160
So this is our first foray into
the into the BACnet MSTP world.

63
00:03:18,160 --> 00:03:19,320
And,

64
00:03:19,840 --> 00:03:21,600
this has really been
a flagship product.

65
00:03:21,600 --> 00:03:23,280
I mean, look at
the the timeline.

66
00:03:23,280 --> 00:03:27,075
That should give you a hint of when
we're gonna phase this product out.

67
00:03:27,075 --> 00:03:31,155
But we've got twenty six years
of run time on this particular

68
00:03:31,155 --> 00:03:32,195
VAV controller.

69
00:03:32,195 --> 00:03:35,595
So it really has been
our our bread and butter,

70
00:03:36,515 --> 00:03:39,715
and it's a flagship product
for us over the years.

71
00:03:39,715 --> 00:03:42,640
So we don't take it lightly
when we know that we have to do

72
00:03:42,640 --> 00:03:43,680
a successor.

73
00:03:43,680 --> 00:03:46,960
And it really I mean, I'm
not I wouldn't be here today,

74
00:03:46,960 --> 00:03:49,600
talking to you guys if it
weren't for the DVC product

75
00:03:49,600 --> 00:03:51,360
line, I'm to be honest with you.

76
00:03:51,360 --> 00:03:55,160
There's hundreds of hundreds of thousands
of these out there in the real world.

77
00:03:56,955 --> 00:04:01,595
Around the, mid twenty tens
ish, we came out with a,

78
00:04:01,595 --> 00:04:03,675
what we call the Ntelezone.

79
00:04:03,675 --> 00:04:05,675
That's Ntele with an e.

80
00:04:05,675 --> 00:04:07,915
This is a VAV
controller that was

81
00:04:07,915 --> 00:04:10,340
used kind of in in a more fixed

82
00:04:10,340 --> 00:04:11,940
algorithm kind of scenario.

83
00:04:11,940 --> 00:04:15,780
A lot of these were used in
cost sensitive applications.

84
00:04:15,780 --> 00:04:16,940
And,

85
00:04:18,580 --> 00:04:20,580
you know, we're still
we're still working on it,

86
00:04:20,580 --> 00:04:23,060
but we have to start thinking
about the successor to this

87
00:04:23,060 --> 00:04:24,525
product line as well.

88
00:04:24,525 --> 00:04:26,845
We still sell a
lot of IntelliZone,

89
00:04:26,845 --> 00:04:28,845
but there they are.

90
00:04:28,845 --> 00:04:31,085
They are getting long in the
tooth now over ten years.

91
00:04:31,085 --> 00:04:33,885
I I still refer to this
as the new VAP controller,

92
00:04:33,885 --> 00:04:35,925
and we're in twelve years.

93
00:04:36,125 --> 00:04:41,140
So this will start to get
phased out, later this decade,

94
00:04:41,180 --> 00:04:44,020
as the RED five
products come in.

95
00:04:46,460 --> 00:04:47,740
So what's new then?

96
00:04:47,740 --> 00:04:51,340
So I've told you about what's going
on in the past where we've been.

97
00:04:51,340 --> 00:04:52,260
Well,

98
00:04:54,145 --> 00:04:59,145
last year, we introduced,
the RED five VAV controller.

99
00:04:59,265 --> 00:05:03,025
This is one of Emily's
taglines, compact and mighty.

100
00:05:03,025 --> 00:05:05,465
And we get we say
mighty with a fist.

101
00:05:06,230 --> 00:05:09,750
This is our new flagship
VAV product line.

102
00:05:09,750 --> 00:05:12,630
And I'll tell you something
kinda funny about it,

103
00:05:12,630 --> 00:05:15,430
and I'm gonna tell you a little
bit more about it in a second.

104
00:05:15,430 --> 00:05:19,190
But RED five VAV
controllers now account for

105
00:05:19,190 --> 00:05:23,235
over fifty four percent
of all of our VAV sales.

106
00:05:23,515 --> 00:05:26,315
So that tells you a little bit
about the adoption of this product.

107
00:05:26,315 --> 00:05:30,955
It's only been around for,
well, ten months now, and,

108
00:05:30,955 --> 00:05:35,475
it's already overtaken, what
we're doing with the DVC products.

109
00:05:38,300 --> 00:05:41,660
So a lot of the intent
behind the RED five product line was

110
00:05:41,660 --> 00:05:45,740
to build a controller that
was powerful enough that could

111
00:05:45,740 --> 00:05:48,660
grow with your
building over time.

112
00:05:48,775 --> 00:05:51,735
We wanna say goodbye to the
rip and replace cycle where a

113
00:05:51,735 --> 00:05:55,255
product maybe only have may
only have five or ten years.

114
00:05:55,255 --> 00:05:58,295
And we know that our industry

115
00:05:58,295 --> 00:06:00,855
changes and and especially now
here we are in twenty twenty

116
00:06:00,855 --> 00:06:04,970
six that, we've got technology
is growing so quickly,

117
00:06:04,970 --> 00:06:05,850
and there's new needs.

118
00:06:05,850 --> 00:06:08,770
There's AI. Everyone's
using buzzwords.

119
00:06:08,890 --> 00:06:13,130
The impact on on the
network infrastructure and

120
00:06:13,130 --> 00:06:17,795
the network requirements
have directed us to

121
00:06:17,795 --> 00:06:21,315
build a product that can
be scalable with your building

122
00:06:21,315 --> 00:06:24,915
over time, and that's why
the Red five VAV was born.

123
00:06:24,915 --> 00:06:26,755
It's still lay
legacy compatible,

124
00:06:26,755 --> 00:06:30,520
so it could still coexist and
play nice with older products,

125
00:06:30,520 --> 00:06:32,800
DVCs, ezone.

126
00:06:33,560 --> 00:06:36,520
But the intent is for
it to grow over time,

127
00:06:36,520 --> 00:06:38,560
as your building needs grow.

128
00:06:42,065 --> 00:06:45,705
Red five VAV has, a lot of

129
00:06:46,465 --> 00:06:50,305
a lot of the underlying
parts of the Red five

130
00:06:50,305 --> 00:06:54,105
VAV is compliance with
guideline thirty six.

131
00:06:54,145 --> 00:06:56,750
We have built in databases.

132
00:06:56,750 --> 00:06:59,070
So if you buy a Red
five VAV controller,

133
00:06:59,070 --> 00:07:00,750
you can set it up before
you even power it on.

134
00:07:00,750 --> 00:07:03,790
You can tell it what VAV
algorithm you want it to use.

135
00:07:03,790 --> 00:07:05,390
You power it up, away you go,

136
00:07:05,390 --> 00:07:07,950
and you can even edit
those programs as you go.

137
00:07:07,950 --> 00:07:11,510
So it's kinda like having a
the dreaded fixed algorithm,

138
00:07:11,765 --> 00:07:15,325
but you can still program it at
the same time if you need to.

139
00:07:15,365 --> 00:07:18,445
Zero drift differential
pressure sensor,

140
00:07:18,725 --> 00:07:21,925
the ability to, have
sustainability metrics.

141
00:07:21,925 --> 00:07:26,320
We've we've unlocked a lot of features
through our PG Python interface.

142
00:07:26,320 --> 00:07:28,880
So you've got GCL
to do your control.

143
00:07:28,880 --> 00:07:30,960
You got Python to do your IoT.

144
00:07:30,960 --> 00:07:32,720
So with all these
bells and whistles,

145
00:07:32,720 --> 00:07:34,000
and in order to support that,

146
00:07:34,000 --> 00:07:35,920
we have to have the power
under the hood to do it.

147
00:07:35,920 --> 00:07:39,720
And that's what we mean by a
scalable controller over time.

148
00:07:40,695 --> 00:07:42,135
On top of that, we all you know,

149
00:07:42,135 --> 00:07:43,895
we have to stick to
the basics as well.

150
00:07:43,895 --> 00:07:46,375
So we wanna make sure that
commissioning is easier,

151
00:07:46,375 --> 00:07:50,215
that you can, improve
your installation times and get

152
00:07:50,215 --> 00:07:52,855
those products in and
get off the job quicker.

153
00:07:52,855 --> 00:07:56,095
And we do that by reducing
your ladder trips,

154
00:07:56,670 --> 00:07:59,150
giving guys a
bidirectional flow sensor.

155
00:07:59,150 --> 00:08:01,790
So now even with the fifty
percent chance of getting it

156
00:08:01,790 --> 00:08:05,710
wrong, when you know what the,
the high and the low side is,

157
00:08:05,710 --> 00:08:07,070
you don't have to worry
about that anymore.

158
00:08:07,070 --> 00:08:08,910
You can just hook the tubes
up however you need to,

159
00:08:08,910 --> 00:08:10,710
and the controller will know

160
00:08:11,465 --> 00:08:14,465
how to scale that
pressure correctly.

161
00:08:16,585 --> 00:08:18,025
And as I mentioned before,

162
00:08:18,025 --> 00:08:20,745
we've got a lot of
VAV applications.

163
00:08:20,745 --> 00:08:23,630
We used to try Emily and I used
to try and figure out how many

164
00:08:23,630 --> 00:08:26,190
different applications we had
built into the controller.

165
00:08:26,190 --> 00:08:28,430
And we started with fifty,
then it was fifty five,

166
00:08:28,430 --> 00:08:31,150
then it was sixty eight, and
I I don't even know anymore.

167
00:08:31,150 --> 00:08:33,470
So we'll just let's just
say there's lots of VAV

168
00:08:33,470 --> 00:08:36,510
applications built in all the
way from guideline thirty six

169
00:08:36,510 --> 00:08:39,925
deep dive applications all
the way just to standard basic

170
00:08:39,925 --> 00:08:42,165
VAV, algorithms.

171
00:08:42,165 --> 00:08:45,285
So you guys can either program
it yourself using your own,

172
00:08:45,285 --> 00:08:48,805
or you can use ours
and edit them however,

173
00:08:48,805 --> 00:08:50,520
however you see fit.

174
00:08:50,520 --> 00:08:54,600
And that can all be enabled
just by the scan of your phone

175
00:08:54,600 --> 00:08:55,640
onto the controller.

176
00:08:55,640 --> 00:08:59,400
I've got several VAVs running in
my office that I had fully

177
00:08:59,400 --> 00:09:01,240
set up and commission
or not commissioned,

178
00:09:01,240 --> 00:09:05,760
fully set up and configured with
algorithms before I even opened the box.

179
00:09:09,945 --> 00:09:13,865
So what does this look like in
context of of of a whole BMS

180
00:09:13,865 --> 00:09:16,585
network or for a Delta network?

181
00:09:16,585 --> 00:09:19,865
Well, this image shows you essentially
three different network types.

182
00:09:19,865 --> 00:09:24,090
The blue line up here let me
get my little, highlighter out.

183
00:09:24,090 --> 00:09:27,490
This blue line up here, that's,

184
00:09:28,330 --> 00:09:32,090
your standard BACnet MSTP
cable and your twenty two

185
00:09:32,090 --> 00:09:34,530
gauge twisted pair.

186
00:09:35,105 --> 00:09:36,865
The orange line down here,

187
00:09:36,865 --> 00:09:38,225
I'm gonna talk about
that in a moment.

188
00:09:38,225 --> 00:09:42,225
That's a t one l, network.
Again, it's on twisted pair.

189
00:09:42,225 --> 00:09:44,385
Could be a legacy
infrastructure,

190
00:09:44,385 --> 00:09:48,065
but it's Ethernet carried
over twisted pair.

191
00:09:48,065 --> 00:09:51,550
And then the bottom
one is your standard,

192
00:09:51,750 --> 00:09:54,070
cat five, cat six Ethernet.

193
00:09:54,070 --> 00:09:56,950
But you'll notice that these
products are all in a daisy chain.

194
00:09:56,950 --> 00:10:00,430
All these VAV controllers are
in a daisy chain configuration.

195
00:10:01,925 --> 00:10:03,205
So starting last year,

196
00:10:03,205 --> 00:10:05,765
let's just look at the Ethernet
side of things for now.

197
00:10:05,765 --> 00:10:08,325
Our standard old
Ethernet, tried and true.

198
00:10:08,325 --> 00:10:11,805
We know everything about it.
We've we're we're used to it.

199
00:10:14,180 --> 00:10:17,380
That's what we call our Red
five Edge VAV controller.

200
00:10:17,380 --> 00:10:19,980
This is our dual
Ethernet controller,

201
00:10:20,660 --> 00:10:22,740
with bypass relays.

202
00:10:22,740 --> 00:10:23,700
We have two models.

203
00:10:23,700 --> 00:10:26,500
We have one, the v one
hundred, which is cooling only,

204
00:10:26,500 --> 00:10:27,620
and the v four forty,

205
00:10:27,620 --> 00:10:32,085
which has the extended IO for
reheat and maybe picking up, like,

206
00:10:32,085 --> 00:10:37,005
base heat baseboard heaters or or
whatever it is that you need to pick up.

207
00:10:38,005 --> 00:10:41,645
Standard twenty four volt AC
DC powered yada yada yada.

208
00:10:42,930 --> 00:10:46,210
But a cool thing about it is
the fact that we've added the

209
00:10:46,210 --> 00:10:49,090
ability to be a BACnetSC node.

210
00:10:49,090 --> 00:10:51,570
And this is basically going
into anything that's a v four

211
00:10:51,570 --> 00:10:56,170
IP controller, the capability
of being a BACnetSC node.

212
00:10:56,375 --> 00:10:58,855
It still supports things
like LinkNet for your LinkNet

213
00:10:58,855 --> 00:11:02,095
sensors, for your stats.

214
00:11:03,015 --> 00:11:06,455
It has the built in, Bulimo
actuator with feedback.

215
00:11:06,455 --> 00:11:10,330
So you've got analog control over
the fee over the actuator with,

216
00:11:10,330 --> 00:11:12,890
analog feedback so you
know what what position the

217
00:11:12,890 --> 00:11:14,170
actuator's in.

218
00:11:14,170 --> 00:11:16,970
And we released
this guy, last year,

219
00:11:16,970 --> 00:11:19,690
last July is when we were
finally able to ship it,

220
00:11:19,690 --> 00:11:21,490
July twenty twenty five.

221
00:11:22,685 --> 00:11:24,685
So this is really
our flagship VAV.

222
00:11:24,685 --> 00:11:27,965
It was the first one we
released and it took off like

223
00:11:27,965 --> 00:11:30,045
gangbusters when we released it.

224
00:11:30,045 --> 00:11:33,725
And as I mentioned, we're
like it's accounting for over

225
00:11:33,725 --> 00:11:36,805
fifty percent now of
our total VAV sales.

226
00:11:39,480 --> 00:11:40,920
So that was the Edge.

227
00:11:40,920 --> 00:11:44,160
Now I wanna talk
to you guys about

228
00:11:45,080 --> 00:11:48,280
a relatively new VAV controller
that we just released last

229
00:11:48,280 --> 00:11:51,160
December, and that is the Field.

230
00:11:51,160 --> 00:11:55,105
And it's an MSTP controller.

231
00:11:55,105 --> 00:11:58,785
This is this is really the
the DVC replacement now.

232
00:11:58,785 --> 00:12:03,465
Again, this comes in your cooling only
model and your extended IO reheat model.

233
00:12:04,770 --> 00:12:07,890
But the difference with this
particular controller is it's

234
00:12:07,890 --> 00:12:10,330
backed at MSTP only.

235
00:12:10,930 --> 00:12:14,370
It supports LinkNet,
and importantly,

236
00:12:14,370 --> 00:12:17,330
it can coexist with legacy
products or other third party

237
00:12:17,330 --> 00:12:19,050
MSTP devices.

238
00:12:20,335 --> 00:12:22,575
We released this in
December twenty twenty five.

239
00:12:22,575 --> 00:12:25,775
So I just wanted to remind
you guys that, you know,

240
00:12:25,775 --> 00:12:28,735
this sort of this product kinda
snuck out right at Christmas

241
00:12:28,735 --> 00:12:30,975
time without a lot of fanfare.

242
00:12:30,975 --> 00:12:35,560
So I want you guys to consider
this as the relaunch of

243
00:12:35,560 --> 00:12:37,400
the Red five field
VAV controller.

244
00:12:37,400 --> 00:12:38,760
So, Emily, I don't know
if you've got, like,

245
00:12:38,760 --> 00:12:43,280
a a burst emoji you can send out

246
00:12:43,640 --> 00:12:47,600
for the official Red
five VAV field relaunch.

247
00:12:49,195 --> 00:12:52,075
So we're starting to we're this
this controller is starting to

248
00:12:52,075 --> 00:12:53,115
pick up a lot of steam.

249
00:12:53,115 --> 00:12:56,515
It's probably the
second highest sale,

250
00:12:57,115 --> 00:13:00,755
VAV controller sitting
in our our arsenal now.

251
00:13:00,875 --> 00:13:04,910
So it proves to us that as much
as we'd like to see MSTP go

252
00:13:04,910 --> 00:13:09,230
away, MSTP is just
it's it's slowly

253
00:13:09,230 --> 00:13:10,670
dragging itself out there.

254
00:13:10,670 --> 00:13:14,270
It's it'll it'll I think
it'll be like Charlton Heston.

255
00:13:14,270 --> 00:13:14,510
You know?

256
00:13:14,510 --> 00:13:18,150
The MSTP can be removed
from its cold dead hands,

257
00:13:19,765 --> 00:13:22,645
But it's still there, and
it's still very much a thing,

258
00:13:22,645 --> 00:13:25,765
and we still need to do a
product that that can run on v

259
00:13:25,765 --> 00:13:27,525
on MSTP for those sites.

260
00:13:27,525 --> 00:13:30,005
There's a lot of MSTP out there,

261
00:13:30,005 --> 00:13:32,925
and we can't just forsake it.

262
00:13:35,600 --> 00:13:38,400
But even though this doesn't
have the IP controller bells

263
00:13:38,400 --> 00:13:40,400
and whistles, it doesn't
have you know, obviously,

264
00:13:40,400 --> 00:13:41,760
doesn't have embedded graphics.

265
00:13:41,760 --> 00:13:43,320
It doesn't have,

266
00:13:44,160 --> 00:13:47,680
you know, IP capability,
but it still has the same

267
00:13:47,680 --> 00:13:50,795
power under the hood
as the IP controller.

268
00:13:50,795 --> 00:13:53,915
So it's got the built in
selectable GCL databases.

269
00:13:53,915 --> 00:13:57,835
It's got the the,
bidirectional pressure sensor.

270
00:13:57,835 --> 00:14:02,130
It's got, the zero drift
differential pressure sensor.

271
00:14:02,130 --> 00:14:05,170
So it it it's a pretty
extremely powerful controller

272
00:14:05,170 --> 00:14:10,010
for, a guy that's just sitting
on an m s MSTP network.

273
00:14:10,610 --> 00:14:12,210
So that's the field VAV.

274
00:14:12,210 --> 00:14:15,490
That is the MSTP controller.

275
00:14:15,490 --> 00:14:18,090
So welcome to our world

276
00:14:18,605 --> 00:14:20,645
Field VAV.

277
00:14:22,845 --> 00:14:27,165
Now we like saying when we
when we started launching all of our

278
00:14:27,165 --> 00:14:30,765
RED five products, you know,
we get the streamlined install,

279
00:14:30,765 --> 00:14:34,050
we get the future proof
design, the energy efficiency,

280
00:14:34,050 --> 00:14:38,050
flexibility, BACnet secure connect,
and it's the last

281
00:14:38,050 --> 00:14:40,410
VAV you will ever need.

282
00:14:40,450 --> 00:14:41,810
That's why I've
highlighted that.

283
00:14:41,810 --> 00:14:44,650
It's the last VAV
you'll ever need.

284
00:14:44,850 --> 00:14:46,930
But wait. There's more.

285
00:14:46,930 --> 00:14:49,535
There must be something
else coming down the line.

286
00:14:49,535 --> 00:14:53,535
So maybe the field and the
edge wasn't the last VAV

287
00:14:53,535 --> 00:14:55,255
you'll ever need.

288
00:14:55,775 --> 00:14:59,775
What if I told you you could
add performance to existing

289
00:14:59,775 --> 00:15:01,655
legacy infrastructure?

290
00:15:02,950 --> 00:15:06,150
What if I told you you could
bring the building to the

291
00:15:06,150 --> 00:15:08,750
future without
having to rewire it?

292
00:15:09,110 --> 00:15:11,150
That's my sales voice.

293
00:15:11,270 --> 00:15:13,910
What if I told you you can
reuse your existing r s four

294
00:15:13,910 --> 00:15:16,590
eighty five twisted
pair lawn cabling,

295
00:15:17,005 --> 00:15:19,725
avoiding disruptive
expensive cabling overhauls,

296
00:15:19,725 --> 00:15:22,725
seamlessly replace
MSTP or lawn works.

297
00:15:24,285 --> 00:15:29,045
It's all true with the
RED five v a v t one l.

298
00:15:29,280 --> 00:15:33,120
This is a brand spanking
new, v a v controller.

299
00:15:33,120 --> 00:15:36,240
It's been in beta since
February twenty twenty six,

300
00:15:36,240 --> 00:15:39,320
so it's been running in beta
for a couple of months now.

301
00:15:39,520 --> 00:15:45,000
We've got, I think we have four good beta
sites out there that have been running this.

302
00:15:45,815 --> 00:15:50,055
This product is is essentially
exactly the same as

303
00:15:50,055 --> 00:15:54,255
the standard Red five
Edge v a b controller,

304
00:15:54,295 --> 00:15:57,735
only it doesn't use, r
g forty five connectors.

305
00:15:57,735 --> 00:15:59,415
It now uses t one l connectors.

306
00:15:59,415 --> 00:16:02,610
So it's running ten
base t one l Ethernet

307
00:16:02,610 --> 00:16:08,250
over twisted pair, and that's
what these ports here are.

308
00:16:08,770 --> 00:16:11,210
These are the t one l ports.

309
00:16:11,970 --> 00:16:14,925
And what you'll do is
you'll all your cable on

310
00:16:14,925 --> 00:16:17,005
MSTP. I'm getting a
bit ahead of myself.

311
00:16:17,005 --> 00:16:20,085
And you'll terminate
it as t one l.

312
00:16:20,125 --> 00:16:22,845
So this, again, is an
IoT ready controller.

313
00:16:22,845 --> 00:16:26,365
It has all the built in
selectable GCL database.

314
00:16:26,365 --> 00:16:29,605
Everything that all the
other VAV controllers have,

315
00:16:29,960 --> 00:16:33,880
except it's on t one l rather
than standard Ethernet.

316
00:16:33,880 --> 00:16:36,440
It'll support embedded
graphics, BACnet Secure

317
00:16:36,440 --> 00:16:40,240
Connect, and there's
some interesting,

318
00:16:40,360 --> 00:16:43,800
side effects for having BACnet
SC and the level that you can

319
00:16:43,800 --> 00:16:45,440
now have full

320
00:16:46,145 --> 00:16:48,345
encryption on your network.

321
00:16:49,825 --> 00:16:52,625
Release coming coming soon.

322
00:16:52,625 --> 00:16:54,865
We're in quarter two of
twenty twenty six now.

323
00:16:54,865 --> 00:16:59,220
We're just basically
finishing off our beta cycle,

324
00:16:59,820 --> 00:17:03,940
cleaning up any last little
remaining bugs that we know about,

325
00:17:04,940 --> 00:17:07,340
and then we'll be
releasing this next month.

326
00:17:07,340 --> 00:17:10,220
And, so far, we're
looking really good.

327
00:17:10,220 --> 00:17:13,380
We're, we're on track
to meet this date.

328
00:17:15,955 --> 00:17:17,555
So there will be an
announcement soon.

329
00:17:17,555 --> 00:17:20,795
I think Emily's even
behind that announcement. Are you?

330
00:17:21,315 --> 00:17:24,355
Soon. Couple weeks.
A week? A week.

331
00:17:24,355 --> 00:17:25,075
Yeah.

332
00:17:25,075 --> 00:17:29,690
So in order to utilize in order

333
00:17:29,690 --> 00:17:33,290
to utilize the t one
l, VAV controller,

334
00:17:33,290 --> 00:17:35,370
you'll also need this
little guy, the con t one l,

335
00:17:35,370 --> 00:17:37,770
and I'll show you what that
architecture looks like in a second.

336
00:17:37,770 --> 00:17:41,730
The VAV itself, I'll go back,
has the built in t one l,

337
00:17:42,170 --> 00:17:43,250
connectors,

338
00:17:43,855 --> 00:17:48,055
But you can add that t
one l to any network,

339
00:17:48,175 --> 00:17:51,055
whether it's a Delta network
like a plus controller or

340
00:17:51,055 --> 00:17:54,255
whether you wanna just connect
them to a standard switch,

341
00:17:54,255 --> 00:17:57,320
BMS switch, you can do that
through the con t one l.

342
00:17:57,320 --> 00:17:59,400
So I just I didn't wanna
make a big deal about this.

343
00:17:59,400 --> 00:18:00,600
We've done webinars on this.

344
00:18:00,600 --> 00:18:05,080
I've done, training sessions on this
and and breakout sessions, etcetera.

345
00:18:05,080 --> 00:18:07,720
But I just wanted to remind
you that this little utensil

346
00:18:07,720 --> 00:18:12,280
exists, and it allows you
to basically bring t one

347
00:18:12,280 --> 00:18:16,125
l to any, standard,

348
00:18:16,245 --> 00:18:17,205
Ethernet network.

349
00:18:17,205 --> 00:18:19,925
You just have to you just have
to connect this to it basically

350
00:18:19,925 --> 00:18:24,205
converts your, cat five,
cat six to a t one l.

351
00:18:24,485 --> 00:18:26,965
This has been released
since October twenty five,

352
00:18:26,965 --> 00:18:28,720
October twenty twenty five.

353
00:18:28,720 --> 00:18:32,640
And I really wanted to point
out that it is system agnostic,

354
00:18:32,640 --> 00:18:35,760
meaning it doesn't have to
attach to a Delta controller.

355
00:18:35,760 --> 00:18:38,760
It can attach to any
Ethernet, product.

356
00:18:41,505 --> 00:18:43,665
So if we were to take
a network like this,

357
00:18:43,665 --> 00:18:45,665
I'm gonna pick on the
DVC for a second here.

358
00:18:45,665 --> 00:18:49,265
So this orange cable there
is your standard low cap

359
00:18:49,265 --> 00:18:52,025
shielded balanced twisted pair,

360
00:18:52,145 --> 00:18:54,185
twenty two or twenty four gauge,

361
00:18:54,270 --> 00:18:58,070
and you'll notice that it's in
a daisy chain configuration.

362
00:18:59,310 --> 00:19:02,070
Well, you can leave
all that cable there.

363
00:19:02,430 --> 00:19:04,950
Whoops. I got too many whoops.

364
00:19:05,310 --> 00:19:08,190
It's it's played my animations
without me wanting to let me

365
00:19:08,190 --> 00:19:08,990
just back this up here.

366
00:19:08,990 --> 00:19:10,070
There we go.

367
00:19:10,805 --> 00:19:13,685
I've added the CON t one
l to a plus controller,

368
00:19:13,685 --> 00:19:16,845
and then without having
to replace all that cable,

369
00:19:17,445 --> 00:19:19,525
we were just able to
replace the devices.

370
00:19:19,525 --> 00:19:24,165
So now the benefit of doing
this is we've brought in IoT

371
00:19:24,165 --> 00:19:28,270
capability and network security
without having to replace the

372
00:19:28,270 --> 00:19:30,790
infrastructure, the
cabling infrastructure.

373
00:19:30,990 --> 00:19:35,590
Now one of the things we did have
to do is we have to re terminate

374
00:19:36,030 --> 00:19:39,790
at each point because you
can't run t m t one l in, like,

375
00:19:39,790 --> 00:19:42,625
a standard multidrop
daisy chain.

376
00:19:42,625 --> 00:19:45,465
So you have to re
terminate each each,

377
00:19:46,065 --> 00:19:47,385
connector

378
00:19:47,905 --> 00:19:49,025
and then separate it,

379
00:19:49,025 --> 00:19:51,665
and then we handle the pass
through through a set of,

380
00:19:51,665 --> 00:19:53,505
pass through relays
in the controller.

381
00:19:53,505 --> 00:19:55,570
So if a controller
drops offline,

382
00:19:55,570 --> 00:19:58,450
this line will
still be maintained,

383
00:19:58,450 --> 00:20:02,090
and the communication of your
downstream devices will still be there.

384
00:20:02,370 --> 00:20:04,890
So what this gives us is

385
00:20:05,410 --> 00:20:08,970
encryption right down to the
terminal controller level

386
00:20:09,695 --> 00:20:11,215
through BACnet Secure Connect.

387
00:20:11,215 --> 00:20:14,415
So each one of those devices
is now a BACnet Secure Connect

388
00:20:14,415 --> 00:20:16,575
node, and they can,

389
00:20:16,575 --> 00:20:20,575
they can lock in and be part of
the network with any BACnet SC hub,

390
00:20:20,575 --> 00:20:24,935
whether that's a plus controller
or your IntelliWeb server.

391
00:20:26,070 --> 00:20:30,550
Also gives you the ability to
unlock the power of Python,

392
00:20:30,550 --> 00:20:34,630
the Python on PG, and to
give you IT capabilities

393
00:20:34,630 --> 00:20:38,390
such as MQTT, or you
can reach out to web

394
00:20:38,390 --> 00:20:40,030
services like

395
00:20:40,515 --> 00:20:45,915
weather services or maybe Cisco routers
or whatever it is you need to do.

396
00:20:46,275 --> 00:20:48,595
That's all unlocked
through Python.

397
00:20:48,595 --> 00:20:52,515
And that's now right down to
the terminal unit level or

398
00:20:52,515 --> 00:20:55,900
unitary level, which
is pretty cool.

399
00:20:55,940 --> 00:20:59,060
Incidentally, each one of those
controllers also has its own embedded web

400
00:20:59,060 --> 00:21:03,900
servers so you can have a a graphic
for each VAV box on each device.

401
00:21:03,940 --> 00:21:05,060
And that's all, you know,

402
00:21:05,060 --> 00:21:07,700
without having to replace the
full blown infrastructure of

403
00:21:07,700 --> 00:21:09,180
the of the network.

404
00:21:13,995 --> 00:21:16,955
So this is what it looks like
when you look at it from the

405
00:21:16,955 --> 00:21:18,075
grand scheme of things.

406
00:21:18,075 --> 00:21:21,435
So we've talked about
the MSTP network.

407
00:21:21,435 --> 00:21:24,915
We've talked about a
standard cat five network,

408
00:21:25,710 --> 00:21:29,630
and now we've talked
about a t one l network.

409
00:21:29,630 --> 00:21:32,550
And we're seeing more
and more of these,

410
00:21:32,590 --> 00:21:34,110
flat network architectures.

411
00:21:34,110 --> 00:21:36,670
It's a big push here
internally at Delta.

412
00:21:36,670 --> 00:21:39,525
We're coming up
with new guidelines,

413
00:21:39,525 --> 00:21:42,965
revising old guidelines
on how you deal with

414
00:21:42,965 --> 00:21:46,565
large flat networks and
network best practices.

415
00:21:46,565 --> 00:21:49,565
So keep your eye
open for your email

416
00:21:50,860 --> 00:21:54,460
for an email from us on how
we're addressing these these

417
00:21:54,460 --> 00:21:56,140
larger flat networks.

418
00:21:56,140 --> 00:21:59,100
Incidentally, I wanna
ask you guys a pop quiz.

419
00:21:59,100 --> 00:22:01,980
So get your little
thumb emoji out,

420
00:22:01,980 --> 00:22:04,275
and I wanna see a thumbs up.

421
00:22:04,275 --> 00:22:06,115
This is a yes or no question.

422
00:22:06,115 --> 00:22:09,555
Is this this is a pop
quest pop quiz, guys.

423
00:22:09,555 --> 00:22:12,395
Is this device here
that I've circled

424
00:22:12,595 --> 00:22:14,555
and this device here,

425
00:22:16,690 --> 00:22:22,010
thumbs up for everybody that thinks
that this is on the same network.

426
00:22:24,050 --> 00:22:26,250
Okay. If we got a
couple of people.

427
00:22:28,945 --> 00:22:31,105
Okay. Lots of
thumbs. This is good.

428
00:22:31,105 --> 00:22:32,385
So you guys are
paying attention.

429
00:22:32,385 --> 00:22:34,545
So the correct answer is yes.

430
00:22:34,545 --> 00:22:37,585
These are absolutely on the
same IP subnet, therefore,

431
00:22:37,585 --> 00:22:38,625
the same network.

432
00:22:38,625 --> 00:22:42,225
So therefore, your wiring guidelines
that's in the existing Delta wiring

433
00:22:42,225 --> 00:22:46,730
guidelines on how to build
a IP network and set up your

434
00:22:46,730 --> 00:22:50,490
network numbers, all
of that is still valid.

435
00:22:50,490 --> 00:22:52,090
It's not changed.

436
00:22:52,090 --> 00:22:56,570
So thumbs up to I wanna get you

437
00:22:56,570 --> 00:22:58,005
guys give me a thumbs up.

438
00:22:58,005 --> 00:23:01,925
Is t one l a new form of

439
00:23:01,925 --> 00:23:06,445
MSTP? Anybody that thinks
it is, give me a thumbs up.

440
00:23:09,285 --> 00:23:10,965
Oh, good. Okay.

441
00:23:10,965 --> 00:23:15,330
Give me a thumbs up if you
agree that t one l is just a

442
00:23:15,330 --> 00:23:18,970
new way to carry
Ethernet and IP.

443
00:23:21,970 --> 00:23:24,690
Excellent. That's
what I wanna see.

444
00:23:24,690 --> 00:23:29,145
So t one l is not a faster MSTP.

445
00:23:29,145 --> 00:23:33,225
T one l is an
ability to carry your

446
00:23:33,225 --> 00:23:35,185
IP Ethernet

447
00:23:37,865 --> 00:23:40,225
over balanced twisted pair.

448
00:23:42,480 --> 00:23:46,440
Thumbs up if you
agree with this.

449
00:23:46,880 --> 00:23:51,600
T one l and MSTP can exist
on the same network cable.

450
00:23:51,600 --> 00:23:53,800
Give me a thumbs up if
you agree with that.

451
00:23:56,175 --> 00:23:58,175
Oh, good. I've got
scared faces. Good.

452
00:23:58,175 --> 00:23:59,855
So, no, t one l,

453
00:23:59,855 --> 00:24:03,615
MSTP cannot exist
on the same network.

454
00:24:03,615 --> 00:24:06,735
So and I'm gonna talk more about
that in a in a second here.

455
00:24:06,735 --> 00:24:09,130
I just wanna make
that really clear.

456
00:24:09,130 --> 00:24:10,730
And I saw one guy comment. Yeah.

457
00:24:10,730 --> 00:24:10,970
No.

458
00:24:10,970 --> 00:24:13,610
T one l is not that
new, but it's new to us,

459
00:24:13,610 --> 00:24:16,130
and it's gonna be
new to you guys.

460
00:24:18,090 --> 00:24:22,850
We've we've actually had our our eye
on t one l for probably ten years,

461
00:24:23,275 --> 00:24:28,395
easily ten years,
but we waited to get

462
00:24:28,395 --> 00:24:30,155
a read on where it was going.

463
00:24:30,155 --> 00:24:32,075
And actually, to
be quite honest,

464
00:24:32,075 --> 00:24:33,595
we're waiting for costs,

465
00:24:33,595 --> 00:24:38,035
to become reasonable to actually
include it in our product.

466
00:24:40,050 --> 00:24:41,570
So the benefits of t one,

467
00:24:41,570 --> 00:24:43,730
I wanna go over a few things
here because it's not just

468
00:24:43,730 --> 00:24:47,890
magic in a box and there
it's not like you still have

469
00:24:47,890 --> 00:24:51,090
to do your due diligence and
you still have to prepare your

470
00:24:51,090 --> 00:24:52,490
site accordingly.

471
00:24:52,805 --> 00:24:56,885
And I wanna be transparent with
what we've encountered during

472
00:24:56,885 --> 00:25:00,765
our development phase
of the t one l products.

473
00:25:01,525 --> 00:25:03,205
So there are some
benefits of it.

474
00:25:03,205 --> 00:25:07,290
This first one here, I take a
little issue. Long cable runs.

475
00:25:07,290 --> 00:25:09,490
Now they claim,

476
00:25:10,250 --> 00:25:14,410
they the proverbial they claim
that t one l stands for a

477
00:25:14,410 --> 00:25:16,890
single twisted pair
over long distances.

478
00:25:16,890 --> 00:25:20,970
And the claim is that you
can run up to one kilometer

479
00:25:20,970 --> 00:25:22,935
between two peer devices.

480
00:25:22,935 --> 00:25:26,575
So that's peer to
peer, one kilometer.

481
00:25:27,415 --> 00:25:30,895
In our experience, that's
purely theoretical.

482
00:25:31,335 --> 00:25:35,815
In our internal testing under
pretty perfect conditions,

483
00:25:35,815 --> 00:25:40,000
we have yet to achieve one
kilometer between two devices.

484
00:25:42,280 --> 00:25:46,040
We've successfully tested up
to about six hundred meters

485
00:25:46,040 --> 00:25:48,760
between two, peer to peer.

486
00:25:48,760 --> 00:25:50,680
But, again, that's under
perfect conditions.

487
00:25:50,680 --> 00:25:54,045
That's under really controlled
circumstances where we

488
00:25:54,045 --> 00:25:56,525
don't have a lot of noise in
the room and we just we're able

489
00:25:56,525 --> 00:25:58,485
to run these long cables.

490
00:25:58,925 --> 00:26:02,445
So we've tested up to
six hundred meters,

491
00:26:02,445 --> 00:26:04,770
but we're recommending
keep your network still be

492
00:26:04,770 --> 00:26:07,490
conservative in your network
design between two devices.

493
00:26:07,490 --> 00:26:11,530
We're recommending two to three
hundred meters depending on what the

494
00:26:12,130 --> 00:26:13,250
cable looks like.

495
00:26:13,250 --> 00:26:15,730
Move your mic for me
just a little bit.

496
00:26:15,730 --> 00:26:16,770
I don't know if that's just me,

497
00:26:16,770 --> 00:26:19,785
but yours is kinda you
can't drop my voice.

498
00:26:19,785 --> 00:26:20,825
Oh.

499
00:26:20,825 --> 00:26:22,985
Can you guys give me a thumbs
up if everybody else hears that

500
00:26:22,985 --> 00:26:25,505
or if that's just my connection?

501
00:26:25,545 --> 00:26:29,185
Okay. Try and, like, move
your computer up and down.

502
00:26:30,985 --> 00:26:31,985
Yep.

503
00:26:33,890 --> 00:26:35,890
We got row robot, Andy.

504
00:26:35,890 --> 00:26:37,250
Still robot?

505
00:26:37,250 --> 00:26:39,970
Still robot. Just
a little robot.

506
00:26:39,970 --> 00:26:40,850
Okay. How about that?

507
00:26:40,850 --> 00:26:45,570
Could just use I could just use
my mic on my on my on camera then.

508
00:26:45,570 --> 00:26:47,505
So it sounded how's
that? Is that better?

509
00:26:47,505 --> 00:26:48,465
Yes. All good.

510
00:26:48,465 --> 00:26:50,545
Great. That's weird. Okay.

511
00:26:50,545 --> 00:26:53,585
Let me go so let me rephrase
the long cable run thing.

512
00:26:53,585 --> 00:26:54,825
So

513
00:26:55,505 --> 00:26:57,905
while we've successfully tested
up to six hundred meters,

514
00:26:57,905 --> 00:27:00,065
that's not the total
network length, mind you.

515
00:27:00,065 --> 00:27:01,865
That's just between two devices.

516
00:27:01,870 --> 00:27:06,670
We're still derating what
our we're still derating what

517
00:27:06,670 --> 00:27:08,190
our recommendations are.

518
00:27:08,190 --> 00:27:12,150
We think playing it safe is
probably a better option.

519
00:27:12,430 --> 00:27:14,905
Two two to three hundred
meters peer to peer.

520
00:27:14,905 --> 00:27:16,185
I mean, in a VAV network,

521
00:27:16,185 --> 00:27:18,985
you're not gonna find very many
VAV networks where it's three

522
00:27:18,985 --> 00:27:21,785
hundred meters
between two VAV boxes.

523
00:27:21,785 --> 00:27:22,585
But who knows?

524
00:27:22,585 --> 00:27:25,465
Maybe you will or maybe you
wanna extend into a, you know,

525
00:27:25,465 --> 00:27:28,210
another building
or what have you.

526
00:27:28,210 --> 00:27:31,730
So long cable runs, it's a
bit of a controversial topic.

527
00:27:31,730 --> 00:27:34,450
We've yet to see one
kilometer in our own testing.

528
00:27:34,450 --> 00:27:36,730
We've seen six hundred meters,

529
00:27:37,170 --> 00:27:40,570
but we still think it's safer to
recommend two to three hundred meters.

530
00:27:42,875 --> 00:27:45,195
Truly, one of the
benefits though,

531
00:27:45,195 --> 00:27:48,555
t one l auto
negotiating polarity, simple wiring.

532
00:27:48,555 --> 00:27:52,915
Somebody made a comment I saw
that popped up, regarding,

533
00:27:53,435 --> 00:27:59,160
you know, some long networks
were twisted or or the t one l

534
00:28:00,160 --> 00:28:02,800
transceivers that we use
are auto negotiating.

535
00:28:02,800 --> 00:28:05,680
So you can actually flip
the polarity and it'll and it'll

536
00:28:05,680 --> 00:28:07,360
still communicate.

537
00:28:07,360 --> 00:28:08,400
So that'll be a nice thing.

538
00:28:08,400 --> 00:28:10,975
So for all your electricians
out there that, you know,

539
00:28:10,975 --> 00:28:14,015
have the fifty percent
chance of getting it wrong,

540
00:28:14,015 --> 00:28:15,375
when they wire it up,

541
00:28:15,375 --> 00:28:18,615
it's not so much of an issue
anymore with the t one l.

542
00:28:19,375 --> 00:28:22,655
Full Internet compatibility
at the at the MAC layer,

543
00:28:22,655 --> 00:28:24,495
so that means you get all the
benefits that you'd normally

544
00:28:24,495 --> 00:28:28,070
get out of a standard
Ethernet controller IP.

545
00:28:28,270 --> 00:28:29,230
Backward integration,

546
00:28:29,230 --> 00:28:33,670
you can reuse the existing MSTP
cabling or long cabling if it will.

547
00:28:34,430 --> 00:28:36,990
So we're getting ten megabits
per second up to ten megabits

548
00:28:36,990 --> 00:28:40,095
per second, meaning you can
host graphics on the controller.

549
00:28:40,095 --> 00:28:44,295
You get quicker firmware upgrades
and better network performance.

550
00:28:46,175 --> 00:28:47,495
And another,

551
00:28:48,175 --> 00:28:51,215
result of this is also it's actually
better for harsh environments.

552
00:28:51,215 --> 00:28:53,700
T one l has better
noise immunity as well.

553
00:28:53,700 --> 00:28:56,180
So we've we don't have the same
grounding issues that we would

554
00:28:56,180 --> 00:28:58,700
have back in the MSTP days.

555
00:28:58,820 --> 00:29:00,820
So it's kinda like you're
getting your having your cake

556
00:29:00,820 --> 00:29:02,180
and eating it too.

557
00:29:02,180 --> 00:29:03,340
Now

558
00:29:04,420 --> 00:29:07,380
the topology, these are all
point to point connection.

559
00:29:07,380 --> 00:29:09,845
No branches, no t's, no stars.

560
00:29:09,845 --> 00:29:12,485
T one l does not
support, multidrop.

561
00:29:12,485 --> 00:29:14,605
You cannot star the network.

562
00:29:14,645 --> 00:29:17,845
You have to do a site survey.

563
00:29:17,845 --> 00:29:20,405
If you're gonna be quoting
this on your job, go out there,

564
00:29:20,405 --> 00:29:23,480
look at the wire, make sure
you understand what that wiring is.

565
00:29:23,480 --> 00:29:27,560
And if there are stars that you
can find them and take them out

566
00:29:27,560 --> 00:29:28,760
and resolve them.

567
00:29:28,760 --> 00:29:32,080
So it's very important to know,

568
00:29:32,920 --> 00:29:36,600
what that wiring looks like
before you deploy the site.

569
00:29:36,600 --> 00:29:39,440
Okay? Before you're, committed.

570
00:29:41,215 --> 00:29:43,775
It does require a
media converter,

571
00:29:43,775 --> 00:29:45,615
so we've given you
the CON t one l.

572
00:29:45,615 --> 00:29:49,135
So that'll be required to
bring that VAV network onto a

573
00:29:49,135 --> 00:29:51,175
standard Ethernet network.

574
00:29:51,295 --> 00:29:54,250
We're supporting up to sixty
four devices per trunk.

575
00:29:54,250 --> 00:29:57,450
So if you were to take an
existing standard Delta MSTP

576
00:29:57,450 --> 00:30:00,730
truck, a large one, we will
support up to sixty four

577
00:30:00,730 --> 00:30:03,250
devices in that trunk.

578
00:30:04,730 --> 00:30:08,130
It's important to take pass
through into consideration

579
00:30:08,205 --> 00:30:10,845
when you're when you're looking
at your maximum distance as well.

580
00:30:10,845 --> 00:30:14,765
Remember we said, two to
three hundred meters is recommended.

581
00:30:14,765 --> 00:30:18,085
It'll break down, we think,
after six hundred meters.

582
00:30:18,365 --> 00:30:20,285
When you have a pass through,

583
00:30:20,285 --> 00:30:22,725
if you have a device
that drops offline,

584
00:30:22,790 --> 00:30:24,470
the pass through closes,

585
00:30:24,470 --> 00:30:26,150
that signal is no
longer being rebuilt.

586
00:30:26,150 --> 00:30:28,870
So you have to take that into
consideration for the total

587
00:30:28,870 --> 00:30:31,070
overall network length.

588
00:30:31,350 --> 00:30:34,390
And we also have to take into
consideration how many devices

589
00:30:34,390 --> 00:30:35,590
in a row fail.

590
00:30:35,590 --> 00:30:39,625
The one thing that does
impact t one l stability is

591
00:30:39,625 --> 00:30:41,705
your network impedance.

592
00:30:41,705 --> 00:30:44,425
And we find that once this
is getting a little techy.

593
00:30:44,425 --> 00:30:48,425
Once we start exceeding, I
think it's around fifty homes

594
00:30:48,425 --> 00:30:50,505
total network impedance,
it's either fifty or hundred.

595
00:30:50,505 --> 00:30:51,905
I have to look that up.

596
00:30:52,430 --> 00:30:56,110
The network actually
will not slowly degrade.

597
00:30:56,110 --> 00:30:58,550
It'll just stop working.

598
00:30:59,390 --> 00:31:01,310
So even with the
pass through devices,

599
00:31:01,310 --> 00:31:04,110
plan ahead to make sure that if
you're gonna have devices that

600
00:31:04,110 --> 00:31:05,235
are dropping offline,

601
00:31:05,235 --> 00:31:07,475
that you know how many devices
in a row that you can have.

602
00:31:07,475 --> 00:31:10,275
We we would typically recommend
a maximum with three or four

603
00:31:10,275 --> 00:31:13,715
devices that could fail in a
row sequentially before the

604
00:31:13,715 --> 00:31:15,435
network starts to break down.

605
00:31:17,250 --> 00:31:18,130
And as I said,

606
00:31:18,130 --> 00:31:20,930
the testing has shown up to six
hundred meter total distance,

607
00:31:20,930 --> 00:31:24,970
peer to peer, but we're recommending
two to three hundred max.

608
00:31:29,250 --> 00:31:32,425
These are the different types
of wire that we've worked with.

609
00:31:32,425 --> 00:31:35,385
So we've actually worked with
Windy City Windy City and

610
00:31:35,385 --> 00:31:39,225
Faster Cable as well that have
kindly provided us cabling

611
00:31:39,225 --> 00:31:43,145
to test on various different
gauges and network and cable

612
00:31:43,145 --> 00:31:46,225
types that we use in
our internal testing.

613
00:31:46,460 --> 00:31:50,780
So we've tested on, you
know, standard echelon spec,

614
00:31:50,780 --> 00:31:55,340
generic shielded, MSTP cable,
non shielded comm wires.

615
00:31:55,340 --> 00:31:57,900
These are all the different
types of wire that we've,

616
00:31:57,900 --> 00:32:01,535
tested on with varying
different results.

617
00:32:01,535 --> 00:32:05,295
These are published on our,
install guide for t one l,

618
00:32:05,295 --> 00:32:08,255
and that's gonna be a living
document that we will continue

619
00:32:08,255 --> 00:32:10,735
to update as we get
more information,

620
00:32:10,735 --> 00:32:12,375
moving into the future.

621
00:32:17,720 --> 00:32:21,240
So the big push,
like I mentioned to summarize,

622
00:32:21,240 --> 00:32:25,080
is we wanna see t one l
being used to secure those

623
00:32:25,080 --> 00:32:28,720
legacy network runs without
having to replace all that cable.

624
00:32:28,735 --> 00:32:32,015
And it'll allow you to protect
your building with BACnet SC,

625
00:32:32,015 --> 00:32:36,415
a completely encrypted network right
down to the terminal box level.

626
00:32:36,415 --> 00:32:38,695
It's gonna give you IoT

627
00:32:39,455 --> 00:32:42,695
capability right at that
infrastructure as well.

628
00:32:42,735 --> 00:32:47,070
And your your Red five VAV
now access a BACnet secure

629
00:32:47,070 --> 00:32:50,110
connect node, and each one of
those devices can be a node,

630
00:32:50,110 --> 00:32:53,110
you can have a completely
encrypted network.

631
00:32:55,070 --> 00:32:58,335
So some people have asked
me at at conferences

632
00:32:58,335 --> 00:33:00,095
or when I see them
in person by the way,

633
00:33:00,095 --> 00:33:01,535
I love seeing you
guys in person.

634
00:33:01,535 --> 00:33:03,055
So whenever we're at
a conference together,

635
00:33:03,055 --> 00:33:06,095
please feel free to come up
and chat with me and talk shop.

636
00:33:06,095 --> 00:33:07,735
I love it when we do that.

637
00:33:08,430 --> 00:33:10,910
But one of the questions
that came up is, well,

638
00:33:10,910 --> 00:33:13,150
you guys have come up
with this t one l device.

639
00:33:13,150 --> 00:33:15,310
Why would you bother, you know,

640
00:33:15,310 --> 00:33:18,950
coming out with a Red five
field MSTP controller?

641
00:33:18,990 --> 00:33:20,350
And as I mentioned previously,

642
00:33:20,350 --> 00:33:22,590
there's still a need
for MSTP out there.

643
00:33:22,590 --> 00:33:23,990
We still

644
00:33:24,615 --> 00:33:28,815
still I think approximately
seventy percent of

645
00:33:28,855 --> 00:33:33,055
all our, VAV controllers
are still MSTP that we sell,

646
00:33:33,495 --> 00:33:34,935
slowly going down.

647
00:33:34,935 --> 00:33:37,015
The the Ethernet,

648
00:33:37,015 --> 00:33:39,740
Red five VAV controller
is starting to overtake that,

649
00:33:39,740 --> 00:33:43,100
but we still see a significant
number of MSTP devices out there.

650
00:33:43,100 --> 00:33:47,020
So where I would use
MSTP is, obviously,

651
00:33:47,020 --> 00:33:49,820
if we have to reuse an
existing MSTP infrastructure.

652
00:33:49,820 --> 00:33:52,780
So if you're if you're doing
a retrofit of a Delta site,

653
00:33:52,780 --> 00:33:54,575
maybe a third party site,

654
00:33:54,575 --> 00:33:57,615
but maybe you cannot
do a full MSTP cutover.

655
00:33:57,615 --> 00:34:01,455
Maybe you have to phase that
cutover in and or maybe there's

656
00:34:01,455 --> 00:34:04,655
third party by sitting on that
network that cannot be swapped out.

657
00:34:04,655 --> 00:34:05,375
That's the case.

658
00:34:05,375 --> 00:34:08,870
You may wanna use MSTP just
to keep that network going and

659
00:34:08,870 --> 00:34:10,390
you'll be fine going
into the future.

660
00:34:10,390 --> 00:34:13,590
Like I said, the the field
may be an MSTP controller,

661
00:34:13,590 --> 00:34:16,790
but it's still got the power
under the hood that it can grow

662
00:34:16,790 --> 00:34:18,750
with the needs of your building.

663
00:34:20,805 --> 00:34:23,845
Another thing is it it might
be a cost sensitive thing too.

664
00:34:23,845 --> 00:34:26,005
You know, we're looking at
maybe a premium of a dollar

665
00:34:26,005 --> 00:34:28,245
about, I don't know, twenty
dollars per controller,

666
00:34:28,245 --> 00:34:31,125
the difference between MSTP
or maybe it's a little less,

667
00:34:31,125 --> 00:34:34,245
fifteen to twenty dollars
between MSTP and the t one l

668
00:34:34,245 --> 00:34:38,360
controller or the Red five
Edge Ethernet controller.

669
00:34:38,560 --> 00:34:40,000
But, I mean, that adds up.

670
00:34:40,000 --> 00:34:42,200
So if it's a costing

671
00:34:44,640 --> 00:34:46,480
and lower bandwidth
is acceptable,

672
00:34:46,480 --> 00:34:50,775
then that's a perfect a perfect
use case for MSTP controllers.

673
00:34:50,775 --> 00:34:52,375
So they're still out there.

674
00:34:52,375 --> 00:34:53,815
They're still doing their thing,

675
00:34:53,815 --> 00:34:57,175
and I don't think MSTP is
going away anytime soon.

676
00:34:57,175 --> 00:34:59,335
I would like to see it go,
but I don't think it is,

677
00:34:59,335 --> 00:35:00,695
if I'm being honest.

678
00:35:00,695 --> 00:35:02,535
So where do you wanna use
Red five two point zero?

679
00:35:02,535 --> 00:35:03,375
Well,

680
00:35:04,180 --> 00:35:07,300
again, we're using existing
infrastructure for sure.

681
00:35:07,300 --> 00:35:11,500
That's its number one,
it it's number one push.

682
00:35:11,780 --> 00:35:14,420
And you're gonna use it in a
situation where you can cut

683
00:35:14,420 --> 00:35:16,820
off, cut over full MSTP network.

684
00:35:16,820 --> 00:35:20,315
Meaning, you're gonna take out all
the MSTP devices and replace them

685
00:35:20,315 --> 00:35:22,515
all with t one l.

686
00:35:22,955 --> 00:35:25,915
It's used when you require
a modernization of services

687
00:35:25,915 --> 00:35:27,915
available on that
infrastructure.

688
00:35:27,915 --> 00:35:31,915
Meaning, you can now get higher
speed and more services available

689
00:35:31,915 --> 00:35:34,435
without having to replace
all infrastructure.

690
00:35:35,020 --> 00:35:37,660
You use it when you need
to have an encrypted secure

691
00:35:37,660 --> 00:35:39,900
network via back that SC.

692
00:35:39,900 --> 00:35:43,820
Use it if you wanna add IoT
capability to that network and

693
00:35:43,820 --> 00:35:47,940
any situation that you wanna take
advantage of ten megabits per second.

694
00:35:48,485 --> 00:35:52,325
That's really the difference
of where you'd use MFTP versus,

695
00:35:52,325 --> 00:35:54,045
t one l.

696
00:35:58,405 --> 00:36:01,325
So what's next? What's
coming down the line?

697
00:36:01,690 --> 00:36:04,250
So who here, give
me a thumbs up,

698
00:36:04,250 --> 00:36:05,970
has heard of

699
00:36:06,570 --> 00:36:08,290
IntelliZone?

700
00:36:08,810 --> 00:36:11,650
Give me a thumbs up if
you've heard of IntelliZone.

701
00:36:12,490 --> 00:36:14,850
Lots of people have heard okay.

702
00:36:16,105 --> 00:36:19,625
So over the last
three, four years,

703
00:36:19,625 --> 00:36:23,625
we've introduced a RED
five IO controller that

704
00:36:23,625 --> 00:36:27,065
replaces our legacy DAC and DSC.

705
00:36:27,065 --> 00:36:29,705
We've released a RED five VAV

706
00:36:29,705 --> 00:36:31,910
controller that'll
start replacing our

707
00:36:31,910 --> 00:36:36,990
legacy DVC and EZone
VAV controllers.

708
00:36:37,350 --> 00:36:41,510
The gap that we have is
what are we gonna do with

709
00:36:41,510 --> 00:36:45,510
unitary controllers,
meaning our IntelliZone fan

710
00:36:45,510 --> 00:36:48,965
coil controller and
heat pump controller.

711
00:36:50,045 --> 00:36:53,165
And that's the brand new
program that I'm working on

712
00:36:53,165 --> 00:36:57,445
right now with the team,
the Red five unitary.

713
00:36:58,125 --> 00:37:00,850
We're gonna do t
one l IP Ethernet

714
00:37:00,850 --> 00:37:02,770
just like we do with the VAV.

715
00:37:02,770 --> 00:37:04,210
We're gonna do MSTP.

716
00:37:04,210 --> 00:37:07,730
It'll support back to
secure connect over IP.

717
00:37:07,730 --> 00:37:11,170
So very, very similar to what
we did with the VAV controller.

718
00:37:11,170 --> 00:37:13,250
We're gonna do with the RED
five unitary controller.

719
00:37:13,250 --> 00:37:15,370
So we're gonna do a
couple of variants.

720
00:37:15,865 --> 00:37:19,265
We're gonna do a
application specific

721
00:37:19,305 --> 00:37:21,145
fan coil controller,

722
00:37:21,145 --> 00:37:24,505
and they'll we'll we'll do
that in two different models.

723
00:37:24,505 --> 00:37:27,065
One that has three speed fan,

724
00:37:27,065 --> 00:37:29,630
meaning it'll have
onboard line voltage

725
00:37:29,630 --> 00:37:32,870
relays, and we'll also
do a model with analog

726
00:37:32,910 --> 00:37:35,990
fan control for, like,
ECM motors as well.

727
00:37:38,830 --> 00:37:41,765
Same deal with supporting
embedded graphics,

728
00:37:41,765 --> 00:37:43,285
PG Python.

729
00:37:43,285 --> 00:37:46,405
We're we're gonna have European
centric products as well where

730
00:37:46,405 --> 00:37:49,125
we have, line voltage power.

731
00:37:49,125 --> 00:37:53,005
We'll also have the twenty
four volt AC and DC models.

732
00:37:54,500 --> 00:37:58,540
So this is all this is what
we're we're going on, this year.

733
00:38:01,060 --> 00:38:03,700
Target timeline, late
twenty twenty six.

734
00:38:03,700 --> 00:38:06,460
That's pretty ambitious,
but it's still our target.

735
00:38:08,365 --> 00:38:11,725
But we will probably see something
in early twenty twenty seven.

736
00:38:11,725 --> 00:38:14,925
And what's important for us
here is is that this product is

737
00:38:14,925 --> 00:38:17,645
designed for the application,
not just the spec sheet.

738
00:38:17,645 --> 00:38:20,445
We're not just trying to do a
bare minimum to get products

739
00:38:20,445 --> 00:38:23,400
out the door and and
into specifications.

740
00:38:23,400 --> 00:38:26,440
We wanna make sure that
we're doing a product that's that's

741
00:38:26,440 --> 00:38:29,160
useful that meets
your guys' needs.

742
00:38:29,160 --> 00:38:31,160
So these are our brand
new renderings of it.

743
00:38:31,160 --> 00:38:34,240
It might differ a little bit
from what this looks like.

744
00:38:34,865 --> 00:38:38,585
These guys are gonna have
the onboard, removable,

745
00:38:39,265 --> 00:38:42,705
connector block, terminal blocks
just like the VAV controller does.

746
00:38:42,705 --> 00:38:46,545
And, again, it'll come in with a
dual Ethernet with pass through,

747
00:38:46,545 --> 00:38:50,505
a dual t one l with pass
through, and an MSTP model.

748
00:38:50,570 --> 00:38:55,010
So keep an eye out for that
in the next in the next year.

749
00:38:56,890 --> 00:39:00,050
Now you guys can click
these links here.

750
00:39:02,250 --> 00:39:03,930
If you wanna click any
one of these links,

751
00:39:03,930 --> 00:39:06,770
they should take
you to these pages.

752
00:39:08,145 --> 00:39:10,305
If you wanna learn more
about the red five family,

753
00:39:10,305 --> 00:39:13,305
red five modules,
the CON t one l,

754
00:39:13,745 --> 00:39:16,145
or if you just wanna read off
over what the whole red five

755
00:39:16,145 --> 00:39:19,720
family, make sure you can
you can click these links.

756
00:39:19,720 --> 00:39:21,160
So maybe you wanna
try it out right now.

757
00:39:21,160 --> 00:39:25,360
I'll give you a second to do that
before we go into the q and a.

758
00:39:29,160 --> 00:39:30,400
Okay.

759
00:39:31,805 --> 00:39:32,605
Has anyone tried?

760
00:39:32,605 --> 00:39:34,685
Give me a thumbs up
if you're able to hit,

761
00:39:34,685 --> 00:39:36,285
try one of these links.

762
00:39:36,285 --> 00:39:38,725
Good? I get a thumbs up. Good.

763
00:39:38,765 --> 00:39:41,005
Okay. So let's do q and a.

764
00:39:41,005 --> 00:39:44,165
We've got roughly
eighteen minutes left.

765
00:39:44,340 --> 00:39:47,940
It's actually a miracle I
finished this on time Perfect.

766
00:39:47,940 --> 00:39:49,140
Within two minutes.

767
00:39:49,140 --> 00:39:51,540
So Perfect.

768
00:39:51,540 --> 00:39:51,860
Okay.

769
00:39:51,860 --> 00:39:53,220
So let's then I'll just yeah.

770
00:39:53,220 --> 00:39:56,180
I can I either you just read
them going straight down,

771
00:39:56,180 --> 00:39:57,220
or I can read them to you,

772
00:39:57,220 --> 00:39:59,025
whatever you Let
me look at the top?

773
00:39:59,025 --> 00:40:03,545
Let me see. How many do we
get here? Quite a few. Okay.

774
00:40:04,305 --> 00:40:05,625
So

775
00:40:06,865 --> 00:40:10,785
Alex, Ramke said, for the
red five VABs with t one

776
00:40:10,785 --> 00:40:14,160
l with being Ethernet, will we
still achieve the same speeds

777
00:40:14,160 --> 00:40:16,880
we do typically
with Ethernet cable?

778
00:40:16,880 --> 00:40:19,520
Do we have to wire length
limitations with t one l VABs

779
00:40:19,520 --> 00:40:20,640
like we do with Ethernet,

780
00:40:20,640 --> 00:40:22,720
or do we have improved
installation lengths?

781
00:40:22,720 --> 00:40:24,000
That is an excellent question.

782
00:40:24,000 --> 00:40:27,160
I hope that you hopefully, my
webinar answered that question,

783
00:40:27,225 --> 00:40:29,265
but I'll reiterate it.

784
00:40:30,265 --> 00:40:34,665
We so t one l ten base t
one l is ten megabits per

785
00:40:34,665 --> 00:40:38,025
second rather than a
hundred megabits per second.

786
00:40:38,025 --> 00:40:39,785
So it is it's slightly slower.

787
00:40:39,785 --> 00:40:43,105
It's it's basically the
same speed as our old DSCs

788
00:40:43,590 --> 00:40:44,390
would do.

789
00:40:44,390 --> 00:40:46,950
Ten megabits per
second overbalanced,

790
00:40:46,950 --> 00:40:48,790
twisted pair of cabling.

791
00:40:48,790 --> 00:40:51,430
Do we have the same wire
length limitations? No.

792
00:40:51,430 --> 00:40:55,710
T one l wire length is
longer than standard,

793
00:40:55,910 --> 00:40:57,590
Ethernet. What is
standard Ethernet?

794
00:40:57,590 --> 00:40:58,910
It's three hundred feet.

795
00:40:58,915 --> 00:41:00,195
It's three hundred feet.

796
00:41:00,195 --> 00:41:03,715
Whereas, we can go
up to we've tested up

797
00:41:03,715 --> 00:41:05,515
to six hundred meters.

798
00:41:09,475 --> 00:41:10,955
Andrew Little,

799
00:41:11,790 --> 00:41:15,150
is the DVC formally end of life?

800
00:41:15,150 --> 00:41:18,350
So the DVC three twenty two e,

801
00:41:18,350 --> 00:41:20,670
the Ethernet DVC
controllers, Andrew,

802
00:41:20,670 --> 00:41:22,910
they're all end of life already.

803
00:41:22,910 --> 00:41:26,190
We will be sending out an
announcement that'll give you

804
00:41:26,190 --> 00:41:29,685
the last time buy, last time
ship for DVC products that'll

805
00:41:29,685 --> 00:41:31,605
be starting in
twenty twenty seven.

806
00:41:31,605 --> 00:41:33,285
So we will be we yes.

807
00:41:33,285 --> 00:41:37,485
We will be phasing those
controllers out over the next year.

808
00:41:37,605 --> 00:41:41,685
This time next year will probably
be around the the last time ship.

809
00:41:41,685 --> 00:41:45,300
So q two twenty twenty seven
will be the end of of the DVC

810
00:41:45,300 --> 00:41:49,580
twenty two, DVC product
line, MSTP and Ethernet.

811
00:41:57,185 --> 00:41:58,585
Actually

812
00:42:00,385 --> 00:42:00,785
okay.

813
00:42:00,785 --> 00:42:03,465
Let's see. I gotta find
another question here.

814
00:42:05,025 --> 00:42:07,585
Probably the next one is
that need to add the stack

815
00:42:07,585 --> 00:42:11,440
configuration tab with the air
balance tab and configuration.

816
00:42:11,440 --> 00:42:12,480
Is that a Oh, yeah.

817
00:42:12,480 --> 00:42:16,400
You know, that's a good that's a good
that's more of a statement than a question.

818
00:42:16,400 --> 00:42:16,720
Yeah.

819
00:42:16,720 --> 00:42:20,880
We we're gonna we are
working on our new

820
00:42:20,880 --> 00:42:24,035
embedded graphics for
the VAV controllers.

821
00:42:24,035 --> 00:42:28,035
Actually, all, v four IP
controllers will be supporting,

822
00:42:28,035 --> 00:42:31,195
embedded graphics, this summer.

823
00:42:31,395 --> 00:42:33,155
We're already looking
at the prototypes.

824
00:42:33,155 --> 00:42:36,635
We're about to go to beta
probably the next month and a bit.

825
00:42:37,490 --> 00:42:40,370
So that gives us the
opportunity to build proper

826
00:42:40,370 --> 00:42:44,810
configuration and
balancing pages as well.

827
00:42:46,850 --> 00:42:50,135
Do red do red five
Ethernet devices

828
00:42:50,135 --> 00:42:53,095
support eight zero eight
zero two point one f?

829
00:42:53,095 --> 00:42:54,935
So that that's a oh my god.

830
00:42:54,935 --> 00:42:57,295
That's gonna take
another webinar.

831
00:42:58,295 --> 00:43:00,615
The we're we are
working on that,

832
00:43:00,615 --> 00:43:01,815
and I'm gonna leave it at that.

833
00:43:01,815 --> 00:43:03,375
We are working on it.

834
00:43:03,720 --> 00:43:04,440
K.

835
00:43:04,440 --> 00:43:08,480
IPV controllers have special
requirements for switches?

836
00:43:09,240 --> 00:43:10,680
No. They don't.

837
00:43:10,680 --> 00:43:14,120
We so Delta v four controllers,

838
00:43:14,120 --> 00:43:18,080
IP based v controllers are a
hundred megabits per second

839
00:43:19,085 --> 00:43:19,965
max.

840
00:43:19,965 --> 00:43:24,445
So, basically, any
standard IT switch will

841
00:43:24,445 --> 00:43:25,565
will be able to you know,

842
00:43:25,565 --> 00:43:28,805
you can have those net
controllers on that network.

843
00:43:29,005 --> 00:43:32,760
T one l, the only special
requirement you need for a t

844
00:43:32,760 --> 00:43:37,720
one l controller is to add the con
t one l or other media converter.

845
00:43:37,720 --> 00:43:41,400
So you need to convert the t
one l to standard Ethernet or

846
00:43:41,400 --> 00:43:42,720
IP.

847
00:43:43,320 --> 00:43:44,145
K.

848
00:43:44,145 --> 00:43:47,345
Next one down is probably
the when are we gonna get the

849
00:43:47,345 --> 00:43:51,425
service tool to connect the
RedPipe field controllers?

850
00:43:51,425 --> 00:43:54,705
It's funny how we have
this question come up in a

851
00:43:54,705 --> 00:43:58,785
DV webinar, and we're
asking about a completely

852
00:43:58,785 --> 00:44:00,425
unrelated product.

853
00:44:00,910 --> 00:44:02,870
You're gonna get it

854
00:44:03,550 --> 00:44:04,830
imminently.

855
00:44:04,830 --> 00:44:08,670
Soonest. Tool. Yeah. The
service tool is complete.

856
00:44:08,670 --> 00:44:11,870
We're just right now wrapping
up the paperwork to send out

857
00:44:11,870 --> 00:44:14,550
the release notification on it.

858
00:44:15,165 --> 00:44:16,605
Is there any concern
You know what?

859
00:44:16,605 --> 00:44:17,325
Hold on a second.

860
00:44:17,325 --> 00:44:19,965
You guys asked a question about an
unrelated product in the webinar.

861
00:44:19,965 --> 00:44:21,965
I just told you
you're getting it.

862
00:44:21,965 --> 00:44:24,925
Can I at least get a little
bit of hoopla about it?

863
00:44:24,925 --> 00:44:26,685
There it is. Look at them all.

864
00:44:26,685 --> 00:44:27,885
Look at the hearts.

865
00:44:27,885 --> 00:44:30,180
I know. It's about
bloody time, isn't it?

866
00:44:30,180 --> 00:44:32,500
I know. I know.
That's why. Too angry.

867
00:44:32,500 --> 00:44:34,740
I'm surprised I don't see
any angry faces in there.

868
00:44:34,740 --> 00:44:36,460
I'd expect more

869
00:44:38,420 --> 00:44:41,580
Alan, do you actually have
something to say on that one?

870
00:44:41,860 --> 00:44:43,980
No. He didn't. Okay. Okay.

871
00:44:44,475 --> 00:44:48,075
Next one's probably, is there
a concern with having all the

872
00:44:48,075 --> 00:44:51,595
power on the field
VAV running on MSTP?

873
00:44:51,595 --> 00:44:54,995
Will the network communication
suffer, etcetera?

874
00:44:55,435 --> 00:44:58,235
******* having all the
power running MSTP.

875
00:44:58,235 --> 00:44:59,635
Well, network communication.

876
00:44:59,880 --> 00:45:00,520
Yeah.

877
00:45:00,520 --> 00:45:04,720
Do you mean by the actual I'm not
sure I understand the question.

878
00:45:06,600 --> 00:45:10,560
Like, do we mean how we're powering
the controllers or the actual

879
00:45:10,600 --> 00:45:13,065
power of the
processor and memory?

880
00:45:13,065 --> 00:45:15,305
If it's the latter, no.

881
00:45:15,305 --> 00:45:18,345
Because we I mean,
MSTP is still MSTP,

882
00:45:18,345 --> 00:45:23,025
and you still have to follow
our guidelines on how you would

883
00:45:23,865 --> 00:45:25,465
deploy an MSTP network.

884
00:45:25,465 --> 00:45:29,450
You know, you wanna restrict the
amount of data exchange it can do.

885
00:45:29,450 --> 00:45:32,730
I mean, they they have more
power than the DDC controller,

886
00:45:32,730 --> 00:45:35,530
obviously, hundred hundreds
of times more power,

887
00:45:35,530 --> 00:45:37,450
but MSTP is still MSTP.

888
00:45:37,450 --> 00:45:40,410
You've only got as much
bandwidth as it can handle.

889
00:45:40,410 --> 00:45:45,675
You know, a highway can handle much
more traffic than a side road can.

890
00:45:45,675 --> 00:45:49,995
MSTP is your side road compared
to a interstate freeway.

891
00:45:49,995 --> 00:45:53,675
So you're still limited to
the bandwidth with MSTP,

892
00:45:53,675 --> 00:45:56,930
but that doesn't really
factor into what what the

893
00:45:56,930 --> 00:45:59,890
controller power can do
unless you, you know,

894
00:45:59,890 --> 00:46:02,970
you're overdoing
your MSTP network.

895
00:46:04,370 --> 00:46:08,370
Will there be an actuator
list version of the red five

896
00:46:08,370 --> 00:46:12,495
VAV controller for instances that
require specialized actuators?

897
00:46:12,495 --> 00:46:14,455
That's a great question.

898
00:46:14,655 --> 00:46:16,535
Thank you for that, Kelly.

899
00:46:16,655 --> 00:46:20,575
The answer is yes,
but not quite yet.

900
00:46:20,575 --> 00:46:22,495
We have to work on a
few other things first.

901
00:46:22,495 --> 00:46:26,210
But, yes, the plan is to
also release a red five

902
00:46:26,210 --> 00:46:29,210
controller that can have
an external actuator.

903
00:46:29,250 --> 00:46:32,210
One of the the perks that we're
getting out of building the

904
00:46:32,210 --> 00:46:35,170
unitary controller is
everything is gonna start

905
00:46:35,170 --> 00:46:37,730
converging on similar
technology, the same

906
00:46:37,730 --> 00:46:41,225
architecture from, you know,
controller architecture.

907
00:46:41,225 --> 00:46:45,465
I mean, the actual, circuits and
processing power and all that.

908
00:46:45,465 --> 00:46:48,665
So once we have that
platform in place,

909
00:46:48,665 --> 00:46:52,425
we can kinda build any sort of
product on top of that platform.

910
00:46:52,425 --> 00:46:55,585
It allows us to move a lot quicker
because we're not redesigning,

911
00:46:56,240 --> 00:46:58,720
you know, the brains of
the controller every time.

912
00:46:58,720 --> 00:47:02,640
So, yes, it's a huge thing
that I wanna do is a Red five

913
00:47:02,640 --> 00:47:05,280
VAV controller
without an actuator,

914
00:47:05,280 --> 00:47:09,160
but it'll probably be
after the unitary program.

915
00:47:11,275 --> 00:47:13,915
Lawn works also has mixed
wiring, not only daisy chain,

916
00:47:13,915 --> 00:47:14,795
but free topology.

917
00:47:14,795 --> 00:47:17,195
So t one l also
free topology. No.

918
00:47:17,195 --> 00:47:19,035
I hope my webinar
answered that too.

919
00:47:19,035 --> 00:47:22,475
You have to return number
one, you have to re terminate.

920
00:47:22,475 --> 00:47:26,560
So you can't start you
can't have t's or stars or

921
00:47:26,560 --> 00:47:27,600
free topologies.

922
00:47:27,600 --> 00:47:31,240
It is a point to
point connection

923
00:47:31,360 --> 00:47:36,240
that is going through path
through the, the the t one l,

924
00:47:36,240 --> 00:47:39,365
transceivers that we have on the
controller is basically a t one l switch.

925
00:47:39,365 --> 00:47:41,525
Think of it as just
a standard switch.

926
00:47:41,525 --> 00:47:43,685
So the controller is now,

927
00:47:43,685 --> 00:47:46,485
navigating that network traffic.

928
00:47:46,485 --> 00:47:48,645
So, no, you cannot
have mixed wire.

929
00:47:48,645 --> 00:47:50,885
You can't have t's or stars
or anything like that.

930
00:47:50,885 --> 00:47:55,325
The one thing t one
l can do is detect

931
00:47:55,370 --> 00:47:57,170
the polarity.

932
00:48:00,090 --> 00:48:01,130
From network standpoint,

933
00:48:01,130 --> 00:48:04,890
are the two segments downstream
of t one l separate segments?

934
00:48:04,890 --> 00:48:06,570
Does heavy traffic
on one segment,

935
00:48:06,570 --> 00:48:07,770
impede traffic on another?

936
00:48:07,770 --> 00:48:09,485
That's a great question.

937
00:48:09,485 --> 00:48:12,005
So from a networking standpoint,

938
00:48:12,205 --> 00:48:15,805
that network drawing I showed you
let me see if I can find it here.

939
00:48:15,805 --> 00:48:20,085
I'll go back to that
drawing. Where is it?

940
00:48:20,205 --> 00:48:21,285
Right here.

941
00:48:23,870 --> 00:48:26,110
These devices are all
on the same network.

942
00:48:26,110 --> 00:48:29,070
Even on this t I kinda drew
this t one l network kind of in

943
00:48:29,070 --> 00:48:33,070
a funny way just to illustrate the
capabilities of the the con t one l.

944
00:48:33,070 --> 00:48:38,205
But all of these devices
are wired in a fashion

945
00:48:38,205 --> 00:48:41,165
that they're on
the same IP subnet.

946
00:48:41,165 --> 00:48:44,485
So, yes, heavy
traffic could impact,

947
00:48:45,165 --> 00:48:47,485
the entire network on a flat
that's why we're coming up with

948
00:48:47,485 --> 00:48:51,890
new, networking guidelines to
give you guys best practices

949
00:48:51,890 --> 00:48:55,570
for, flat networks, things
like restricting broadcast.

950
00:48:55,570 --> 00:48:59,810
Make sure your BDE controllers or
your BDE objects are set up correctly.

951
00:48:59,810 --> 00:49:02,290
Don't be broadcasting
data for BDEs.

952
00:49:02,290 --> 00:49:04,090
Make sure that you only have

953
00:49:04,545 --> 00:49:06,465
a one to many for transmission,

954
00:49:06,465 --> 00:49:08,785
not a many many to
transmit and receive,

955
00:49:08,785 --> 00:49:12,665
things like that to help
reduce heavy traffic.

956
00:49:14,945 --> 00:49:17,745
Greg has written, can
you write to AVs, BDs,

957
00:49:17,745 --> 00:49:21,240
or MVs or PGs from the
Python environment?

958
00:49:21,240 --> 00:49:23,760
That's a really
good question too.

959
00:49:25,560 --> 00:49:28,240
The answer to that
is yes and no.

960
00:49:28,440 --> 00:49:32,295
Python is not designed
to do control algorithms.

961
00:49:32,295 --> 00:49:35,495
It's not fast enough the way
it interacts with BACnet.

962
00:49:35,495 --> 00:49:39,255
In the future, we are planning on
bringing that capability to the,

963
00:49:39,255 --> 00:49:41,375
to the Python environment.

964
00:49:41,575 --> 00:49:44,615
But there's a lot of technical work
we have to do in order to get there.

965
00:49:44,615 --> 00:49:47,940
So, yes, it can
actually write to an AV.

966
00:49:47,940 --> 00:49:49,620
I I use it for writing, like,

967
00:49:49,620 --> 00:49:53,780
weather data to a CSV
or into AV description

968
00:49:53,780 --> 00:49:56,820
field, but it's
slowly it's slow and

969
00:49:56,820 --> 00:50:00,020
it's not designed to
do control algorithms,

970
00:50:00,020 --> 00:50:01,980
but we would like to get there.

971
00:50:03,115 --> 00:50:06,555
You can't use a cannot
use a PG Python,

972
00:50:06,555 --> 00:50:10,395
a Python program to write
to an external PG either.

973
00:50:10,395 --> 00:50:12,915
Those those PGs are their own

974
00:50:13,755 --> 00:50:16,035
independent units, if you will.

975
00:50:21,850 --> 00:50:25,290
Next one down is about the
expected date for PG Python to

976
00:50:25,290 --> 00:50:29,010
come out or feature Oh, to
come out of a preview feature?

977
00:50:30,075 --> 00:50:32,915
Yeah. If it were up
to me, it'd be now.

978
00:50:33,115 --> 00:50:35,835
But we're still doing we're
what we're doing the reason why

979
00:50:35,835 --> 00:50:39,115
it's still a preview is
we're ensuring that there's

980
00:50:39,115 --> 00:50:43,275
still guardrails on it to make
sure that we understand all the

981
00:50:43,275 --> 00:50:48,130
the the rules and limitations
and boundaries around it.

982
00:50:48,130 --> 00:50:52,090
We also are trying
to develop a library,

983
00:50:52,130 --> 00:50:55,490
from a lot of our beta
testers and internally that so that we

984
00:50:55,490 --> 00:51:00,775
can provide those libraries back to
you guys so that you actually have

985
00:51:02,175 --> 00:51:05,735
proper use cases and useful
information that you can

986
00:51:05,855 --> 00:51:08,015
employ with PG Python.

987
00:51:08,015 --> 00:51:09,095
So

988
00:51:09,510 --> 00:51:10,950
I believe once we have all that,

989
00:51:10,950 --> 00:51:14,150
I still think we're targeting
this summertime to take to

990
00:51:14,150 --> 00:51:16,750
officially have it
in release grade.

991
00:51:17,590 --> 00:51:19,590
But I have to actually
verify that with the firmware

992
00:51:19,590 --> 00:51:21,270
development team.

993
00:51:21,270 --> 00:51:23,270
It's pretty it's getting
pretty mature now,

994
00:51:23,270 --> 00:51:24,670
so we're getting closer.

995
00:51:24,775 --> 00:51:28,175
But it won't be earlier than
summer, put it that way.

996
00:51:31,335 --> 00:51:34,215
Right. Right. A lot of
comments about my robot voice.

997
00:51:34,215 --> 00:51:37,215
I was probably an improvement,
guys, to be honest.

998
00:51:37,975 --> 00:51:39,420
Technician tool.

999
00:51:39,420 --> 00:51:39,820
Yeah.

1000
00:51:39,820 --> 00:51:42,180
I mean, god, you
don't wanna hear my

1001
00:51:42,220 --> 00:51:43,660
weasley voice.

1002
00:51:43,660 --> 00:51:47,100
Any recommendations for
replacing a few VAV MSTP

1003
00:51:47,100 --> 00:51:51,660
devices and then eventually upgrading
the entire subnet to t one l?

1004
00:51:51,660 --> 00:51:53,460
Oh, that's a good one.

1005
00:51:55,115 --> 00:51:57,115
How can I illustrate this? Yes.

1006
00:51:57,115 --> 00:52:00,315
I do have a recommendation for
it. Thanks, Greg. Hey, Greg.

1007
00:52:00,315 --> 00:52:02,595
How are you? I haven't
seen you in a long time.

1008
00:52:04,875 --> 00:52:09,250
What you could do is you
upgrade part of the network

1009
00:52:09,250 --> 00:52:13,370
with t one l, but
then you have to put a

1010
00:52:13,730 --> 00:52:14,770
you would have to put, like,

1011
00:52:14,770 --> 00:52:17,410
a half router in
there to take like,

1012
00:52:17,410 --> 00:52:20,530
you probably have to put a a
plus controller on t one l as

1013
00:52:20,530 --> 00:52:24,125
well that would pick up any
remaining MSTP devices that you

1014
00:52:24,125 --> 00:52:26,045
have that you couldn't cut over.

1015
00:52:26,045 --> 00:52:27,565
So you'd have to
separate the network.

1016
00:52:27,565 --> 00:52:31,405
You do part of the network in
t one l with a plus controller in

1017
00:52:31,405 --> 00:52:34,925
there that maybe picks
up the remaining MSTP.

1018
00:52:34,925 --> 00:52:38,050
Either that or if you have a
way to run the last chunk of

1019
00:52:38,050 --> 00:52:40,210
MSTP devices back to
the home controller,

1020
00:52:40,210 --> 00:52:41,490
you would have to
do that as well.

1021
00:52:41,490 --> 00:52:43,690
We cannot mix and match them.

1022
00:52:44,130 --> 00:52:46,290
You missed one on there
about the technician tool for

1023
00:52:46,290 --> 00:52:48,690
connecting to red
five fields ETP.

1024
00:52:48,690 --> 00:52:49,730
I just answered that.

1025
00:52:49,730 --> 00:52:53,335
So the red the technician tool
is coming out, like, in Oh, yeah.

1026
00:52:53,335 --> 00:52:54,135
Yeah. Yeah. Two weeks.

1027
00:52:54,135 --> 00:52:56,055
Not even. A week. I
I think May seventh.

1028
00:52:56,055 --> 00:52:59,255
We I think we have the
May seventh date for the

1029
00:52:59,255 --> 00:53:00,215
announcement to come out.

1030
00:53:00,215 --> 00:53:02,735
Yep. It's just in
paperwork right now.

1031
00:53:03,975 --> 00:53:07,560
Rob Luke is saying, if
you have an EV manager

1032
00:53:07,560 --> 00:53:12,160
or Red Flag Plus with
MSTP DVCs under it,

1033
00:53:12,520 --> 00:53:14,600
you are changing VEVs
out one at a time.

1034
00:53:14,600 --> 00:53:17,400
Is there a reason you couldn't
temporarily connect the t one

1035
00:53:17,400 --> 00:53:21,005
l, that one to the MSTP bus.

1036
00:53:21,005 --> 00:53:24,245
And then once they are
changed out, move the wire.

1037
00:53:25,325 --> 00:53:27,525
I think that goes back

1038
00:53:29,565 --> 00:53:29,885
yeah.

1039
00:53:29,885 --> 00:53:31,005
I know what Rob's asking.

1040
00:53:31,005 --> 00:53:33,845
He wants kind of t one l and

1041
00:53:34,400 --> 00:53:36,880
MSTP on the same controller
and switch it out.

1042
00:53:36,880 --> 00:53:38,560
We don't have that yet.

1043
00:53:38,560 --> 00:53:41,120
You'd have to do it where
you split the network, Rob.

1044
00:53:41,120 --> 00:53:42,800
Again, you have
to take the MSTP,

1045
00:53:42,800 --> 00:53:44,720
separate that back to net two,

1046
00:53:44,720 --> 00:53:49,235
and then take your cat five out
to a con t one l and then take

1047
00:53:49,235 --> 00:53:51,355
that to your t one l network.

1048
00:53:54,515 --> 00:53:58,275
Jeremy is asking, does it
work over eighteen gauge wire? Yes.

1049
00:53:58,275 --> 00:54:00,635
We've actually tested
over eighteen gauge wire,

1050
00:54:00,960 --> 00:54:06,880
and it seems to not all eighteen
gauge wire is is the same.

1051
00:54:06,880 --> 00:54:11,200
So you do have to do
a you you do have to

1052
00:54:11,200 --> 00:54:14,305
observe the site, take a look
at the quality of the wire,

1053
00:54:14,305 --> 00:54:17,505
the state of the you
know, what state it's in.

1054
00:54:17,505 --> 00:54:19,945
We did a, case study,

1055
00:54:20,065 --> 00:54:23,985
where we wired up our entire network
basically over eighteen gauge.

1056
00:54:23,985 --> 00:54:27,120
But we've had mixed we've
had mixed success on it.

1057
00:54:27,120 --> 00:54:29,680
Some eighteen gauge
wire hasn't worked well.

1058
00:54:29,680 --> 00:54:32,560
Some gate eighteen gauge
wire has worked okay.

1059
00:54:32,560 --> 00:54:38,360
And it comes down to what that
cable impedance is typically.

1060
00:54:39,475 --> 00:54:42,515
We found that the most suitable
wire is actually twenty two

1061
00:54:42,515 --> 00:54:45,675
gauge has given us the best
results in our testing.

1062
00:54:46,515 --> 00:54:50,435
Isaiah Isaiah Blanco says, dZNR
device for boosting network

1063
00:54:50,435 --> 00:54:52,275
length over sixty four devices.

1064
00:54:52,275 --> 00:54:53,115
No.

1065
00:54:53,450 --> 00:54:55,130
That will not work.

1066
00:54:55,130 --> 00:54:58,090
There will no be no device for
boosting the network length

1067
00:54:58,090 --> 00:55:01,330
over sixty four devices
on a t one l network.

1068
00:55:02,730 --> 00:55:06,330
I would say that sixty
four devices is even pushing it.

1069
00:55:06,330 --> 00:55:08,835
We support it, but, I mean,

1070
00:55:08,835 --> 00:55:11,475
that's the maximum that
we support for MSTP.

1071
00:55:11,475 --> 00:55:12,995
That's what we test with.

1072
00:55:12,995 --> 00:55:16,915
So the maximum devices we test our t
one l networks is sixty four devices.

1073
00:55:16,915 --> 00:55:20,155
So that's what we
limit our support to.

1074
00:55:22,770 --> 00:55:24,770
Sixty four device oh,
this is a great question.

1075
00:55:24,770 --> 00:55:28,370
Christopher McLeod asked,
sixty four devices is the max,

1076
00:55:28,370 --> 00:55:30,850
but what is the recommended
number for a run?

1077
00:55:30,850 --> 00:55:34,970
I guess it's gonna that that
question is gonna come down to

1078
00:55:37,045 --> 00:55:41,045
it's gonna have to come down to
that saying your mileage may vary.

1079
00:55:41,045 --> 00:55:42,565
A lot of companies,

1080
00:55:42,565 --> 00:55:46,245
I worked for a company where
they didn't like to have MSTP

1081
00:55:46,245 --> 00:55:48,845
networks over
thirty two devices.

1082
00:55:50,110 --> 00:55:53,150
So they limit no matter what
we said, they said, nope.

1083
00:55:53,150 --> 00:55:57,350
We're never building an MSTP
trunk over six thirty two devices.

1084
00:55:57,790 --> 00:55:59,950
T one l, I would think it's
probably the same thing.

1085
00:55:59,950 --> 00:56:02,830
Your limitation is how long
is the complete network?

1086
00:56:02,830 --> 00:56:04,990
How long is it between devices?

1087
00:56:04,990 --> 00:56:06,150
And

1088
00:56:06,725 --> 00:56:09,485
what kind of quality
is is the wire?

1089
00:56:10,565 --> 00:56:14,245
So I would say if you if
your company likes to play

1090
00:56:14,245 --> 00:56:15,765
conservative, you
could say, well,

1091
00:56:15,765 --> 00:56:18,445
recommended devices is
thirty or thirty two.

1092
00:56:18,980 --> 00:56:23,900
We test with sixty four over
various different wire engages.

1093
00:56:24,740 --> 00:56:27,060
And then John here
actually said same as MSTP.

1094
00:56:27,060 --> 00:56:29,540
Thirty two to forty looks
good for a solid network.

1095
00:56:29,540 --> 00:56:31,580
I'm going with max fifty.

1096
00:56:31,635 --> 00:56:34,435
So it's not an exact science,
but John's playing it sick.

1097
00:56:34,435 --> 00:56:35,635
He's playing it conservative,

1098
00:56:35,635 --> 00:56:38,435
which is which is totally a
good thing to do because it

1099
00:56:38,435 --> 00:56:41,155
costs less money in the
long run when you play it

1100
00:56:41,155 --> 00:56:43,115
conservative rather
than push it.

1101
00:56:43,490 --> 00:56:44,450
Real quick, Andy.

1102
00:56:44,450 --> 00:56:45,490
We are Oh my god.

1103
00:56:45,490 --> 00:56:46,210
There's so many questions.

1104
00:56:46,210 --> 00:56:48,370
On our time. Yeah.
That's okay. No problem.

1105
00:56:48,370 --> 00:56:50,850
So we'll go through and we'll just
continue to answer these questions,

1106
00:56:50,850 --> 00:56:52,930
but I just wanted to let
everybody know again just so

1107
00:56:52,930 --> 00:56:55,090
you are aware this will
all still be recorded,

1108
00:56:55,090 --> 00:56:57,985
and I will compile all these q
and a's and send it out to you.

1109
00:56:57,985 --> 00:57:00,625
So if you have to run and your
question has not been answered,

1110
00:57:00,625 --> 00:57:02,065
we will still keep
going through them.

1111
00:57:02,065 --> 00:57:04,225
So keep it moving,
Andy. We got this.

1112
00:57:04,225 --> 00:57:06,385
Okay. Yeah. Anybody who
wants keep up, go ahead.

1113
00:57:06,385 --> 00:57:09,120
I I understand completely.
We're at eleven.

1114
00:57:09,120 --> 00:57:12,120
So there are a couple
of questions here

1115
00:57:12,240 --> 00:57:14,560
that I do wanna address.

1116
00:57:14,560 --> 00:57:18,160
So Donald Schroeder asked, can
the CON t one l be installed

1117
00:57:18,160 --> 00:57:21,760
midsegment on the t one
l network allowing for four

1118
00:57:21,760 --> 00:57:23,575
separate segments to
branch off from it?

1119
00:57:23,575 --> 00:57:28,055
So I'm guessing if
we look at at this

1120
00:57:28,055 --> 00:57:31,295
network here where I've added

1121
00:57:32,055 --> 00:57:36,055
a con t one I've sort of done that
right here with these devices.

1122
00:57:36,055 --> 00:57:37,860
I've I've taken a
t one l network.

1123
00:57:37,860 --> 00:57:40,180
I've branched off of
the t one l network,

1124
00:57:40,180 --> 00:57:45,380
and I've gone cat five up to
a red five edge controller.

1125
00:57:45,380 --> 00:57:46,980
So, yeah, you could
you could do that,

1126
00:57:46,980 --> 00:57:50,620
but you would probably have to
lay the network out in a in a

1127
00:57:50,865 --> 00:57:54,785
logical fashion so that it's
still easy to follow and

1128
00:57:54,785 --> 00:57:56,745
is serviceable.

1129
00:57:59,425 --> 00:58:00,465
Andrew Little said,

1130
00:58:00,465 --> 00:58:04,100
what do you do if you have switches
that do not support ten meg anymore?

1131
00:58:04,100 --> 00:58:06,740
It doesn't impact t one l
because you're going through a

1132
00:58:06,740 --> 00:58:07,700
con t one l.

1133
00:58:07,700 --> 00:58:11,700
So the con t one l
supports ten one hundred on

1134
00:58:11,700 --> 00:58:13,820
the cat five side.

1135
00:58:18,595 --> 00:58:20,835
How do the firmware updates
for the field devices over the

1136
00:58:20,835 --> 00:58:22,875
network performed terribly?

1137
00:58:24,115 --> 00:58:27,475
We are working on I'm I'm
good. I'm not in sales guys.

1138
00:58:27,475 --> 00:58:29,195
I'm gonna tell you guys the real

1139
00:58:30,600 --> 00:58:33,480
so firmware upgrades over MSTP,

1140
00:58:33,480 --> 00:58:36,320
especially in the
v four landscape,

1141
00:58:36,360 --> 00:58:39,480
are a lesson in patients quite

1142
00:58:39,480 --> 00:58:43,000
literally because we're talking
firmware files that are now

1143
00:58:43,000 --> 00:58:47,095
twenty four or twenty five
megabytes compared to back in

1144
00:58:47,095 --> 00:58:49,735
the DSC DAC days
where they're, like,

1145
00:58:49,735 --> 00:58:51,855
twenty four kilobytes.

1146
00:58:53,095 --> 00:58:54,455
So we're talking, you know,

1147
00:58:54,455 --> 00:58:58,415
hundreds or thousand times
size difference in file size,

1148
00:59:01,340 --> 00:59:04,140
and we're running over
seventy six eight.

1149
00:59:04,140 --> 00:59:09,580
So firmware is an item of
contention internally here.

1150
00:59:09,580 --> 00:59:11,900
Know it is amongst
you guys as well.

1151
00:59:11,900 --> 00:59:13,340
There's a couple of
things you could do.

1152
00:59:13,340 --> 00:59:14,340
For now,

1153
00:59:15,085 --> 00:59:17,805
we're working on
firmware broadcasts.

1154
00:59:17,805 --> 00:59:21,645
So basically, what that means
is you can broadcast the

1155
00:59:21,645 --> 00:59:25,525
firmware update
onto an MSTP network

1156
00:59:26,620 --> 00:59:29,500
and it'll update every
single device at once.

1157
00:59:29,500 --> 00:59:31,980
And you basically just tell
it what network you wanna update.

1158
00:59:31,980 --> 00:59:36,780
So what that means is if it took
three hours to upgrade one device,

1159
00:59:36,780 --> 00:59:39,660
it'll also take three hours
to upgrade all of the devices

1160
00:59:39,660 --> 00:59:41,695
because they're all gonna
upgrade at the same time,

1161
00:59:41,695 --> 00:59:44,415
but you'll never be less than
three hours, essentially.

1162
00:59:44,415 --> 00:59:46,415
The other thing that we're
working on right now,

1163
00:59:46,415 --> 00:59:47,695
it's ongoing development.

1164
00:59:47,695 --> 00:59:49,695
It has been for
probably the last year,

1165
00:59:49,695 --> 00:59:51,855
is the differential firmware.

1166
00:59:51,855 --> 00:59:54,975
So that means that rather
than sending the whole entire

1167
00:59:54,975 --> 00:59:59,500
firmware file, we just send the
what's changed in the binary.

1168
00:59:59,500 --> 01:00:02,420
And that should
give us a lot more

1169
01:00:03,820 --> 01:00:06,380
efficiency when we're
transferring that firmware file.

1170
01:00:06,380 --> 01:00:09,020
So it's not great right now,

1171
01:00:09,020 --> 01:00:11,825
but we are working on
ways to improve it.

1172
01:00:11,825 --> 01:00:14,145
The other thing that you can do
to hold you over until we have

1173
01:00:14,145 --> 01:00:18,385
all that stuff released is to do
the dual mode firmware update.

1174
01:00:18,385 --> 01:00:20,305
So, basically,

1175
01:00:20,305 --> 01:00:23,505
plan for a firmware update
before you get to site if you

1176
01:00:23,505 --> 01:00:26,185
have access to this
site, remote access.

1177
01:00:26,320 --> 01:00:29,680
Do the staged update, which
means you upload the firmware

1178
01:00:29,680 --> 01:00:32,400
file to each controller
ahead of time,

1179
01:00:32,400 --> 01:00:33,760
and it just sits in
its flash memory.

1180
01:00:33,760 --> 01:00:36,240
It doesn't actually
deploy the firmware,

1181
01:00:36,240 --> 01:00:39,280
and it doesn't impact the
functionality of the controller.

1182
01:00:39,280 --> 01:00:41,960
It doesn't disrupt the
network or anything like that.

1183
01:00:42,025 --> 01:00:45,385
And it'll just upload all those
firmware files however long it takes.

1184
01:00:45,385 --> 01:00:46,585
And then when you get to site,

1185
01:00:46,585 --> 01:00:48,665
all you have to do is tell
the controller to use that new

1186
01:00:48,665 --> 01:00:49,705
firmware file.

1187
01:00:49,705 --> 01:00:52,945
So that's one thing you
can do for now until you

1188
01:00:53,865 --> 01:00:56,505
until you're, we have
those new methodologies

1189
01:00:56,505 --> 01:00:59,070
of firmware loading.

1190
01:01:08,230 --> 01:01:10,190
I'm just racing here.

1191
01:01:10,655 --> 01:01:14,175
Probably all the way down to
can NFC be removable for jobs

1192
01:01:14,175 --> 01:01:15,695
that don't allow it.

1193
01:01:15,695 --> 01:01:18,935
Oh, where is that?
Yes. Can it okay.

1194
01:01:19,375 --> 01:01:20,655
Thank you, Darren.

1195
01:01:20,655 --> 01:01:23,855
I think it's like you're
an you're you're a plant,

1196
01:01:23,855 --> 01:01:28,110
an audience plant, So you'll get
me to plug our new controller.

1197
01:01:29,510 --> 01:01:31,750
Watch for an announcement
in the next couple of days.

1198
01:01:31,750 --> 01:01:35,350
We are releasing the new
red five secured facility models

1199
01:01:35,350 --> 01:01:39,230
that'll have NFC and BLE removed

1200
01:01:39,795 --> 01:01:41,395
from the controller.

1201
01:01:41,395 --> 01:01:44,275
So that'll be the new red
five secondurity facility.

1202
01:01:44,275 --> 01:01:47,395
You should see an announcement
go up Friday, actually.

1203
01:01:47,395 --> 01:01:48,995
It would have gone
up today, actually,

1204
01:01:48,995 --> 01:01:53,275
but we're still waiting for
some, paperwork to be, filed.

1205
01:01:56,920 --> 01:01:58,480
Okay.

1206
01:02:02,760 --> 01:02:05,680
I'm just gonna skip over
some of these questions.

1207
01:02:10,465 --> 01:02:13,905
Can you please share the future
plans for the DVCPoe controllers?

1208
01:02:13,905 --> 01:02:14,785
That's a good question.

1209
01:02:14,785 --> 01:02:16,545
Is there a red five
replacement coming,

1210
01:02:16,545 --> 01:02:19,420
and will POE remain an
option for VAV controllers?

1211
01:02:19,420 --> 01:02:21,180
So the plan is this,

1212
01:02:21,180 --> 01:02:25,900
the DVC PoE controllers will not go
anywhere until we have a replacement.

1213
01:02:25,900 --> 01:02:29,420
So, power over Ethernet DVC
will be the only one that we

1214
01:02:29,420 --> 01:02:31,380
don't obsolete.

1215
01:02:31,660 --> 01:02:32,140
Yes.

1216
01:02:32,140 --> 01:02:34,420
There will be a
replacement coming

1217
01:02:35,235 --> 01:02:37,355
in red five world,

1218
01:02:38,195 --> 01:02:41,475
but we just have to schedule
it in to work on it.

1219
01:02:41,475 --> 01:02:46,075
But we are planning on doing a power
over Ethernet model of red five.

1220
01:02:49,010 --> 01:02:50,570
Okay.

1221
01:02:52,930 --> 01:02:56,610
Does it work on an eighteen
dash two shielded wire,

1222
01:02:56,610 --> 01:02:58,370
so not a big network?

1223
01:02:58,370 --> 01:03:00,170
Yeah. We it does.

1224
01:03:00,175 --> 01:03:03,935
Again, it it comes down to the
quality of the wire and the distance.

1225
01:03:03,935 --> 01:03:07,055
So you'll have to look at if
you could get the wire specs to

1226
01:03:07,055 --> 01:03:10,575
make sure that the overall line
impedance isn't over a hundred

1227
01:03:10,575 --> 01:03:13,415
ohms, I believe it
it should work okay.

1228
01:03:13,840 --> 01:03:17,440
Again, it it comes down to going
to site and doing a site survey

1229
01:03:17,440 --> 01:03:20,800
and maybe even getting a
picoscope and testing the cable

1230
01:03:20,800 --> 01:03:23,560
out and looking for reflections
and that kind of thing.

1231
01:03:28,625 --> 01:03:32,545
Ryan, said, can you explain a bit
how to troubleshoot the t one l or

1232
01:03:32,545 --> 01:03:36,185
edge networks with Wireshark
under back that secure connect?

1233
01:03:36,545 --> 01:03:39,265
Actually, that's a good
question, Ryan. Hey, Ryan.

1234
01:03:39,265 --> 01:03:41,625
Good to see you. That's
good that you're here.

1235
01:03:43,720 --> 01:03:48,640
We're we've got Wireshark built
into the controllers now, and

1236
01:03:49,400 --> 01:03:52,960
we are working on
having the ability to,

1237
01:03:53,720 --> 01:03:55,800
take captures of
encrypted traffic,

1238
01:03:55,800 --> 01:03:58,835
but it's not something that is
actually I have to look and see

1239
01:03:58,835 --> 01:04:00,515
where we are with it
with the firmware team.

1240
01:04:00,515 --> 01:04:02,555
But, yes, that is coming.

1241
01:04:02,915 --> 01:04:06,155
And right now, Wireshark is
built right into the controller.

1242
01:04:09,315 --> 01:04:11,220
Sarah Sarah Smith is asking,

1243
01:04:11,220 --> 01:04:14,180
is embedded graphics like the
etouch saving a graphic into

1244
01:04:14,180 --> 01:04:16,260
the controller along
with the database?

1245
01:04:16,260 --> 01:04:21,820
Actually, so the embedded graphics
will work in a similar fashion.

1246
01:04:22,020 --> 01:04:26,015
You will load the graphic the
controller graphic into an

1247
01:04:26,015 --> 01:04:29,455
FIL object, and that FIL
object is part of the database.

1248
01:04:29,455 --> 01:04:31,535
So if you save the
controller database out,

1249
01:04:31,535 --> 01:04:32,975
you'll save the
graphics with it.

1250
01:04:32,975 --> 01:04:35,295
So if you do, again, a
VAV network, for instance,

1251
01:04:35,295 --> 01:04:37,695
you could take that single
database with a graphic in it

1252
01:04:37,695 --> 01:04:40,455
and deploy it to all of
your VAV controllers.

1253
01:04:43,910 --> 01:04:46,790
Corey asks, are there any updates
or timelines with regards to

1254
01:04:46,790 --> 01:04:49,270
refresh the Intellibus platform?

1255
01:04:49,270 --> 01:04:52,150
Stay tuned for a
separate webinar on that.

1256
01:04:52,150 --> 01:04:53,670
That's a a big question.

1257
01:04:53,670 --> 01:04:58,165
There are plans to refresh
the Intellibus system.

1258
01:04:58,165 --> 01:05:00,565
Exactly what that all entails
kinda out of scope of what I

1259
01:05:00,565 --> 01:05:03,445
wanted to get into this
because it's a big rabbit hole.

1260
01:05:03,445 --> 01:05:07,125
Question two, any plans to release an
HOA version of the red five module?

1261
01:05:07,125 --> 01:05:08,045
Yes.

1262
01:05:09,940 --> 01:05:14,180
Question three, when will the
twenty four VAC power supply

1263
01:05:14,180 --> 01:05:16,700
for the red five
modules be released?

1264
01:05:17,140 --> 01:05:19,780
We actually wanted to release
it in April this month,

1265
01:05:19,780 --> 01:05:22,740
but we found a bug with
it that may that meant

1266
01:05:22,740 --> 01:05:24,705
that we had fixed the bug,

1267
01:05:24,705 --> 01:05:28,265
and then we missed the firmware
release train for four twenty.

1268
01:05:28,385 --> 01:05:31,585
So we have to catch the four
twenty one release train.

1269
01:05:31,585 --> 01:05:35,665
So the, Red five
expand o four ACDC

1270
01:05:35,665 --> 01:05:39,910
will be released with four
twenty one this summer.

1271
01:05:40,830 --> 01:05:44,990
Are we anywhere near releasing
red five plus RTR with two

1272
01:05:44,990 --> 01:05:46,990
separate Ethernet ports?

1273
01:05:46,990 --> 01:05:50,390
Actually, I've just started working
on the product definition for that.

1274
01:05:50,625 --> 01:05:51,985
So we are getting there.

1275
01:05:51,985 --> 01:05:54,625
It's not going to be tomorrow,

1276
01:05:54,625 --> 01:05:57,745
but we are working on the definition
of it right now as I speak.

1277
01:05:57,745 --> 01:05:59,265
In fact, if I wasn't
in this webinar,

1278
01:05:59,265 --> 01:06:00,665
I'd be working on that.

1279
01:06:05,570 --> 01:06:09,090
So if the actuator part
dies on the red flag VAV,

1280
01:06:09,090 --> 01:06:10,210
do we have to replace
the whole thing?

1281
01:06:10,210 --> 01:06:13,530
Yes. It'll have to go to RMA.
It's not field replaceable.

1282
01:06:16,610 --> 01:06:20,890
Okay. Let's just get I
gotta get through here.

1283
01:06:23,705 --> 01:06:27,385
Do you offer development or
lab box kit that includes

1284
01:06:27,385 --> 01:06:29,145
controllers and telepromp?

1285
01:06:29,145 --> 01:06:32,945
Do we like, if they're asking
if we have a prebuilt demo box

1286
01:06:33,590 --> 01:06:33,990
Oh.

1287
01:06:33,990 --> 01:06:35,230
Do.

1288
01:06:35,990 --> 01:06:37,270
That's a good thing.

1289
01:06:37,270 --> 01:06:41,230
You want, like, a a even
like a training kit or a

1290
01:06:42,230 --> 01:06:43,750
so there's two answers to that.

1291
01:06:43,750 --> 01:06:46,070
Yeah. We actually do need
a good marketing kit.

1292
01:06:46,070 --> 01:06:48,685
So that's something that
is on a to do list for us.

1293
01:06:48,685 --> 01:06:52,285
We do we do have, IntelliCloud,

1294
01:06:52,285 --> 01:06:53,925
and we have,

1295
01:06:54,605 --> 01:06:57,605
Canvas that allows to build up

1296
01:06:59,325 --> 01:07:01,245
offline networks if
well, not offline.

1297
01:07:01,245 --> 01:07:04,230
The network is online, but
it's not in production.

1298
01:07:04,230 --> 01:07:08,870
So you can still, build
your databases through that.

1299
01:07:08,870 --> 01:07:10,470
We also have what is it called?

1300
01:07:10,470 --> 01:07:12,750
The, Delta training

1301
01:07:13,430 --> 01:07:15,030
it was a Delta training device.

1302
01:07:15,030 --> 01:07:16,230
You can online ordering.

1303
01:07:16,230 --> 01:07:17,750
It's called the DTD,

1304
01:07:17,750 --> 01:07:21,865
and that's like a little mini
IO board that sort of mimics a

1305
01:07:21,865 --> 01:07:25,065
fan coil controller with
actual IO ports and a fan and

1306
01:07:25,065 --> 01:07:26,105
everything on it.

1307
01:07:26,105 --> 01:07:27,625
You can get that
on online ordering,

1308
01:07:27,625 --> 01:07:30,105
you can connect that to any
controller as well to work with

1309
01:07:30,105 --> 01:07:32,505
a, to do any
offline programming.

1310
01:07:32,505 --> 01:07:36,230
But I think we should incorporate
that into That's a good idea.

1311
01:07:36,230 --> 01:07:37,470
Yep.

1312
01:07:39,430 --> 01:07:42,630
Lyle says I can send a picture
of the Ducon BT for proof.

1313
01:07:42,630 --> 01:07:43,270
Thanks, Lyle.

1314
01:07:43,270 --> 01:07:43,830
I know.

1315
01:07:43,830 --> 01:07:45,830
So Picture is different.

1316
01:07:45,830 --> 01:07:47,710
You guys are comedians.

1317
01:07:49,155 --> 01:07:51,075
I'm gonna do one more question,

1318
01:07:51,075 --> 01:07:54,315
and then we're gonna call
it because there's, like,

1319
01:07:54,515 --> 01:07:57,755
a lot of these are just
sort of replicating.

1320
01:07:59,475 --> 01:08:00,035
Oh, yeah.

1321
01:08:00,035 --> 01:08:02,515
I wanna I I really wanna keep
answering these questions

1322
01:08:02,515 --> 01:08:05,560
regarding stability
of of the network.

1323
01:08:05,920 --> 01:08:11,440
John asks, have you used
unshielded wire with success?

1324
01:08:11,440 --> 01:08:14,480
Are you confident in your sixty
four controller limit using

1325
01:08:14,480 --> 01:08:18,200
unshielded twenty
two gauge wire?

1326
01:08:20,875 --> 01:08:22,955
There's a lot to
unpack in that one.

1327
01:08:22,955 --> 01:08:25,755
So we actually have various

1328
01:08:25,755 --> 01:08:28,635
different types of wire on
our internal test wall where we're

1329
01:08:28,635 --> 01:08:30,515
running sixty four controllers.

1330
01:08:32,090 --> 01:08:34,890
We're confident in our test
wall. It's running really well.

1331
01:08:34,890 --> 01:08:35,930
It's running constantly.

1332
01:08:35,930 --> 01:08:38,130
It's been running
for several months,

1333
01:08:38,250 --> 01:08:39,770
but every site is different.

1334
01:08:39,770 --> 01:08:43,450
So, again, it comes down to
verifying the cable and verifying the

1335
01:08:43,450 --> 01:08:44,730
feasibility of that cable.

1336
01:08:44,730 --> 01:08:46,895
We have tested on
unshield cable.

1337
01:08:46,895 --> 01:08:48,895
Maybe Lyle, if he's still
here, could chime in.

1338
01:08:48,895 --> 01:08:50,935
He's the guy that tested it.

1339
01:08:52,495 --> 01:08:55,735
So it would come down to

1340
01:08:57,135 --> 01:09:00,575
verifying that wire on-site
and and testing it out.

1341
01:09:00,575 --> 01:09:01,895
Bring your picoscope

1342
01:09:03,570 --> 01:09:05,970
and verifying how that
cable's functioning.

1343
01:09:05,970 --> 01:09:09,530
Like, you have to it's good to know
what the specs are on that wire.

1344
01:09:09,970 --> 01:09:12,970
We're gonna do as much
as we can to publish

1345
01:09:13,995 --> 01:09:17,195
our internal test results so
that we're transparent and you

1346
01:09:17,195 --> 01:09:19,835
know what we've tested
with and what works.

1347
01:09:19,835 --> 01:09:20,995
So,

1348
01:09:22,235 --> 01:09:24,635
you know, we're trying to
max out like, we you know,

1349
01:09:24,635 --> 01:09:27,275
we're using different gauges
of wire in our own wall,

1350
01:09:27,275 --> 01:09:30,810
which is never a recommended
thing just to stress test it.

1351
01:09:30,810 --> 01:09:32,330
So we're relatively common.

1352
01:09:32,330 --> 01:09:34,970
You know, we're confident in our
sixty four device controller limit,

1353
01:09:34,970 --> 01:09:36,730
but as always, I mean,

1354
01:09:36,730 --> 01:09:39,210
your mileage may vary with
the wire that's on-site,

1355
01:09:39,210 --> 01:09:41,330
and that's even true with MSTP.

1356
01:09:41,915 --> 01:09:44,715
We gotta make sure that the
that the network itself is is

1357
01:09:44,715 --> 01:09:46,955
healthy and the
topology is correct.

1358
01:09:46,955 --> 01:09:49,115
There's no t's, no
stars, etcetera.

1359
01:09:49,115 --> 01:09:52,595
So there is work to be
done when you deploy this stuff.

1360
01:09:58,570 --> 01:10:00,130
Okay.

1361
01:10:01,530 --> 01:10:04,090
T one l ring
topology. Apologies.

1362
01:10:04,090 --> 01:10:06,370
We already answered this
in the previous response.

1363
01:10:07,905 --> 01:10:08,385
No.

1364
01:10:08,385 --> 01:10:12,985
We do not support t one l in
a ring topology at this time.

1365
01:10:13,425 --> 01:10:15,585
That can be something we
would have to look into.

1366
01:10:15,585 --> 01:10:18,425
It's a good it's a good
feature request, actually.

1367
01:10:18,785 --> 01:10:22,690
But there are, bypass relays to
keep the network alive in the

1368
01:10:22,690 --> 01:10:24,810
in the loss of a device.

1369
01:10:28,850 --> 01:10:32,850
When will a t one l version
of the non VAV red five edge

1370
01:10:32,850 --> 01:10:34,130
controllers be released?

1371
01:10:34,130 --> 01:10:34,610
Yes.

1372
01:10:34,610 --> 01:10:37,855
I would like to do t one
l in all of our IP based

1373
01:10:37,855 --> 01:10:38,975
controllers eventually.

1374
01:10:38,975 --> 01:10:43,615
We're focusing on the application
specific unitary first.

1375
01:10:43,615 --> 01:10:45,295
But, yeah, I think
that's a great question.

1376
01:10:45,295 --> 01:10:47,735
That's something that we
would like to do as well.

1377
01:10:49,470 --> 01:10:52,990
Someone asked if power
polarity was still a problem.

1378
01:10:52,990 --> 01:10:54,910
Does does that ring a bell?

1379
01:10:54,910 --> 01:10:55,150
Yeah.

1380
01:10:55,150 --> 01:10:57,070
It really I mean, if they're
sharing the same power,

1381
01:10:57,070 --> 01:10:59,470
you you have to maintain
polarity on power always.

1382
01:10:59,470 --> 01:11:00,310
Okay.

1383
01:11:00,945 --> 01:11:02,665
That's a good question.

1384
01:11:02,865 --> 01:11:06,425
It has to make my job easy
by asking good questions.

1385
01:11:07,745 --> 01:11:10,305
If I have a red five plus
at the end of a line,

1386
01:11:10,305 --> 01:11:13,830
can I connect a con t one l to
carry out the t one l b a b?

1387
01:11:13,830 --> 01:11:17,110
I'm assuming if
it's a the end of a,

1388
01:11:17,110 --> 01:11:19,990
cat five network, then,
yep, yeah, you could,

1389
01:11:19,990 --> 01:11:22,430
you could add a con
t one l to that.

1390
01:11:24,630 --> 01:11:26,270
And

1391
01:11:28,445 --> 01:11:32,045
I think she's asking for
comparison between Johnson

1392
01:11:32,045 --> 01:11:34,005
Controls and Allerton.

1393
01:11:34,365 --> 01:11:35,685
Oh,

1394
01:11:36,285 --> 01:11:37,165
that'll be up to us.

1395
01:11:37,165 --> 01:11:39,005
That's a that's a
product management job.

1396
01:11:39,005 --> 01:11:40,965
That should be something
that I have to do.

1397
01:11:41,500 --> 01:11:41,900
Yeah.

1398
01:11:41,900 --> 01:11:44,620
I think we would actually, I
think you did one, didn't you?

1399
01:11:44,620 --> 01:11:47,580
We did. Mark we did we
haven't published it.

1400
01:11:47,580 --> 01:11:49,100
We no. It's
published. We have it.

1401
01:11:49,100 --> 01:11:53,125
We have the comparison of us
versus Honeywell slash Allerton,

1402
01:11:53,125 --> 01:11:56,405
but I don't believe Johnson
Controls at the time that I did

1403
01:11:56,405 --> 01:11:58,565
it had a t one l offering.

1404
01:11:58,565 --> 01:12:00,405
So I'm not sure
if they still do.

1405
01:12:00,405 --> 01:12:04,005
But, yeah, it was
Allerton's was not

1406
01:12:04,005 --> 01:12:05,445
any third party devices.

1407
01:12:05,445 --> 01:12:06,965
So they just had it on board,

1408
01:12:06,965 --> 01:12:10,770
so they did not have the
equivalent of the Conn t one l.

1409
01:12:10,770 --> 01:12:13,810
So you could only use it
within their EcoStruxure.

1410
01:12:13,810 --> 01:12:16,610
But it was essentially the same thing
because it's the same technology.

1411
01:12:16,610 --> 01:12:19,850
So they still have
ten base t one l. So.

1412
01:12:20,625 --> 01:12:23,505
Okay. Well, it's eleven fifteen.

1413
01:12:23,505 --> 01:12:26,985
Everybody that stuck around, I
really, really appreciate it.

1414
01:12:27,105 --> 01:12:29,025
Thank you so much
for joining us today.

1415
01:12:29,025 --> 01:12:32,665
I it's all I know you guys are busy
and you got a million things to do.

1416
01:12:33,360 --> 01:12:37,160
So I always love it when I
get to to interact with you.

1417
01:12:37,600 --> 01:12:38,800
And I I really,

1418
01:12:38,800 --> 01:12:43,080
really appreciate you guys taking
the time to to join us today.

1419
01:12:43,120 --> 01:12:45,800
As always, you guys know
how to get a hold of me,

1420
01:12:47,325 --> 01:12:49,685
and I love hearing from you.

1421
01:12:50,925 --> 01:12:51,565
That's it.

1422
01:12:51,565 --> 01:12:53,485
Thank you very much.
Yep. That's perfect.

1423
01:12:53,485 --> 01:12:56,605
All of this will come out to you
guys within the next week or so.

1424
01:12:56,605 --> 01:12:57,645
We really appreciate it.

1425
01:12:57,645 --> 01:13:00,010
Again, those of you who stuck
around, thank you so much.

1426
01:13:00,010 --> 01:13:03,770
We also will be having our
next webinar, May twenty first.

1427
01:13:03,770 --> 01:13:06,410
So everybody come see
what that's all about.

1428
01:13:06,410 --> 01:13:09,290
There's good stuff with
Sentra and Milsight,

1429
01:13:09,290 --> 01:13:11,530
some some interesting
products there.

1430
01:13:11,530 --> 01:13:15,745
So we'll see you all soon.
Appreciate it. Thanks, Andy.

1431
01:13:15,745 --> 01:13:18,145
Cheers, guys. Thanks,
Emily, for all your help.

1432
01:13:18,145 --> 01:13:20,745
Bye, everyone. Bye.