My First Plug-in - Inventor API .NET 开发从0开始-课程2

inventor二次开发-课程1-环境搭建及开发资料 文章目录1.为什么要二次开发?2.二次开发的条件3.inventor开发的资料4.inventor开发的那事儿5.开发方式的选择6.开发环境的搭建:7.本课程的核心思路 1.为什么要二次开发? 定制自己所需要的功能,批量的实现重复性的操作。 能用鼠标和键盘交互绘制的图形,二次开发也可以。 2.二次开发的条件 (1)熟悉inventor的基本操作 (2)具备一定的编程基础,在本次课程中需要用到... 阅读详情

在课程1我们做了一个简单的例子,初步知道程序大概会是什么样子,如何用一个按钮实现我们的设计意图。所谓知其然需知其所以然,我们需要走到代码背后,解读其基本的元素,为进一步的学习做好准备。不要紧张,本课程在内容上考虑到了初学者,甚至.NET的初学者情况,在描述上尽量的不涉及到很复杂的原理以及知识点。当然,如果你想在有关方面有综合而深入的了解,可以参考.NET的教程。

课程2使用的代码工程如下:

lesson2_vb-net.zip(zip - 19Kb)

lesson2_c-sharp.zip(zip - 23Kb)

What does it mean to “build” code?

The code that you typed in to Visual Basic Express in Lesson 1 was a set of human-readable instructions (source code) that needed to be converted into code that could be understood and executed by the computer. The “build” you performed did just that: it packaged up the resulting executable code inside a standard Windows EXE file. It’s also possible to create a DLL (Dynamic-Link Library) that can be loaded into Autodesk Inventor, but that’s a more advanced topic not covered by this guide.

The following screenshot shows the output EXE along with the associated program debug database (which provides additional information when troubleshooting the EXE), once you have built the solution in Lesson 1 using Visual Basic Express. The path to which the EXE gets compiled is specified in the Visual Basic Express project settings and is set, by default, to the bin sub-folder of the Visual Basic Express project folder. 

在课程1,我们首先打开了一个工程,所谓工程简单讲就是设计应用程序的一组文件,包括源代码,配置文件,资源文件等。为了让程序运行,有一步是在Visual Basic环境中,点击【调试】>>【编译 MyFirstInventorPlugin_Lesson1】。什么叫做“编译”?一句话,就是让代码能够让计算机看得懂,能执行。课程1最终产生一个EXE程序,类似我们平时运行的林林种种的软件。也可设计为DLL(动态链接库),这种方式作为Inventor插件加载。我们暂时不会介绍。

下图就是课程1产生的几个文件:EXE是执行文件,PDB是供调试用的。EXE一般在什么地方?通过代码工程属性>>编译选项>>输出目录里设置。

 

Choosing a Programming Language and Development Tool

Just as humans use different languages to communicate, you have various language options available to you when creating an Inventor plug-in: for the purposes of this guide we have chosen Visual Basic .NET (VB.NET), a strong general-purpose programming language that is popular with Inventor developers.

There are a number of tools available for developing VB.NET code. They range from open source tools such as SharpDevelop to Microsoft’s flagship, professional development environment, Visual Studio. In your case you will be using Visual Basic Express, a free version of Visual Studio focused on building VB.NET applications.

Visual Basic Express is an Integrated Development Environment (IDE) because it is composed of various tools, menus and toolbars which ease the creation and management of your code.

The project system in Visual Basic Express comprises Solution and Project files as well as Project Items, the individual files belonging to projects. A solution is a container for one or more projects. Each project can in turn be considered a container for project items – such as source files, icons, etc. – most of which get compiled into the resultant executable file (EXE or DLL). Visual Basic Express provides a Solution Explorer that organizes and displays the contents of the loaded solution in a tree-view format:

 

这是关于开发语言的选用。由于Inventor是COM API,可选的语言很多。本课程的是比较广泛使用的VB.NET。而开发工具,最权威的当属微软的Visual Studio。本课程使用免费的Visual Basic Express。这样在开发上你可以省去一笔费用。

