tag 标签: arduino

相关帖子
相关博文
  • 热度 2
    2020-3-28 21:43
    1253 次阅读|
    0 个评论
    一、1602LCD简介 液晶显示器简称LCD。 1602液晶也叫1602字符型液晶,是指显示的内容为16X2(即可显示两行,每行16个字符)的液晶模块。 使用1602液晶制作的显示器也就叫做1602LCD。 1602LCD可以工作在3.3v或者5v的电压条件下,但最佳工作电压为5v。工作在5v的条件下,工作电流为2mA。 1602LCD模块有16个引脚,每个引脚的功能如下: 1.VSS:接电源地。 2.VCC:接5v电源。 3.V0 :对比度调整端,一般串联变阻器接入来调节LCD的对比度。 4.RS :寄存器选择,高电平时选择数据寄存器,低电平时选择指令寄存器。 5.R/W:读/写信号线,高电平时进行读操作,低电平时进行写操作。 6.E:使能端,高电平时读取信息,负跳变时执行指令。 7.D0~D7:8位双向数据传输段。 8.A/K:背光正/负极。 1602LCD具体信息百度搜索1602LCD数据手册。 二、基于Arduino的使用 首先Arduino的IDE是有LiquidCrystal库的,另外其本身也带有示例程序。 比如display "Hello,World!": // include the library code: #include // initialize the library by associating any needed LCD interface pin // with the arduino pin number it is connected to const int rs = 12, en = 11, d4 = 5, d5 = 4, d6 = 3, d7 = 2;//此时只用到了D4~D7的引脚 LiquidCrystal lcd(rs, en, d4, d5, d6, d7); void setup() { // set up the LCD's number of columns and rows: lcd.begin(16, 2); // Print a message to the LCD. lcd.print("hello, world!"); } void loop() { // set the cursor to column 0, line 1 // (note: line 1 is the second row, since counting begins with 0): lcd.setCursor(0, 1); // print the number of seconds since reset: lcd.print(millis() / 1000); } 具体的使用方法可以打开Arduino\libraries\LiquidCrystal\src路径中LiquidCrystal.cpp以及LiquidCrystal.h文件阅读底层代码。
  • 热度 5
    2015-12-16 09:41
    1425 次阅读|
    2 个评论
    本文转自雷锋网硬创邦,作者吴攀。编者注:本项目来自Instructables,作者Smudger_WTH利用3D打印和基于Arduino的机器人程序开发一个能够行走,也能够变成机器小车的“变形金刚”;其通过安卓手机的蓝牙连接进行控制。作者为其起名为蜘蛛机器人(Spiderbot),下面我们就来看看这只变形蜘蛛是怎么炼成的。 第一步:准备工作 电子组件: Arduino Nano 12个EMAX ES08MA II舵机 Adafruit 16信道12位PWM/伺服驱动 蓝牙HC-05模组 电机驱动L293D 4个300RPM 6V N20直流电机(带橡胶轮胎) Hobbywing UBEC-8A2-6S 电子调速器(UBEC) Wild Scorpion 7.4V 2200mAh LiPo电池和对应的电池接头 6cm x 9.5cm PCB板 2个LED灯 线材等 结构材料: 50枚M2 x 10mm圆头螺丝 30枚M1.2 x 6mm沉头自攻螺钉 少量扎带 3D打印组件 第二步:3D打印结构 本项目的大部分结构部件都是利用3D打印技术制作完成的,具体的文件点击  3D_Print_Parts_STL.rar 下载,其中包含8个独立的文件,打印数量如下: base.stl 基板x1 cover.stl 盖板x1 coxa.stl 髋板x2 coxa_mirror.stl 髋板固定x2 femur.stl 股板x4 motorMount.stl 电机安装板x4 tibia.stl 胫板x2 tibia_mirror.stl 胫板固定x2 第三步:安装结构 使用M1.2 x 6mm的螺丝将4个股板做好,并将舵机臂安装到基板上。 使用M2螺丝将舵机安装到髋板和胫板上。 将带轮子的N20直流电机安装到胫板上,这里使用M2螺丝和电机安装板进行固定。 注意电机和舵机的方向。 第四步:制作PCB并焊接电子件 电子组件的连接图如下,我们需要为这些连接制作一块PCB板。 PCB板的设计(下载 PDF文件 或 PCB文件 ),其尺寸为6cm x 9.5cm。 制作成功的PCB。 安装各个部件,这里安装了6条线:2条5V、2条接地、Arduino Rx-HC-05 Tx和Arduino Tx-HC-05 Rx。 安装开关。 将两个LED分别串联一个电阻后并联起来,它们将作为机器人的两只眼睛。 最后,将电子调速器(UBEC)连接到6V输出,并将UBEC的输出连接到16信道伺服驱动。 第五步:连接舵机和电机 将舵机连接到板上。舵机有三条线,其中棕色是地线,红色接V+,黄色是PWM。 为了和后面的程序匹配,这里选择的连接方式是: 左前腿舵机是0,1,2; 右前腿舵机是4,5,6; 左后腿舵机是8,9,10; 右后腿舵机是12,13,14; 另外,接口3,11,15空接;接口7用于LED的PWM调制。 然后将控制4个轮子的4个电机和PCB上的电机焊接起来,一共8个接口。 第六步:写入代码并调试 这里的代码需要用到 Adafruit_PWMServoDriver 舵机驱动库,其安装方法点击 这里 查看。 库安装完成后,就可以开始编译代码了。另外注意一点:在使用USB为Arduino Nano写入代码时,注意不要将其它供电组件连接到Arduino上。点击 spiderbot_servo.rar 下载代码。 代码上传完成后,接好断开的线就可以打开电源了。 设备启动时,所有的舵机都会回归到“0”位点,最后会呈现下图的模样:髋板与基板成45度角,股板与髋板成30度角,而胫板竖直略向外。如果样子不同,那就需要进行适当的调整,调整过程中不需要断电。另外,你也可以通过调节Arduino代码中的偏移值对其进行校准。 接下来在底面固定电池。 第七步:调试机器人的运动 你可以在Arduino代码的主循环函数中单独调用单个函数来对机器人进行调试。 void loop() {   //去掉函数前面的双斜杠即可单独调用该函数   //forward();   //backward();   //left();   //right();   //vehicle(); } 如果运动方式不对,进行相应的调节即可。在汽车模式下,机器人的腿应该像下图一样折叠起来。注意折叠起来之后不要对舵机的运动构成阻碍,一旦你听到异常响亮的噪声,很可能是舵机负载过大,这时应该切断电源。 至于机器人的步态(creep gait),看起来有些奇怪,但机器人运动学不是本项目的主题,详情你可以点击 这里 了解。简单来说,就是在一只脚抬起的时候,另外三只脚必须在地面以保持平衡和稳定。你也可以在Arduino代码中对步态进行调节,让它看起来更优雅一点。 最后你也可以修改代码中mleft()和mright()函数中的参数修改汽车模式下机器人左转右转的角度。 第八步:安装安卓软件并连接蓝牙 本项目的安卓程序是作者自己编写的,界面比较简单,只有左下角的运动控制和右下角的变形按钮。另外需要注意的一点是,如果你没有进行修改,该蓝牙设备的初始名字应该是HC-05,初始密码是1234. 本安卓程序的源代码在 这里 下载,编译好的APK文件则可点击 这里 下载。 第九步:安装盖板,完成 将LED穿过盖板上的孔,盖紧盖板就完成了,接下来开始试玩,跑起来还真够奇葩的!
  • 热度 1
    2015-6-1 19:48
    1161 次阅读|
    0 个评论
    Ever since I’ve known Max, I have figured that there is no keeping up with him or even beating him -- that is until now when he challenged me to a design-off contest  over who could build the best pixel ring clock . So I thought to give it a whirl.   This is a work in progress. Comments are welcome.   Hardware I thought my clock’s display should be quite active when running, understand what I say to it, have capacitive-sense touch buttons that also would know when it was touched anywhere, and have a speech and audio playback synthesizer to complete the communication-to-human part of the beast. Lastly and obviously, no clock would be complete without a time-keeping mechanism, so a clock/calendar is included.   I ended up with the following for hardware and will give my reasoning: Arduino Leonardo . The UNO and Mega have a USB to TTL chip that connects to the hardware serial port, which ties up the hardware serial port that I want to use to talk to the voice recognition system. The alternative is using the software serial interface, which might work if changed to be interrupt driven – however, my clock is going to be too busy to have to take on this overhead. Available from SparkFun , the Leonardo has the USB built into the processor, which frees up the hardware serial port. It also makes the ‘bridge’ function to connect the PC to the voice system simple and easier to share with the debug-serial I/O console built into the compiler environment, not to mention that it also runs 115k baud with minimal overhead.   ChronoDot clock/calendar , available from Adafruit , was almost a no-brainer. It interfaces to the I2C wire bus, is very low power, and keeps outstandingly accurate time. Also it comes with the obvious other things required, such as the button-cell battery, for example.   EasyVR shield V3 , from Veear and available from Sparkfun . This little beauty is both a speech recognition engine and a sound player in one. Having extensive support and library, this board-shield offloads the Arduino from what would otherwise be an impossible task for the 16 MHz memory-limited processor. The hardware can be run in standalone PC mode, as well as ride on the Arduino, to make it easier to develop an operating environment. Its separate commander software that runs on the PC makes the job of teaching the device words (speaker dependent) and then downloading them a breeze. For Arduino code development, there are very good examples to use. Lastly, for speaker-independent additional-word supplements, a software tool can be purchased.   Groove Q-touch sensor , from EpicTinker , has the following features: Shares the I2C bus nicely, has 7 separate very noise-tolerant capacitive inputs, self calibrates, and is very small itself. For debug, three of the buttons can optionally be used already configured on the board’s underside.   The concentric, three pixel rings , which are 60 pixels for the outside-most ring, 24-pixel ring for the middle, and a 12-ring for the inside-most ring, make a tasty clock. This makes the minutes and seconds share the outside ring, the 24-ring for hours when in the 24-hour mode, and lastly the 12-ring to display the hours in 12-hour mode. Having the extra unused ring depending on the mode, allows it to be used for AM/PM indication, and status display of other clock functions such as voice, for example.   Power supply . An external power supply is required, since all-white/all-on and fully-bright pixels draw considerable amps. I chose the Recom Power RAC60-05S/OF  from Digi-key . It has room to grow at 10 amps, is relatively small, and is only about $21. One down-side note to mention however, is that whenever the supply draws more than a few amps, it ‘sings’ a bit, which could get a tad annoying if it turns out to be loud enough after mounting it inside the clock.   To get started: I hooked everything up as mentioned, and used digital pins 4, 7, and 8 for the 60-ring, 24-ring, and 12-ring respectively. I left the pullup resistors for the I2C bus installed on the Q-touch, because I changed the I2C library away from using the standard WIRE library, and the replacement didn’t enable the internal pullups. I will discuss this library replacement later.   Software At first it seemed logical to try to use everything stock and standard, as supplied by the manufacturers of each of the respective pieces, to save time and keep it simple, clean, and understandable. However, it quickly became apparent that to have a dynamic real-time display, something like an interrupt-driven task manager would make things work better. The manager would not need to be a full up pre-emptive multitasker operating system, but could be a single-level interrupting scheduler. Hunting around for exactly that on the web, I landed on something that was an outstanding multitasker  but wasn’t interrupt driven. To overcome this problem, I thought to give it a try as a quick poll in loop(), then add the interrupts as necessary. To its credit, this library is very full featured, having things like run once, run every time on a time, run a certain number of times, oscillate, pulse, stop, update, and find free event index. I found the   t.every( xMilliseconds, routineName, number-of-times)   quite useful, where it calls the routinenamed  every x milliseconds  for number-of-times and then stops.   All tasks are sampled to see if the timers are to be triggered for calls, each time the t.update() is run. As nice as this was to use, it had the down-side that PWM, millis() and other internal timer delays, as well as other timer library functions were not useable. So rather than expend energy to add interrupts, I thought to look for another solution that was already interrupt-driven, which led me to LeOS (little embedded Operating System) . While this was not as full featured, and lacked the run number-of-times item I wanted, it did have everything else, including interrupts, task restart, task change, etc. Much later on I would also discover, to my chagrin, that this scheduler was not compatible with the NeoPixel and WIRE I2C libraries, causing me to hunt/replace these with something that would work. To these ends I first found the Neopixel replacement, light_WS2812  which worked well enough, even though it was a very basic engine. Next I found the replacement for the I2C  which allowed to disable interrupts, set speed, and other nice things, but which mainly was compatible with LeOS. I did notice that this library didn’t enable the internal pullups, so I went to make sure there were external ones provided on at least one of the boards connected to the bus, rather than spend the time to find the software fix. After substituting appropriately this softI2C master to the function calls to the ChronoDot, I thought to tackle the touch controller, which I had working originally using the Wire library, prior to integrating LeOS. This was not to be.   At this point, I had a beautifully spinning and whirring display, eloquently running, voice recognition accepting a trigger-speech command, and responding with speaking the current time. However, I couldn’t get the I2C library swapped out for the WIRE library on the calls to the touch controller. It seems that the trouble lies in the compiler’s insistence that the I2C be declared in proper scope inside the touch controller’s library, where the I2C is itself a library. All the techniques I usually use to resolve such issues, such as pulling the code out of the library up to the top-level sketch, for example, have failed.   Some of you who read this, may have discovered a few OTHER quirks with the otherwise nice compiler. As an example that I ran across on this project, I had a function called serialIN(), which worked just fine as the code steadily grew, but then suddenly the compiler began complaining that serialIN was not defined in this scope. I worked for hours trying to fix this, until I accidentally renamed it to iserialIN(), which made the compiler happy! Now mind you, the serialIN was not a keyword (Serial.xxx with the capitol ‘S’ is a keyword, as it would indicate this by a change of text color). There were no constructors, classes or anything else that I could find, having been added, to cause the error. Not having much more patience to bear, I left it like this and decided to move on.   To solve this last seemingly insurmountable problem (to me) with the I2C library replacement for the touch controller, I welcome any ‘C’ guru to take a look at this and offer a suggestion/fix. I will supply the appropriate code snippets for all who brave forward.   iframe width="400" height="360" src="https://www.youtube.com/embed/Ov1ZI26uTFI?feature=player_embedded" frameborder="0" allowfullscreen/iframe   By the way, I have included a video of what I have so far, for you who are interested to drool over, or cry, as appropriate.   Thanks in advance!   Ivan Cowie
  • 热度 1
    2014-4-5 18:29
    621 次阅读|
    0 个评论
    Mastro Gippo's friend, who is blind, had requested for his help in locating a multimeter that could speak. What Mastro found was that they were quite expensive. The only meter he located cost over $2,000. Being the kind of guy who builds things in his spare time, he decided he wasn't going to just accept that cost, he would build one instead . He knew he could find a relatively cheap multimeter with serial output. His idea was to read the serial output with an Arduino, then spit out the corresponding audio. Ideally, this would all be packaged in a nice little container for portability. Mastro was in luck. He found a small MP3 player that could charge over USB, had a built-in speaker, auxiliary input, and extra space in the case. He ripped open the MP3 player, crammed in his Arduino Pro Mini and SD card reader, and reassembled it. By using the Super Simple SDaudio Library, he was able to get the audio output he needed for the MP3 player. As you can see in the video, the entire setup seems to work quite well. I don't speak Italian, so I can't vouch for the enunciation of the spoken words, but it sounds loud enough, and the package isn't too cumbersome. Of course, after he was finished, he noticed that there are, in fact, several cheap speaking multimeters on the market. At this point, that has become somewhat irrelevant! Caleb Kraft, Chief Community Editor, EE Times
  • 热度 3
    2013-12-23 21:26
    1392 次阅读|
    0 个评论
    Just in case you haven't heard by now, fearless EE Times Editor Max Maxfield is building himself an Arduino-based robot . My part in Max's master plan, as discussed below, will be to help him implement his ultrasonic distance ranging sensors. Max wrote about these in his blog, A Sensor for All Seasons. Since that time, we've been bouncing ideas back and forth with regard to connecting the sensors to his Arduino. To refresh your memory, Max wants to load up on ultrasonic rangefinders as one technique to maintain good situational analysis. The sensors Max picked—the SRF04 type (sometimes shown without the F as SR04)—are "cheap-and cheerful" and can be obtained for only a few dollars (the price on Amazon goes up and down like a yo-yo, but you can usually obtain these sensors for less than $3 apiece). Of course, you get what you pay for. The reason SRF04s are so cheap is that they don't have an onboard MCU; instead, they rely on the host MCU for all of their control and processing. The host MCU has to trigger an ultrasonic "ping," then time the delay between the ping and the return echo, and then use this delay to calculate the distance between the sensor and the object it's detected. The host MCU has to do this for each ultrasonic sensor, as well as managing all other aspects of the robot. This works reasonably well for a small number of sensors, and most robots would typically only have one or two such sensors mounted on the front. The thing is that Max's three-wheeled robot platform can scoot around in any direction, which means it has no "front." This explains why he wants to have multiple sensors mounted around the periphery of his platform. The problem here is that when you start to add more and more sensors, the host MCU can very quickly use up all of its processing power servicing the sensors. When that happens, there's nothing left over for any other "robotic things." Thus, my mission was to offload the ranging burden without incurring too much cost. For my own robot project, I've been experimenting with a related model of ultrasonic sensor, the SRF08. The '08 has an onboard PIC MCU to deal with the timing and the conversion of time into distance. It communicates over I2C in a "fire-and-forget" mode. An I2C command from the host MCU will instruct the sensor to initiate the ping, after which the host MCU can go about its business without the need to watch and wait for the echo return. Another I2C command sometime later will retrieve the distance measurement from the sensor. Here is a front view of one of my original '08 modules:   The two "cans" are the ultrasonic transmitter and receiver. The small part, between the two, near the top, is a CdS light-controlled resistor. The on-board MCU and a bunch of other bits and pieces are found on the backside of the module as illustrated below:   The downside is that the '08 is considerably more expensive than the '04. When Max and I looked recently, the best price we could find was around $55 for each '08 module. Since Max is talking about having nine ultrasonic sensors on his robot, this could quickly become a very expensive hobby. Fortunately (certainly for Max), my own robot project will be able to help here. I plan to use an FPGA to talk to a large number of sensors simultaneously. In order to make this possible, I need each of my sensors to have a small on-board MCU and to communicate over I2C. Key to this concept is the availability of an inexpensive sensor-to-I2C board. Since I couldn't find anything commercially available that satisfied my requirements, I whipped up my own board. Conveniently, this little board will be perfect for Max to use with his '04s. In fact, the image below shows an '04 (on the left) plugged into one of my boards:   There's nothing at all complex about my board—its main feature is a small PIC12F1840 MCU and some connectors. For the purposes of these discussions, imagine my board in the above image to be rotated 90 degrees clockwise such that the 4/5 double row of holes (with the '04 plugged into the row for 4 holes) are at the top. The '04 uses a four-pin connector, while the slightly more sophisticated SRF05 uses a five-pin connector, hence the 4/5 double row of holes at the top of my board. If we keep on visualizing my board in the image above as being rotated 90 degrees clockwise, then the six pins on the right are for programming. Meanwhile, the connector on the left can be I2C or SPI. The three-pin connector in the middle of the board (just under the 4/5 double row of holes) is designed to accept an analogue IR ranging sensor (but not at the same time as an '04 or '05, of course). Finally, the five-pin connector at the bottom of the board is the I2C interface to the host MCU. The clever thing is that this is presented with exactly the same pin-out as an SRF08 (the LED, just right of the MCU, is connected to the trigger line). The idea is that, in its default configuration, my board—which costs only around $3 fully populated—can be used to make a $3 '04 or '05 sensor behave just like a $55 '08 module. When I proudly presented the above image to Max, his immediate response was "That looks very nice, but where are the mounting holes?" Welcome to Revision 1.1:   First, this new version has mounting holes (never design a board for Max without mounting holes). Also, it has two more LEDs (as a general rule of thumb, you can't have too many LEDs on a board intended for Max). In addition to the trigger indicator, we now have an LED on the echo line and a power-on indicator LED on the back side of the board. (The echo LED has a jumper inline so it can be disabled when using the analogue input.) By the time I'm finished with this and Max is happily roboting away, maybe I'll have the FPGA on my own robot ready to accept a dozen of these little boards. Duane Benson Marketing Manager Screaming Circuits  
相关资源
  • 所需E币: 0
    时间: 2020-12-26 22:44
    大小: 8.53MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 22:27
    大小: 1.39MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 0
    时间: 2020-12-26 22:28
    大小: 2.28MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 0
    时间: 2020-12-26 22:32
    大小: 94.99KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 22:40
    大小: 1.28MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 0
    时间: 2020-12-26 22:41
    大小: 1.99MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 22:43
    大小: 10.66MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 0
    时间: 2020-12-26 22:43
    大小: 339.14KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:03
    大小: 1.17MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:36
    大小: 415.5KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:36
    大小: 1.04MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:28
    大小: 450KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:37
    大小: 1.02MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:28
    大小: 1.98MB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:38
    大小: 523.5KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:29
    大小: 349.5KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:38
    大小: 340.5KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:29
    大小: 885KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:39
    大小: 442KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
  • 所需E币: 1
    时间: 2020-12-26 23:30
    大小: 593KB
    上传者: Argent
    喜欢Arduino开发的工程师有福咯,本人收集了一些有关Arduino开发的综合资料,Arduino是一个准标准的软硬件开发平台,类似VC开发Windows软件一样的平台,集成各类库文件。ArduinoIDE可以在Windows、MacintoshOSX、Linux三大主流操作系统上运行。
广告