Kwon, The schematic can be located here: e2e.ti.com/.../744269 I will follow-up with the team that owns the source for firmware to get this provided to you. I will send it to you via email. Regards, Wade
↧
Forum Post: RE: ADS1278-EP: information about MMB0 modular EVM motherboad of ADS1278 EVM
↧
Forum Post: DAC38RF82: External Reference
Part Number: DAC38RF82 Hello Team, the DAC38RF82 has a built-in reference voltage for the DAC core of 0.9V. The reference voltage can be measured on the pin EXTIO. According to the datasheet, this pin is I/O. Is it possible to use an external 0.9V as reference voltage? What are the current drive requirements for an external reference to override the internal reference? Thanks and Best Regards, Hans
↧
↧
Forum Post: RE: TINA/Spice/ADS1298: ADS1298
Hi Mes, Happy to help! Ah I see, I didn't know that you built it into the write function. //[ datgaValue - 1 (in decimal)*LSB size]/gain, where LSB size = VREF/(2^23-1) - in voltage is technically incorrect since the LSB size will be multiplied by 1 before getting subtracted from the dataValue. It should be this: (Code (decimal) - 1) x LSB / Gain = Volts e2e.ti.com/.../1363393
↧
Forum Post: RE: DAC38RF84: DAC38RF84
Jim, Thanks for your reply. I write a "0" to 0x05 every time before reading it. And now when I read 0x05, I get a value 0xfa, the last 3 bits are "010" which I think is expected, and the PLL_LFVOLT is 3, so I think the pll is locked. The problem now is why I get a value 0xfa instead of 0x02 when reading 0x05? Bits 8:3 are all ones, what does this mean? Regards, Rita
↧
Forum Post: RE: ADS1220: ADS1220 install issue
Hi Alex, On Win7, the driver should install as a part of the ADS1220EVM plugin installation. There could be several reasons why there may be an issue with not finding the ADS1220EVM . The most common issue we have seen in the past is the EVM is not an ADS1220EVM , but rather an ADS1120EVM . Make sure that the actual IC device is marked ADS1220 . Second possibility is the ADCPro plugin is started before the EVM is plugged into the PC. Make sure that the EVM is plugged into the PC before the ADCPro plugin is started. If you are using an extender cable from the PC to the EVM this may be an issue as the cable may be preventing the EVM from enumerating on the USB bus correctly. Try plugging in the EVM directly to the PC USB port if you are currently using a cable. Third possibility is the ADS1220EVM is not being correctly powered. Make sure you see 2 green power LEDs lit, and that the jumpers are in the correct positions as detailed in the EVM user's guide. The best place to try to determine why you might be having a problem is to check the connection from the Device Manager in windows. You can find the Device Manager in the Control Panel on Win7. As I stated in my previous post, you should see a virtual COM port device added to the list of COM port devices. What the ADCPro ADS1220 plugin does when it is first started is to make a list of all available COM ports. From the list of ports, the plugin will attempt to connect to the ports one at a time and look for a return message of ADS1220 . If the auto discovery works, then the plugin will use that port and continue. If it does not get the proper return message it will try the next available port. When you see the message that you have displayed with the pop-up that appears to manually connect to a port, this means that the plugin was not able to auto connect. So the best place to start is to check to see if the EVM was able to connect to the PC. This will help tell us where to troubleshoot next. Best regards, Bob B
↧
↧
Forum Post: RE: DAC38RF84: DAC38RF84
Jim, And I found strange problems about the pins GPO0, GPIO1, SYNC0+/- and SYNC1+/-. According to the datasheet, the output of pins GPO0, GPIO1, SYNC0+/- and SYNC1+/- can be selected by register 0x01. When I write 0x0080 to register 0x01, I think GPO0, GPIO1, SYNC0+/- and SYNC1+/- are all supposed to be low. But when I checked it in FPGA using chipscope, I found that GPO0 and GPIO1 is low, but SYNC0+/- and SYNC1+/- is high. And when I write 0xff80 to register 0x01, GPO0 , SYNC0+/- and SYNC1+/- are high but GPIO1 is still low. I think this is not right, GPIO1 and GPO0 should have the same output. So why is GPIO1 always low and why are SYNC0+/- and SYNC1+/- always high? I think maybe there are something wrong in the hardware, please help me figure out where is wrong. Regards, Rita
↧
Forum Post: RE: DAC38RF84: DAC38RF84
Jim, I attached the schematics of my board. Would you please help me to check if the design of DAC is right or not? Thanks a lot. Regards, Rita (Please visit the site to view this file)(Please visit the site to view this file)(Please visit the site to view this file)(Please visit the site to view this file)
↧
Forum Post: RE: ADS1293: ADS1293 3-Lead ECG noise
Hello Shih, Using the RC filter from the ADS1298EVM is fine. This is certainly 60Hz noise that should be canceled out, however something that I didn't notice from your registers in my last post is that the ID register 0x40h is not reading back correctly. I also noticed that in register 0x17h, the analog pace output is connected to RLDIN, try disabling this. Can you verify that the common mode voltage is present on the IN4 pin? If you change the register so that RLD is output to IN5, do you see the common mode voltage on IN5? I found a couple of posts that may help: e2e.ti.com/.../2026199 e2e.ti.com/.../1046151
↧
Forum Post: RE: ADS1298R: the amplitude of test signal is wrong
Hi Max, Thanks for your post! The PACE_OUT should be (0.4*PGA_GAIN) and is also dependent on the input signal applied to the channel. A couple of posts that may help: e2e.ti.com/.../224498 e2e.ti.com/.../119171
↧
↧
Forum Post: RE: ADS1246: ADS1246 with 3.3V AVDD
Hi Leo, Thanks for your post and welcome to the forum! If you take a look at the Device Comparison Table, you will see that the ADS1246 does not have an internal reference. Unfortunately this means that the ADS1246 is not ideal for load cell applications since the excitation voltage should be the same as the reference. For the ADS1246 , the reference must be less than AVDD-1V, so the maximum reference voltage is 2.3V. I encourage you to explore a few other parts in the portfolio: The highest precision devices for load cell applications while still being relatively low cost are the: ADS1230 (20-bit) ADS1232 (24-bit) ADS1231 (24-bit) Higher cost and higher speed would be: ADS1220 ADS1235 ADS124S06 There are advantages/disadvantages to each one. The top group is precision at the sacrifice of speed (max of 80sps) but are very simple to operate as well (no registers and pin controlled only.)
↧
Forum Post: DAC38RF82: DAC test thread, will delete
Part Number: DAC38RF82 Dac test thread, will delete TI>COM LINK http://www.ti.com/product/DAC38RF82/technicaldocuments
↧
Forum Post: RE: ADS8350: VOL with external pull-up
Hi Oba, Your understanding is correct. Thank you for the interest in the ADS8350 !
↧
Forum Post: RE: CCS/ADS8699: ADS8699 SPI DMA example c code
Hi, in the c code you can see the new pin configuration. I extended it with the RVS signal. 1. I want to use the max. SPI speed of 16MHz. I'm not really sure about the constant: /* SPI Master Configuration Parameter */ const eUSCI_SPI_MasterConfig spiMasterConfig = { EUSCI_B_SPI_CLOCKSOURCE_SMCLK, // SMCLK Clock Source 3000000, // clockSourceFrequency: SMCLK = DCO = 3MHz 16000000, // desiredSpiClock: SPICLK = 16MHz EUSCI_B_SPI_MSB_FIRST, // MSB First EUSCI_B_SPI_PHASE_DATA_CHANGED_ONFIRST_CAPTURED_ON_NEXT, // Phase EUSCI_B_SPI_CLOCKPOLARITY_INACTIVITY_LOW, // low polarity EUSCI_B_SPI_3PIN // 3Wire SPI Mode }; Which/what clock ist the clockSourceFrequency? I only can choose SMCLK and ACLK. Furthermore, I can't recognise a clock at pin 1.5 with a oscilloscope while the while loop (se below) is running. Because of this, I think there is something wrong with the clock setting. 2. In reference to p.11 fig. 1 and 3 I made a simple test sequence: while(1) { // conversion start with rising edge on CONV: GPIO_setOutputLowOnPin(GPIO_PORT_P4, GPIO_PIN3); GPIO_setOutputHighOnPin(GPIO_PORT_P4, GPIO_PIN3); // Wait until conversion is done (RVS -> high): while (GPIO_getInputPinValue(GPIO_PORT_P4, GPIO_PIN6) == 0); // set CONV to low for reading buffer: GPIO_setOutputLowOnPin(GPIO_PORT_P4, GPIO_PIN3); int k; for (k = 0; k < 4; ++k) { RXData[k] = SPI_receiveData(EUSCI_B0_BASE); } } But everytime I read with SPI_receiveData 0x0000311C. The value never changes. What's wrong? Regards
↧
↧
Forum Post: RE: DDC264: DDC264EVM
Hi David, Thanks for using DDC264EVM . According to our engineering manager here: Could you please copy the USB_IO_for_VB6.dll to the following directory location in your PC? C:\Users\ \AppData\Local\Apps\2.0\ \ \ddc2..tion_ f0cdf37a7314ad51_0001.0000_542e76346161ac81 The text highlighted in red could be different on the customer’s PC. This should most probably fix the error "Unhandled exception has occurred ..... Please try it. Hope this can help. Thank you and best regards, Chen
↧
Forum Post: RE: ADS8900B: What is the use of pattern registers?
Hi Venkatesh, Yes, DATA_PATN[19:0] is a fixed pattern that can be selected for the output by setting the DATA_VAL bit, per Figure 43 in the datasheet. This can be helpful in testing the digital interface between the ADS8900B and the host controller. Regards, Keith N. Precision ADC Applications
↧
Forum Post: RE: Downloading DXP
Arash, I have seen the setup work on Windows 10, but I think the main issue at this point is how the installer is actually navigating / negotiating with the Windows file-system given all possible IT-oriented permutations which PCs can be deployed with, particularly in a corporate / business environment. What we mean to say is the Software was extensively tested and deployed for Windows 7, but not maintained through Windows 10. Right now we are "testing the waters" with a new platform. Pending acceptance there, we will be migrating old tools to the new platform which will support Windows 10 in addition to Linux and Mac operating systems. The other potential issue is that these tools leverage resources from National Instruments which occasionally have their own compatibility issues, specifically the NI VISA driver. Based on your error message I could see potential for there to be a NI VISA contention if you have other LV RunTimes etc. installed on that PC.
↧
Forum Post: RE: ADS7961: ADCPro Timeout
Arash, A colleague pointed me to a newer post that he thinks is a bit more complete. It's for a different board, but it should be the same setup. e2e.ti.com/.../656505 The board should enumerate as an NI-VISA device when plugged in (If this doesn't happen, you'll need the NI-VISA driver). When you run ADCPro it should download the firmware. At that point in device manager, the board should disconnect and reenumerate as a USBStyx device. If this doesn't happen, then you'll need the libusb-win32-bin-1.2.6.0 driver. Regardless, read through the post, try it out, and let me know. Joseph Wu
↧
↧
Forum Post: RE: ADS5263: 16 bits mode
Hi Gauthier, How are you? Thanks for using ADS5263 device. For this question, first, please look at the ADS5263 schematics from the User's Guide on the TI website. When you don't plan to use 14bit mode (such as INxB_P and INxB_M input pins) and want to short these input pins to ground. Then, we suggest please connect these INxB_P and INxB_M pins with each pin connected to a 0.1uF cap in series to Ground Plane. Thanks and best regards, Chen
↧
Forum Post: ADS1148: unable to clock out conversion result
Part Number: ADS1148 I am controlling the chip with an arduino Uno Rev3. The arduino built-in SPI interface did not work for me for some reason; therefore, I'm using bit banging for all spi communications. The code was based on the pseudocode provided in the datasheet. I have attached the code and the scope captures at the bottom of this post. - Able to write to the registers and did a sanity check by reading back the registers. - Pulsed the START pin high to start the conversion - DRDY pin did go low after start pin pulsed high - polling for DRDY 0 instead of an interrupt - DRDY did force high on the first falling clock edge - sent the RDATA command and 16 clks afterwards to try to clock out the conversion data... however MISO just kept returning 0 - everything seems to be working but I just cannot clock out the result!! Please provide some assistance. Thanks in advance. scope captures: https://www.dropbox.com/s/bj81xcmidpah292/scope%20captures.pdf?dl=0 arduino code: https://www.dropbox.com/s/et9cm1jrhfwir3u/adc.zip?dl=0
↧
Forum Post: RE: ADS8900B: SPI interface compatibility with Xilinx AXI Quad SPI IP
Hi Praveen, I suggest reaching out to Xilinx on the details of configuring the IP module. For quad SPI, the ADS8900B requires at least 5 SCLK's to clock out the reading result or register contents (Table 7 in the datasheet). If you also want to read the parity bits, then 6 SCLK's are needed. If you want to keep the data transfer to a standard 8 bits, you can use 8 SCLK's. When reading the conversion result, you can hold the ADS8900B SDI input either high or low. In order to write to the internal registers, you must clock at least 22 bits into SDI. You can clock more than 22 bits, i.e., 24bits, by adding two zeros and then the 22b command, per Tables 2 and 4 in the datasheet. As long as the Xilinx core is flexible enough to read 5-8b in quad, MISO mode and write 22-24b in single, MOSI mode, you should be able to get it to work. Regards, Keith N. Precision ADC Applications
↧