Visual Basic Express是一个集成开发环境,包括了代码的编写,调试,工程设置管理,工具等很多内容。在课程1,我们首先打开了一个工程,所谓工程简单讲就是设计应用程序的一组文件,包括源代码,配置文件,资源文件等。最终产生的是dll或者EXE。

 

The Visual Basic Express interface also contains a text editor and an interface designer. These are displayed in the main window depending on the type of file being edited. The text editor is where you will enter the Visual Basic code for your Inventor plug-in. This editor provides advanced features such as IntelliSense and collapsible code sections along with the more classic text-editing features such as bookmarks and the display of line numbers.

IntelliSense is an extremely valuable feature of the Visual Studio family that greatly improves programmer productivity: it automatically provides suggestions for the code being written based on the objects available and the letters that are being typed. IntelliSense showing the methods and properties for a ComponentOccurrence:

 

工程里不同的文件类型会有不同的编辑环境。例如在课程中有Form1.vb,双击它进入了对话框编辑界面,能直接添加布置控件,例如按钮,单选多选控件等,而打开Form1.vb的源代码,就可以在编辑界面中进行具体编写。

代码窗口中,可以看到诸如Dim xxx As xxxx 形式的代码,这是在定义变量。我们会使用它去操作对应的API。而Visual Basic里自带了IntelliSense工具,当变量后输入“点”号,就会出现其支持的方法,属性等内容,并包括方法的参数,属性的返回值类型等。而不用你来回的翻阅帮助文档,从而极大的提高设计效率。

 

Clearly one of the key features of Visual Basic Express is its ability to build VB.NET code into an executable file. During the build process, the language compiler performs various checks and analyses on the code. One such check is to ensure the code conforms to the syntactical rules of the Visual Basic language. The compiler also performs various other checks, such as whether a variable has been appropriately defined or not. Detected errors are reported via the Error List Window, typically found at the bottom of the main window.  The Error List can be displayed by selecting Error List from the View menu > Other Windows.

 

毫无疑问,Visual Basic会将代码编译为可执行的EXE程序。而这个过程包含了代码错误检查。所有错误会在【错误列表】中显示。你可以通过主菜单的【视图】>>【其它窗口】>>【错误列表】打开这个窗口。修改错误是代码调试经常做的工作。

 

The Visual in Visual Basic Express

One of the main strengths of Visual Basic Express is its set of tools for creating a User Interface. When you create a new project you can select a Windows Forms Application. When this template is used, the main window for the application is automatically created. This window is called a form and you can place user interface elements (called controls), such as a command buttons, on it. You add an element simply by selecting it in the Toolbox and then clicking and dragging it onto the Form. The Toolbox can be displayed using the View menu > Other Windows > Toolbox. Much of the code to make these elements work correctly gets added automatically to the project, greatly reducing the effort needed to get your application up and running.

设计可视化的界面也是Visual Basic很大的特色。你可以创建Form,Dialog,在其中添加各种控件。通过【视图】>>【其它窗口】>>【工具箱】可以打开控件的列表。



 

Reviewing your use of Visual Basic Express

In this section, you will create a blank project similar to the one you were provided in Lesson 1. This project will be the starting point for Lesson 3.

  1. Create a Windows Forms Application:
    Close the project from Lesson 1, if it is still open in Visual Basic Express, and then on the File menu, click New and then select New Project.

    This will open up a new dialog called New Project in which you have the option to select the template that will be used to create the plug-in application.

    As you are working with Visual Basic Express, your installed templates are under the Visual Basic category.

    In the center of the dialog, you can see various application templates that are available to you, the choice of which depends on the type of application you wish to create. As you’re creating a simple, standalone EXE with a dialog-based user interface, select the “Windows Forms Application” template.

    You now need to select a name for your project. Enter MyFirstInventorPlug-in in the box near the bottom of the New Project dialog and select OK: The basic solution containing your project should now be created and loaded into the Visual Basic Express editor.

              重新打开Visual Basic Express。点击【文件】>>【新建】>>选择【Windows Forms Application】。并输入工程名。

         2. View the references:
        By default your blank project was created containing a few standard project references to core .NET components. You can see these references by right-clicking the  

        project in the Solution Explorer and selecting Properties. In the Properties window select References.

 

