CSoft.TopPortLib
6.0.1
See the version list below for details.
dotnet add package CSoft.TopPortLib --version 6.0.1
NuGet\Install-Package CSoft.TopPortLib -Version 6.0.1
<PackageReference Include="CSoft.TopPortLib" Version="6.0.1" />
paket add CSoft.TopPortLib --version 6.0.1
#r "nuget: CSoft.TopPortLib, 6.0.1"
// Install CSoft.TopPortLib as a Cake Addin #addin nuget:?package=CSoft.TopPortLib&version=6.0.1 // Install CSoft.TopPortLib as a Cake Tool #tool nuget:?package=CSoft.TopPortLib&version=6.0.1
Communication
通讯库
用法详见例子
一、为什么要分割数据包
因为通信的时候,接收到的数据是一个连续的数据流。我们需要从中获取到一个完整的数据包。
二、分割一个数据包的几种方式
1.包头和包尾
例子
头:01 02 尾:04 06(以后的例子中的头和尾都用01 02 和 04 06) 一个完整的数据包 01 02 xx xx … xx 04 06
安全性问题
如果对方只发送了包头,然后一直发送垃圾数据,这些数据中不包含包尾。我们的程序无法丢弃这些垃圾数据,这会导致占用内存越来越大,最终导致程序崩溃
2.包尾
例子
一个完整的数据包 xx xx … xx 04 06
安全性问题
如果对方一直发送垃圾数据,这些数据中不包含包尾。我们的程序无法丢弃这些垃圾数据,这会导致占用内存越来越大,最终导致程序崩溃
3.包头和长度
例子
一个完整的数据包 01 02 03 05 07 其中01 02 是包头(TCP可以不带包头),03代表长度(也可以传入指定长度)。比如协议规定,除包头以外,还有长度为3的数据,本例中是03 05 07。
安全性问题
如果对方一直发送垃圾数据,这些数据中不包含包头。我们的程序可以移除这些无效数据,这样不会使内存占用变大。所以推荐使用这种分割数据包的方式
4.时间
这种方式用于串口通信。不会产生垃圾数据占用内存的问题。一定时间内(比如Modbus是200ms)收到的数据作为一个完整的数据包
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 is compatible. net5.0-windows was computed. net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- CSoft.Communication (>= 6.0.1)
- CSoft.Crow (>= 6.0.1)
- CSoft.Parser (>= 6.0.1)
-
net5.0
- CSoft.Communication (>= 6.0.1)
- CSoft.Crow (>= 6.0.1)
- CSoft.Parser (>= 6.0.1)
-
net6.0
- CSoft.Communication (>= 6.0.1)
- CSoft.Crow (>= 6.0.1)
- CSoft.Parser (>= 6.0.1)
NuGet packages (6)
Showing the top 5 NuGet packages that depend on CSoft.TopPortLib:
Package | Downloads |
---|---|
CSoft.Protocol.ProtocolInterface
协议接口 |
|
FTIRSpectrometerCore
基于设备私有网络应用层通信协议开发为傅里叶红外光谱产品服务的配套模块库 |
|
GalaxySmartDeviceCore
如果银河系有旋律,星星一定是发光的IoT设备。做可信赖的智慧工业物联网的生态型伙伴,听一听宇宙终极乐章。 |
|
FTIRSpectrometerBusiness
傅里叶红外光谱商用库是为傅里叶红外光谱产品服务的配套模块,基于设备私有网络应用层通信协议开发。它提供了一组功能强大的接口和工具,方便用户对傅里叶红外光谱产品进行操作和控制,具有高度可定制、高效稳定、易于使用、灵活可扩展等特点。 |
|
CSoft.Communication.Bluetooth
Package Description |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated | |
---|---|---|---|
8.3.1 | 1,040 | 9/3/2024 | |
8.3.0 | 668 | 6/28/2024 | |
8.2.9 | 215 | 6/25/2024 | |
8.2.8 | 164 | 6/21/2024 | |
8.2.7 | 379 | 6/11/2024 | |
8.2.6 | 229 | 6/7/2024 | |
8.2.5 | 146 | 6/6/2024 | |
8.2.4 | 137 | 6/6/2024 | |
8.2.3 | 145 | 6/6/2024 | |
8.2.2-pre | 101 | 5/31/2024 | |
8.2.1-pre | 105 | 5/30/2024 | |
8.2.0 | 137 | 5/30/2024 | |
8.1.7 | 192 | 5/28/2024 | |
8.1.6 | 707 | 4/30/2024 | |
8.1.5 | 179 | 4/29/2024 | |
8.1.3 | 284 | 4/11/2024 | |
8.1.2 | 225 | 4/10/2024 | |
8.1.1 | 179 | 3/22/2024 | |
8.1.0 | 232 | 3/11/2024 | |
8.0.9 | 214 | 2/28/2024 | |
8.0.8 | 190 | 2/4/2024 | |
8.0.7 | 150 | 2/4/2024 | |
8.0.6 | 375 | 12/28/2023 | |
8.0.5 | 157 | 12/28/2023 | |
8.0.4 | 206 | 12/20/2023 | |
8.0.3 | 200 | 12/14/2023 | |
8.0.2 | 185 | 12/12/2023 | |
8.0.1 | 392 | 12/4/2023 | |
8.0.0 | 444 | 11/15/2023 | |
7.0.6 | 318 | 9/19/2023 | |
7.0.5 | 577 | 8/28/2023 | |
7.0.4 | 197 | 8/17/2023 | |
7.0.3 | 2,493 | 2/28/2023 | |
7.0.2 | 523 | 2/27/2023 | |
7.0.1 | 2,074 | 2/13/2023 | |
7.0.0 | 2,819 | 11/9/2022 | |
6.6.2 | 473 | 10/24/2022 | |
6.6.1 | 778 | 10/17/2022 | |
6.6.0 | 450 | 10/17/2022 | |
6.5.2 | 477 | 10/15/2022 | |
6.5.1 | 580 | 10/15/2022 | |
6.5.0 | 749 | 10/14/2022 | |
6.4.3 | 460 | 10/14/2022 | |
6.4.2 | 474 | 10/14/2022 | |
6.4.1 | 473 | 10/13/2022 | |
6.4.0 | 462 | 10/13/2022 | |
6.3.0 | 484 | 10/13/2022 | |
6.2.6 | 767 | 9/30/2022 | |
6.2.5 | 449 | 9/30/2022 | |
6.2.4 | 636 | 9/26/2022 | |
6.2.3 | 629 | 9/23/2022 | |
6.2.2 | 541 | 9/23/2022 | |
6.2.1 | 524 | 9/22/2022 | |
6.2.0 | 1,210 | 8/19/2022 | |
6.1.2 | 512 | 8/12/2022 | |
6.1.1 | 505 | 5/26/2022 | |
6.0.9 | 529 | 5/19/2022 | |
6.0.5 | 491 | 5/17/2022 | |
6.0.4 | 503 | 5/13/2022 | |
6.0.3 | 534 | 3/15/2022 | |
6.0.2 | 477 | 3/15/2022 | |
6.0.1 | 648 | 11/9/2021 | |
5.1.4 | 497 | 8/18/2021 | |
5.1.3 | 529 | 7/8/2021 | |
5.1.2 | 482 | 7/8/2021 | |
5.1.1 | 405 | 7/8/2021 | |
5.1.0 | 616 | 7/7/2021 | |
5.0.9 | 517 | 7/7/2021 | |
5.0.8 | 588 | 3/11/2021 | |
5.0.7 | 569 | 1/26/2021 | |
5.0.6 | 473 | 1/23/2021 | |
5.0.5 | 518 | 1/22/2021 | |
5.0.4 | 510 | 1/11/2021 | |
5.0.3 | 472 | 1/11/2021 | |
5.0.2 | 544 | 11/18/2020 | |
5.0.1 | 601 | 11/18/2020 | |
1.0.2 | 548 | 11/18/2020 | |
1.0.1 | 550 | 10/12/2020 | |
1.0.0 | 636 | 6/30/2020 |
通讯口使用类库