今天在看Vision的时候，发现Clamp.llb中封装了10个函数，但是在程序框图中的可选项只有5个函数，这是为什么？？？例如： Overlay Line with Arrows.vi
2019-11-01 13:33
annoying problem. When working in the Layout mode the Arrows which represent the ports are huge.
2019-01-09 15:21
Micro:bit的板载应用主要包括：图像、文本、数学、游戏。
2020-11-06 07:55
我有一个显示ERR303和ERR304的8562a表示解锁状态。这通常是A14板或YTO的问题吗？ 300MHz校准信号接近但不准确，关闭几Mhz，其他一切似乎都在工作。任何帮助，建议欢迎...... Bob bfehn在metcom dot org 以上来自于谷歌翻译 以下为原文I have an 8562a that shows ERR303 and ERR304 indicating an unlock condition. Is this typically an issue on the A14 board or, the YTO?300MHz cal signal is close but not exact, off by a few Mhz, everything else appears to be working. Any help, suggestions welcome... Bob bfehn at metcom dot org
2019-04-15 09:26
嗨！我想知道它是否可以在程序内存窗口中放大？（图片）同样，当我用光标移动窗口-GT时，有几次像图片2中出现的东西。它让我一遍又一遍地点击我想要的选项。 以上来自于百度翻译 以下为原文 Hi, there!I'm wondering if it could zoom in in the program memory window?(picture) Also, there are several times that something occurs like picture 2 when I had my cursor to move window -> any option with arrow. It had me to repeat again and again to click the option which I wanted. Attached Image(s)
2019-02-14 15:13
you then move the mouse cursor to any of the choices with little arrows next to them (indicating
2019-06-28 10:51
我设计了一个小型板使用MCP30F521芯片来监测交流线路电压和功率。I2C接口运行良好，我指示芯片从RMS电压寄存器开始读取24个字节（0x18），90%的时间得到预期结果，24个字节加上3个字节用于芯片ACK/NACK字节、字节计数和校验和。校验和匹配，并且显示在将来的控制方案中使用的数据。每秒读取一次数据。我看到的其他90%的时间对我来说完全没有意义。正常数据读取具有0x06字节第一（ACK），然后字节数为27（0x1b），然后是数据和校验和。我在坏数据中看到的是ACK字节是正确的，但是字节数的下一个字节可以或多或少地小于正确的数字。我的代码仍然读取27字节，但显然数据需要被拒绝。我的逻辑分析器的时序和响应对于好的和坏的读数都是相同的，但是数据都是错误的，有时坏数据看起来是移位的，其他时候它是完全的垃圾。有没有人看到过这样的事情，发现了一个原因或工作？多谢 以上来自于百度翻译 以下为原文 I have designed a small board using the MCP39F521 chip to monitor AC line voltage and power. The I2C interface is running well, I am instructing the chip to read back 24 bytes (0x18) starting at the RMS Voltage register and 90% of the time I am getting the expected results, 24 bytes with the extra 3 bytes for the chip ACK/NAK byte, byte count, and checksum. Checksums match and I display the data which will be used in a future control scheme. The data is read back once per second. What I see the other 90% of the time makes absolutely no sense to me ... Normal data reads have the 0x06 byte first (ACK), then the number of bytes at 27 (0x1B), then the data, and the checksum. What I see on bad data reads is that the ACK byte is correct, but then the next byte for the number of bytes can be more or less than the correct number. My code still reads back the 27 bytes but obviously the data needs to be rejected. The timing and responses on my logic analyser appear the same for both good and bad reads, but the data is all wrong, sometimes the bad data appears to be shifted, other times it is complete garbage. Has anyone seen anything like this and found a cause or a work around? Thanks In Advance Larry Attached Image(s)
2018-10-18 16:02
在前一个MPLA8XX中，如果我停止调试，我可以重新启动调试而不重新编译所有代码并重新编程。MPLAB X IDE上有可能吗？ 以上来自于百度翻译 以下为原文 In the previous MPLAB 8.xx if I stop the debug I can restart the debug without recompile all the code and reprogram again.Is it that possible on MPLAB X IDE?
2018-09-26 17:26
): undefined reference to `stdscr'scripts/kconfig/lxdialog/checklist.o: In function `print_arrows
2022-11-25 07:38
/kconfig/lxdialog/checklist.o: In function `print_arrows':checklist.c:(.text+0x2c): undefined reference
2022-01-13 09:30