Along with the standard references, a blank VB form is created and added to the project.  It’s this form that gets displayed in the text editor window, Form1.vb. Forms have two views, Design and Code: you can switch between the two views by right-clicking on Form1.vb in the Solution Explorer and selecting View Code or View Designer.

工程建立后,到工程属性管理界面,点击【引用】,如下图。缺省的,已经有多个.NET方面的引用。

3. Add references:
So far you have created a blank Windows Forms Application project using Visual Basic Express.

This blank Windows Forms Application project, as created by Visual Basic Express, does not automatically make use of the Inventor API. For it to do so, you need to add a project reference to the interface DLL in Inventor describing its API, Autodesk.Inventor.Interop.dll.

In the Solution Explorer, right-click the project and choose Add Reference.  Click the Browse tab in the Add Reference dialog and navigate to a location such as this beneath the installed location of Inventor on your system:

  • C:\Program Files\Autodesk\Inventor 201x\Bin\Public Assemblies

Select Autodesk.Inventor.Interop.dll and then OK.



The Inventor API has now been referenced into your project.

在属性管理【引用】>>【添加引用】, 浏览到文件夹C:\Program Files\Autodesk\Inventor 201x\Bin\Public Assemblies,选择t Autodesk.Inventor.Interop.dll,OK。这就是Inventor API库文件。有了它,就能访问到Inventor API所有对象

 

4View Object Browser:
Before proceeding further, let’s use the Object Browser in Visual Basic Express. The object browser is a tool that can help you understand how to use the objects in the Inventor API. Once you have referenced the Inventor API (Autodesk.Inventor.Interop.dll) in your project its objects can be displayed in the Object Browser. The Object Browser is a dialog containing a tree showing how various components’ objects are organized. As well as using the tree to browse the hierarchy, you can also search on the name of an object to access it directly. Once you have the object displayed and selected in the left pane of the tree view, you can see its methods and properties in the right pane. In the screenshot below, the Application object is selected in the left pane and its ActiveDocument property is selected in the right from among the object’s various properties and methods. Try selecting other properties to see their details.

Note: To display the Object Browser go to the View menu and select it. If “Object Browser” is not available on the View Menu then go to the Tools Menu, click on “Settings” and then select “Expert Settings”. Also by default the function key “F2” will display the Object Browser. (In both Expert and Basic settings).  


在菜单【视图】>>【对象查看器】,找到Autodesk.Inventor.Interop(如下图),展开它,找到Application,在右面的列表中,可以看到Application的所有成员属性和方法。其中有个ActiveDocument。有点属性吧?对!它就是在课程1里使用到的当前打开的文档。就是通过Application访问到的。

 

5. Ready to add Inventor API code:
You’re now ready to use the Inventor API by entering code in Visual Basic Express. In other words, to provide instructions telling Inventor how to perform certain tasks.

可以说到现在就是万事俱备了,只欠你自己想做的代码了。

 

6. Build the project:
While developing code, it’s a good idea to build the solution, from time to time, to check whether errors have been introduced in the code. The code does not necessarily have to be complete or functional when building the solution. This approach can help avoid potentially lengthy troubleshooting once the code is complete, and has the side benefit of automatically saving any edited source files before the build starts.

To build a solution inside Visual Basic Express, select Build <ProjectName> from the Debug pull-down menu.

这开始个空白的工程,不过你可以编译一下,看看有无什么错误。编译的快捷键是F6



Tip: As a shortcut, you can use the Function key ‘F6’ to directly build the solution without accessing the menu.

If the build was successful, you will see Build Succeeded in the status bar at the bottom-left corner of the Visual Basic Express interface.

7. Save the file:
On the File menu, click Save All. Saving the solution creates physical files representing the contents of your class library project on your computer’s hard drive, allowing you to open and edit it at another time in the future.

A quick recap: in this lesson you took a brief look at what happens when you build a project, as well as some background information on VB.NET and Visual Basic Express. You then spent some time creating a brand new Windows Forms Application project in Visual Basic Express, adding the required project reference for it to be able to use the Inventor API.

 

