我正在使用E3645A电源作为直流电流源。在我的测量中，我必须切换电流源的极性。我有两个2位开关（用于“低”和“高”功率输出）。在切换过程中有一个“高”和“低”输出短路的时刻。可以通过短路损坏电源
2019-04-01 16:48
请教各位大神，直流伺服电机有没有280型，我查了查好像只有3645，55，70，90、110，130的呢，谢谢
2013-08-19 10:43
比如，我想让一个有3648个元素的数组的前几位和后几位是同一个采集到的数：a[0]=a[1]=a[2]=a[3]=a[4]//5个元素值皆为a[4]的值 a[3647]=a[3646]=a[3645
2018-04-07 23:34
2024-01-05 06:52
T3/E3/STS-1光纤扩展知识点总结的太棒了
2021-05-31 06:58
我正在将基于mfgr驱动程序的测试系统转换为使用VISA I / O库。系统已经可靠运行了5 - 6年，没有命令（SCPI）或时序结构发生变化，但是当我使用VISA库时，我在大约1500次操作时得到“VI_ERROR_SYSTEM_ERROR”，导致软件在2次尝试后冻结恢复。最常见的仪器是66311D电源。我知道这似乎是很多操作。这些测试涉及16个DUT，100个测试和3个温度下的4个配置操作，以及在不同温度下对所有16个DUT进行100组测量，正如我之前所说，测试已经运行了几年。一个DUT通常需要在一个温度下进行1000次仪器操作。我使用的是Windows XP SP3，Agilent I / O Library 16.1，HP 66311D，HP 53181A，Aeroflex 2945B以及一些专有夹具。我无法在Internet或任何Agilent文档中找到相关参考。任何帮助将不胜感激。 以上来自于谷歌翻译 以下为原文I am converting a mfgr driver based test system to using the VISA I/O library. The system has worked reliably for 5-6 yearsand none of the command (SCPI) or timing structurehas changed, but when I use the VISA library I get a "VI_ERROR_SYSTEM_ERROR" at about 1500 operations which causes the software to freeze after 2 tries to recover. The most common instrument involved is the 66311D power supply. I know this seems like a lot of operations. These tests involve 16 DUTs, 100 tests and 4 configuration operations at 3 temperatures and a group of 100 measurements at various temperatures for all 16 DUTs and as I indicated earlier the tests have been running for several years. One DUT typically requires 1000 instrument operations at one temperature. I am using Windows XP SP3, Agilent I/O Library 16.1, HP 66311D, HP 53181A, Aeroflex 2945B, and some proprietary fixtureing.I have been unable to find a relevant reference on the Internet or in any Agilent documentation. Any help will be appreciated.
2019-08-06 12:19
请帮帮我，我做的事情很愚蠢，我似乎找不到我做错了什么！我想建立一个现场嵌入式HV（12V PROG模式）在电路编程的PIC18F42。为了发展，我已经把我的编程电路和我插入18F45的下降到我的程序员ZIF SOCKEY程序员似乎是在工作，它似乎验证编程代码匹配英特尔16 HEX文件，但MCU编程不工作，甚至只是交换。相邻小块位置的源代码会造成不同的混沌操作。我知道我的源代码是工作的，适合于18F562从16F87工作的源代码。我知道我的编译器是OK（MaPLAB XC8）免费模式，因为我还生成了一个英特尔HEX文件编译使用一个旧的9.80版本的高科技，并得到完全相同的混乱结果，当我试图编程18F45 2。我没有任何其他编程设备，如皮卡2目前，一个皮卡来自中国的T II克隆将在40-50天内到达。我已经下载并仔细研究了18FXX2/XX8芯片（DS9566B）的Flash编程文档中所示的步骤，但是很明显，我可能做了一些非常非常错误的事情。我的问题是：（1）生成的HEX文件显示了字节T。o以小的Endiad格式书写。为了澄清这里的解释，我已经把第二行和第三行的16位单词结合起来，以便更容易查看。（当然，我的程序员使用未编辑的18F42..HEX文件）：（实际代码来自.HEX文件）：04000000 7FEF 0F09E（奇偶字节被丢弃）：10001800 FFFDFC40F0 E8CF 41F0 E0CF 42F0 F2A4 A4:1000 228 0 01D0 01D0 04D0 FE0E D76E 310E D66 E F2A4 E8:1000 38 000 01D01D058D0000 0F1BF24BF24BB54 B6C:1000、86B62B090EFB6501D01D04CD0FB6BFA2B07这是我如何使用HEX数据：上面的第3行说字节起始地址是0x28，在这行上有16个数据字节。编程序列需要在使用单P写入之前用8字节填充缓冲器。我的编程策略：我创建一个16位字，每个十六进制文字数字的每一个小字节，并把每个字放进一个数组中，数组的元素号是MCU程序存储器的字地址，例如：01D0（如上面的第3行所示）将被存储为一个16位字。在长整数数组元素中：PGM〔20〕＝0xD01；PGM〔21〕＝0xD00；PGM〔22〕＝0xD00；PGM〔23〕＝0x0EFE；//这些数组元素内容已被验证，现在我有8个字节（＝4个16位字）来填充单字节模式写入的8位写入缓冲器。 以上来自于百度翻译 以下为原文 Please help, I am doing something very stupid and I can't seem to find out what I am doing wrong! I would like to build an onsite embedded HV(12V-prog mode) in-circuit programmer for the PIC18F452. For development, I have breadboarded my programming circuit and I am plugging the 18F452 DIPs into my programmer ZIF socket My programmer seems to be working in that it seems to verify the programming code to match the Intel 16 Hex File, but the MCU programmed doesn't work, and even by just swapping positions of small adjacent pieces of the source code will cause different chaotic operation. I know my source code was working, was adapted to 18F452 from 16F887 working source code. I know my compiler is ok (MAPLAB XC8) free mode because I've also generated an Intelhex file compiled using an old 9.80 version of Hi-Tech and get exactly the same chaotic results when I attempt to program the 18F452. I don't have another programming device such as a PICkit 2 at the moment,a PICKit II clone from China is due to arrive within 40-50 days. I've download and studied carefully followed the steps shown in the Flash Programming doc for 18Fxx2/xx8 chips (DS39576B), but obviously, I am probably doing something very, very wrong. My Questions:(1) The Hex file generated shows the bytes to be written in little-endian format. To clarify my explanation here, I've parsed the 16-bit words together of the 2nd and 3rd line to make it easier to view. (Of course, my programmer works with the un-edited 18F452 .Hex file) Example:(actual code from .hex file):04000000 7FEF 00F0 9E(parity bytes discarded):10001800 FFFF D8CF 40F0 E8CF 41F0 E0CF 42F0 F2A4 A4:10002800 01D0 01D0 04D0 FE0E D76E 310E D66E F2A4 E8:1000380001D001D058D00001FB2BF24BF32BB54B6C:10004800B62B090EFB6501D001D04CD0FB6BFA2B07Here's how I work with the hex data:Line 3 above says the byte-wisestarting address is 0x28 and there are 16 data bytes on this line.The programming sequence requires a buffer to be filled with 8-bytes prior to writing using Single Panel Mode mode. My programming strategy:I create a 16-bit word with each little-endian quad of hex literal digits and place each word into an array whose element number is the word address of MCU program memory to write to.For instance: 01D0 (as shown above line 3) would be stored as a 16-bit word in a long integer array element:Pgm[20]=0xD001;Pgm[21]=0xD001;Pgm[22]=0xD004;Pgm[23]=0x0EFE;//These array element contents have been verifiedNow I have the 8-bytes (=4 16-bit words) to fill the 8-byte write buffer for a Single Panel Mode write. Am I correct so far?
2018-10-17 16:36