养成良好习惯,记住保存工程。

 

Additional Topics

Visual Basic Express vs. Visual Studio Professional

In this guide, you are using Visual Basic Express. This is a free version of Visual Studio and a great tool to help you start writing and managing Visual Basic code for your Inventor plug-in without the need for an additional software investment. Microsoft has targeted the Express editions of Visual Studio at students, hobbyists and other part-time programmers. While they provide most of the features of Visual Studio Professional, such as IntelliSense, they do have certain limitations. For instance, Visual Basic Express contains fewer project templates and has limited options for debugging and troubleshooting your code. If you are serious about plug-in development beyond this introductory guide, we recommend investing in one of the more fully-featured members of the Visual Studio product family.

这里谈到Visual Basic Express 和. Visual Studio Professional的区别。最大区别是Express (速成版)是免费的。它面向学生,开发爱好者或兼职的程序员。而Visual Studio Professional面向专职的程序员,有更多的工程模板,更多的编译选项和错误检查。

 

What is COM?

“Microsoft COM (Component Object Model) technology in the Microsoft Windows-family of Operating Systems enables software components to communicate. COM is used by developers to create re-usable software components, link components together to build applications, and take advantage of Windows services. COM objects can be created with a variety of programming languages. Object-oriented languages, such as C++, provide programming mechanisms that simplify the implementation of COM objects.” Source: MSDN Library

COM is the underlying API technology used by older versions of Visual Basic, including Visual Basic for Applications (VBA). While some Windows application developers have exposed .NET interfaces to their software, others have continued to invest in their COM interfaces, as these can also be called from .NET applications (see below for further information).

我们多次提到了Inventor是COM API。那什么是COM?COM是组件对象模型的简称。它提供的机制能够让我们创建出可重用的组件, 组件接口供其它程序使用, 以及可利用到Windows服务。COM也是很早Basic版本(包括VBA)的后台机制。更多了解请访问MSDN Library

 

What is .NET?

The .NET Framework is a software framework that sits on top of the Microsoft® Windows® operating system* and provides the underlying platform, libraries and services for all .NET applications. The services generally include memory management, garbage collection, common type system, class libraries, etc.

* Subsets of .NET are also available on other operating systems, whether via the open source Mono project or via Microsoft® Silverlight®, but these are not topics for this guide: you will focus solely on the use of .NET in the context of Microsoft Windows.

什么是.NET呢?它是一种基于Windows 操作系统的软件程序框架,提供了基于框架的类库,服务等各种内容。服务一般包括内存管理,垃圾回收,状态系统等。

 

What does the .NET Framework Contain?

The framework contains two main components:

  1. Common Language Runtime (CLR) – This is the agent (or execution engine) in the .NET Framework responsible for managing the execution of code. Which is why code written to target this runtime is also known as managed code. All managed code runs under the supervision of the CLR, but what does this mean? The CLR manages code by providing core services such as memory management (which includes automatically releasing the computer’s memory for reuse on other tasks when it is no longer needed), error (or exception) handling, managing the use of multiple threads of execution and ensuring rules around the use of different types of object are adhered to. The CLR is really the foundation of the .NET Framework.

  2. .NET Framework Class Library – As the name suggests, this is a library or collection of object types that can be used from your own code when developing .NET applications. These .NET applications are targeted for Windows (whether command-prompt based or with a graphical user interface), the web or mobile devices. This library is available to all languages using the .NET Framework.

As mentioned above, the CLR improves code robustness by making sure the executing code conforms to a common type system (CTS). The CTS ensures that all .NET (or managed) code – irrespective of the language – uses a similar set of object types and can work together in the same environment. It is this feature that makes it possible for you to write applications in the development language of your choice and yet make use of components/code written by programmers using other .NET languages.

 

.NET框架包含两个主要内容。一是一般程序运行时(CLR)。我们写出的.NET代码将交由运行时执行,所以.NET代码也叫做叫做托管代码。CLR是整个.NET的基础。二是框架类库。类库是对象集合。包含了不同种类的功能。例如System.Windows.Forms包含了对话框设计中需要的类和支持。

 

Building Executables

When you built your code into an EXE, it was compiled into Common Intermediate Language (CIL – also known as MSIL) code using the language-specific compiler. CIL is a CPU-independent set of instruction that can be executed by the CLR on Windows operating systems. CIL is typically portable across 32- and 64-bit systems and even – to some extent – to non-Windows operating systems. The CIL code generated from your VB source code was then packaged into a .NET assembly. Such an assembly is a library of CIL code stored in Portable Executable (PE) format (which contains both the CIL and its associated metadata). Assemblies can either be process assemblies (EXEs) or library assemblies (DLLs).

During the course of this guide, you will focus on developing a particular type of Inventor plug-in: a process assembly (EXE) which communicates with Inventor. Because of the overhead associated with developing them, you will not spend time looking at Inventor AddIns, which are usually library assemblies (DLLs) that get loaded into and executed within the memory space of Inventor. One reason that implementing an EXE to work with Inventor is simpler than developing an AddIn is related to its user interface: Executables do not need to integrate seamlessly with the Inventor user interface by adding ribbon buttons (for instance).

 

当我们编译代码为EXE。它将被编译到一般即时语言CIL。这是一种不依赖任何CPU的指令集合,可以由CLR得到执行。本课程系列以EXE形式和Inventor进行通信。我们将不介绍另外一种形式Dll(插件)。前者是自己独立的运行进程,而后者是运行在Inventor进程中。前面提到过,通过EXE,更方便初学者了解和使用Inventor API。

 

Running Executables

During execution of a .NET assembly, CIL (residing in the assembly) is passed through the CLR’s just-in-time (JIT) compiler to generate native (or machine) code. JIT compilation of the CIL to native code occurs when the application is executed. As not all of the code is required during execution, the JIT compiler only converts the CIL when it is needed, thus saving time and memory. It also stores any generated code in memory, making it available for subsequent use without the need to recompile.

In the last step of this process, the native code gets executed by the computer’s processor.

If you would like more details on the process of building .NET applications

 

这张图表示了代码执行的过程。编译器对原代码处理为CIL语言,然后交由CLR进行执行,最终其实都是二进制的指令序列。CPU按照指令进行执行。更多内容,参考MSDN Library.

 

如何在Inventor插件中使用InventorView控件 (即InventorViewCtrl.ocx) 两年前,我写过一篇关于 InventorViewControl.ocx不能用在Inventor进程内使用的折衷办法的文章,当时没有花时间写例子程序,只是说了一下解决方法。最近又有人问起这个问题,我索性就写了个例子程序。大家可以从下面下载:(存放在微软的云上,所以大家不需要优快云帐户也可以下载) vbAddInCallInventorViewCtrl.zip https://skydrive. 阅读详情

相关推荐

#APPINVENTOR扩展插件之MQTT

http://code.appinventor.mit.edu/http://code.appinventor.mit.edu/ 对应AI伴侣下载地址:http://code.appinventor.mit.edu/companions/MITAI2Companion.apkhttp://code.appinventor.mit.edu/companions/MITAI2Companion.apkIOT: 存放一些本科阶段做的IOT项目代码 - Gitee.comhttps://gitee.com/love

byhyf83862547的博客 4347

Inventor2022安装threadModeler插件,生成真实螺纹

在插件安装好后打开C:\ProgramData\Autodesk\ApplicationPlugins\coolOrange_threadModeler.bundle\Contents。2020以后的版本他提供了一个在线网站,我试了一下反正半天没动弹。将此处的25改为27,当然如果你是21版本就改为26。重新打开inventor会弹出一个窗口,确定就行。在工具,附加模块中将禁止去掉,加载勾选,就可以在主页看到他的选项。点击我们之前的螺纹特征,然后ok就生成好了!

Ailong2376192982的博客 3175

Inventor 二开环境配置

Autodesk.GDC_Inventor.Inventor.addin(.addin 插件说明文件一个)inventor安装的时候,会自动在GAC中添加Inventor interop library,其中Samples包含了一些插件的源码对开发指导有很大的作用。目前Inventor开发支持C++、C#、VB。Library路径:C:\Windows\。xxxaddin.dll (一个或多个)inventor版本:2020。开发环境:VS2015。

weixin_38213653的博客 1748

[如何做Inventor插件和做插件的安装程序]网络培训

我在上一篇免费的Autodesk Inventor培训课之讲义中提到第二讲【基本概念和通用的文档介绍】的讲义和录像下载地址。这一周做完了第三讲【如何做Inventor插件和做插件的安装程序】,明后天大家就可以从下面的链接来下载录像和培训用过的例子了: http://www.adskconsulting.com/adn/cs/api_course_webcast_archive.php ->选择Language为Chinese,可能会有一项"May 31 14.30 [DotNet Addin & i

CAD定制乐园 4102

Inventor SDK入门---环境搭建

Inventor SDK入门---环境搭建,快速建立一个Inventor Addin项目

guoll8952的专栏 2221

Inventor插件开发入门:从零开始创建一个简单的记事本调用插件

本文详细介绍了如何从零开始开发一个Autodesk Inventor插件,实现记事本调用功能。内容涵盖SDK环境搭建、插件项目创建、代码实现、部署调试等关键步骤,并提供了功能区按钮集成、错误处理等进阶技巧,帮助开发者快速掌握Inventor插件开发的核心流程。

convnet3designer的博客 230

My First Plug-in - Inventor API .NET 开发从0开始-课程1

首先需要安装  Autodesk® Inventor®  和  Microsoft® Visual Basic® Express。这个系列课程基于VB.NET讲解,但同时也提供了C#源码工程。所以,若用C#,需要安装Visual C# Express。安装后,启动Inventor和Visual Basic,看看有无什么问题。 课程1演示如何建立独立的EXE工程,然后连接到Inve

Gear Up Cloud 2964

Inventor齿轮绘制插件:高效机械设计解决方案

Autodesk Inventor是业界领先的3D机械设计软件之一,广泛应用于产品设计、设计验证和工程仿真。它将建模、仿真、可视化和文档编制集于一身,极大地提高了机械设计师的工作效率和设计精度。齿轮参数输入界面是用户与齿轮设计插件交互的第一步。一个直观、简洁且功能强大的界面设计对提高设计效率至关重要。它应当包括以下几个关键部分:参数字段:这部分为用户提供了输入齿轮参数的区域,如模数、齿数、压力角、齿宽等,每个字段后面跟随一个提示,解释该参数的含义以及推荐的输入范围。

weixin_30700095的博客 1849

My First Plug-in - Inventor API .NET 开发从0开始-课程3

今天我们来看课程3,深入学习代码。原文地址是 Lesson 3: A First Look at Code 文章标题是:在课程2的工程里添加一些新代码,更进一步的了解相关API Add code to the project you created in Lesson 2 In Lesson 2 you created a project and it re

Gear Up Cloud 2208

App Inventor扩展插件

最近新接触了App Inventor开发,感觉对新手开发App是比较容易上手的开发形式,App Invebtor是简单的可视化编程,相比于Android Studio是对新手比较友善,这里整理了两个常见的扩展插件,http://app.gzjkw.net/。

使用VB.Net二次開發inventor幾個例子

使用VB.Net二次開發inventor幾個例子: Analyze CustomCommand CustomEnvironment

My First Plug-in - Inventor API .NET 开发从0开始-课程4

在课程3我们创建了一个Windows Form程序, 执行一些代码. 本次课程我们将基于前面的例子, 增加一个按钮, 把课程1中隐藏选择集代码拿来执行. 这个过程中你将学习到相关代码如何工作的.  课程例子源码工程: lesson4_vb-net.zip (zip - 25Kb) lesson4_c-sharp.zip (zip - 27Kb) Coding

Gear Up Cloud 1523

揭秘N531:这颗不到2毛钱的国产栅极驱动器,如何成为功率开关的“全能搭档”?

本文深入解析了国产栅极驱动器N531如何成为功率开关的“全能搭档”。针对MOSFET和IGBT等电压驱动器件在实际应用中需要大电流实现快速开关的核心痛点,N531凭借±500mA的强劲驱动能力、宽电压供电及高兼容性,有效降低开关损耗,提升系统效率与可靠性。文章通过实战案例与设计指南,阐述了这颗高性价比芯片在简化设计、降低成本方面的显著优势。

z5a6b的博客 620

My First Plug-in - Inventor API .NET 开发从0开始-课程5

有一阵子没继续这个课程系列的翻译了。不知前面几个课程是否已经熟练掌握,今天来看看如何为对象添加属性。原文地址: Lesson 5: Adding Attributes 课程相关代码工程:  lesson5_vb-net.zip (zip - 26Kb) lesson5_c-sharp.zip (zip - 40Kb) 打开课程4的工程,进入Form1的

Gear Up Cloud 1411

Qt 5.15.2静态编译避坑实录:MinGW 32位版从源码到Creator配置的全流程踩坑总结

本文详细介绍了Qt 5.15.2 MinGW 32位版本的静态编译全流程,包括环境准备、配置参数优化、编译过程监控及安装后配置。重点解决了静态编译中的常见问题,如参数顺序敏感、路径引号问题等,并提供了性能对比实测数据,帮助开发者高效完成静态编译。

weixin_26749245的博客 271

LiteOS | 基于LiteOS的智慧农业案例实验分享

分享一个基于小熊派+LiteOS+华为云的案例实验(智慧农业)。 实验框图 相关模块简介 1、STM32L431RCT6 2、LiteOS LiteOS是华为开发的轻量级实时操作系统: LiteOS源码GitHub仓库链接: https://github.com/LiteOS/LiteOS 其源码一级目录结构如下: 其内核包括任务管理、内存管理、时间管理、通信机制、中断管理、队列管...

嵌入式大杂烩 5990

My First Plug-in - Inventor API .NET 开发从0开始

从去年开始,我们团队陆续的撰写AutoCAD,Inventor,Revit二次开发零起点教程,使用.NET。这个真正是零起点,因为即使你连Visual Studio都没摸过,都可以按照教材一步步的进入Inventor开发,享受其中的乐趣。当然更重要的是为实现你或你用户的需求打下基础。这些教程可以说是精心打造。有点遗憾内容描述只有英文。 www.autodesk.com/myfirstinvent

Gear Up Cloud 1529

YOLOv8改进,MobileNetV3轻量化架构改进特征提取网络,助力涨点

MobileNetV3通过结合硬件感知网络架构搜索(NAS)和NetAdapt算法,通过新颖的架构改进进一步提升了性能。本文开始探讨了自动化搜索算法与网络设计如何协同工作,以利用互补方法来提升整体技术水平。通过这一过程,创建了两个新的MobileNet模型:MobileNetV3-Large和MobileNetV3-Small,分别针对高资源和低资源使用场景。这些模型随后被适配并应用于目标检测和语义分割任务。

在职AI算法工程师,擅长计算机视觉,YOLO目标检测、分割等,擅长web、pyqt界面可视化,好内容持续更新中,来这里跟大家一起学习,共同进步 3835

【免费下载】 App Inventor 扩展插件集合

App Inventor 扩展插件集合 【下载地址】AppInventor扩展插件集合 本仓库提供了一个包含20多种App Inventor(AI2)扩展插件的资源文件,这些插件已经过中文整理(部分)。资源文件中包含了多种实用组件的设计,如PDF组件、手电筒、判断第一启动应用、更多按钮、侧边栏、快捷方式、定位、监控电量等...

gitblog_09761的博客 1524

基于非接触式微波雷达设计的跌倒检测预警系统【短信报警】

本项目选择基于非接触式微波雷达的跌倒检测预警装置作为技术核心,采用云帆瑞达的R60AFD1跌倒检测模组。这一模组能够根据人体的运动变化,如速度、距离和姿态等特征,判断是否发生跌倒,并可以持续监控老年人是否处于危险状态。此外,本项目还结合4G通信技术,通过Air724UG模块实现短信报警功能,一旦检测到跌倒事故,系统将自动通过4G网络向紧急联系人发送短信报警,及时通知亲属或医护人员进行救援。

1753

RAGFlow 系列教程 第14课:GraphRAG -- 知识图谱增强检索

RAGFlow v0.25.0深度解读了GraphRAG技术,通过构建知识图谱解决传统RAG在多跳推理问题上的局限。系统支持General GraphRAG和Light GraphRAG两种实现,包含四阶段构建流程:实体关系抽取、实体消解、社区检测和图持久化。核心代码位于rag/graphrag目录,采用LLM驱动的抽取机制,结合编辑距离和LLM确认的实体消解策略,以及Leiden社区检测算法。KGSearch模块通过多信号融合检索(实体+关系+N-hop+社区)实现高效查询。该系统将非结构化文本转化为可推

weixin_43674738的博客 101

免费 UGUI 插件 Inventory Master 背包系统使用方法

Inventory Master - uGUI   使用UGUI作为基础的、一款免费的UI系统插件,适用于unity5,插件提供了背包、快捷键栏、仓库、商店和工艺制造等一系列的游戏UI解决方案,并且还是免费的,在商城中直接就能下载使用 https://www.assetstore.unity3d.com/cn/#!/content/26310         先不管这款UI插件在国内的人气如

MichaelLiew的博客----VR行者 6440

YOLO与ORB-SLAM3的结合:实现动态环境下的目标检测与视觉SLAM

摘要: 本文介绍如何将YOLOv5目标检测与ORB-SLAM3视觉SLAM系统结合,实现动态环境下的机器人感知与定位。内容包括:源码下载(集成项目YOLO_ORB_SLAM3)、libtorch安装(PyTorch C++支持)、编译配置(解决路径依赖问题)、ROS环境下的部署(Noetic适配),以及使用TUM数据集的测试流程(RGB-D数据关联与运行)。重点解决编译时Torch路径错误、ROS与Anaconda冲突等问题,并展示系统运行效果。该整合方案为动态场景SLAM提供目标检测能力,未来可优化检测模

FJN110的博客 960

Inventor插件免注册

从2012开始插件可以不用注册(推荐采用)。插件向导会自动创建免注册的插件。 以前版本的插件向导会生成COM Registration代码,如下所示: 现在,从2012版本开始,插件向导将不再生成COM Registration代码,如下所示: 如何转换旧版本的插件(VB, C#, 和 C++)成为免注册插件,帮助文档有详细说明。查找register free就能找到。 现在,需要

CAD定制乐园 4809

Google Earth Engine——使用STARFM 图像融合算法将Landsat 和 MODIS 融合得出2000-2023 NDVI长时序图(空间分辨率为 30 米、时间分辨率为 16 天)

非本地入侵物种是全球生态系统面临的主要威胁之一。野葛(Pueraria montana)是一种生长迅速的藤本植物,原产于亚洲,现已入侵美国一些地区,因此该物种的管理成为一个重要问题。利用 Landsat 和 MODIS 平台收集的数据,计算了 2000 年至 2015 年肯塔基州三个侵扰地点的归一化差异植被指数(NDVI)估算值。使用 STARFM 图像融合算法将大地遥感卫星和 MODIS 得出的 NDVI 结合成空间分辨率为 30 米、时间分辨率为 16 天的时间序列。

此星光明博客 2509

霍尼韦尔SoftMaster使用说明

霍尼韦尔SoftMaster使用说明

【免费下载】 App Inventor 扩展插件集合:提升开发效率的利器

App Inventor 扩展插件集合:提升开发效率的利器 【下载地址】AppInventor扩展插件集合 本仓库提供了一个包含20多种App Inventor(AI2)扩展插件的资源文件,这些插件已经过中文整理(部分)。资源文件中包含了多种实用组件的设计,如PDF组件、手电筒、判断第一启动应用、更多按钮、侧边栏、快捷方...

gitblog_09755的博客 2073

温度PID控制PLC程序

温度PID稳定控制程序,适用于欧姆龙PLC,对其他PLC也具有很大参考价值

上一篇: My First Plug-in - Inventor API .NET 开发从0开始-课程1
下一篇: iProperties 简述
autodeskinventorapi
博客等级 码龄14年 313粉丝 164原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值