• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 47 subscribers
  • Views 6165 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ads1298 evm error code 6004

Timothy Starr
Expert 2445 points
Other Parts Discussed in Thread: ADS1298

Hello-

For my ADS1298EVM , a software error happened after driver installed during signal acquiring. Because of this error no signal appeared on the ECG screen.

The message is "An error occured with error code 6004 lvstyx.lvlib:check_styc_err.vi<ERR> cannot get a fid/ads1298evm/data

<b> Complete call chain:<b>lvstyx.lvlib:check_styx_err.vi lvstyx.lvlib:lvstyx_write_path.vi ADS1298EVM_Main.vi"

Could you suggest what might have gone wrong? Thanks,

  • 0
    TI__Expert 3260 points

    Hi Timothy,

    It sounds like you may have an old version of the evaluation software. To be sure, please ensure you have the latest software, and double check the jumpers are configured as per the User's Guide. The below link has the latest software, as well as the User's Guide:

    http://focus.ti.com/docs/toolsw/folders/print/ads1298ecgfe-pdk.html

    Hope this helps.

    Regards,

    Michael Wheeler

  • 0
    Prodigy 40 points

    hi Timothy

    I get the same error message now with my ADS1298EVM... I only have it about 2 weeks and it worked at first because I recorded some ECG signals with it. After reading the reply to your message, I downloaded the latest software and tried it with two MMB0 motherboards that I have... but it always gives the same error. The MMB0 struggles to read or write to the ADS1298 board, and gives error messages about the registers or data. Something is wrong internally with the register reading or writing... maybe it is the SPI interface itself. I also have an ADS1298RECGFE board and it works fine when connected to either of the MMB0 motherboards. At the moment I am trying to return my ADS1298ECG board as it cannot be communicated with at all no matter which motherboard I use.

    Just thought I would share my experience with this board! It is a pity that the ADS1298 chip is not placed in a removable type of socket... then we could buy new chips and easily replace them. The present chip socket arrangement is maybe good for industrial users with the right equipment, but certainly not good for semi-professional and home users with limited equipment. And replacing a complete board... when it only comes as part of a complete PDK package... is an expensive option! Though I think TI is on a winner here with this one chip that does everything idea... and congratulate them on producing such an excellent piece of kit that has so many uses.

    Regards

    Robert

  • 0 in reply to Robert Davey
    TI__Mastermind 46290 points

    Hello Robert,

    Sorry to hear about your difficulties, very interesting that it worked for a while but has since failed. Sounds like some jumper settings may be in a non-valid configuration or the board has been damaged. When does the error you're encountering occur? On start-up? Or only when you attempt to write to a register or read data?

  • 0 in reply to Kevin Duke
    Prodigy 40 points

    Hi Kevin

    Thanks for the response... the jumper idea started me thinking... and I eventually realised that when I separated the ADS1298ECGFE from the other ADS1298RECGFE, that I had not reset the main 2.048MHz oscillator jumpers. Because the 2 boards were in multiple configuration mode only one oscillator was active, so when I activated the oscillator on the ADS1298ECGFE board it worked perfectly again with the MMB0 motherboard. So the error code 6004 was of my own making, and of course related to an apparently dead or disconnected board as suggested by yourself.  I was glad that the board still worked because it showed that my multiple configuration wiring with associated microprocessor data collection setup had not done any harm, and  I could look elsewhere for reasons why my multiple configuration setup was not working. I hope this report back on my own issue will be of help to others in resolving a 6004 error.

    For the sake of others who may be attempting multiple configuration with these ADS1298ECGFE boards, let me also report briefly on how I finally got my setup working. The initial reason why I thought the ADS1298ECGFE was faulty and removed it from the multiple configuration setup to test it again with the MMB0 motherboard, was that I couldn't get the test signal to show properly on all 16 channels. It was infuriating really, some channels would show ok and others would not, and sometimes none would show. I couldn't see any reasoning to it, until I connected a logic analyser and realised that the SPI DRDY signals were not synchronised properly and the SPI CS board switching was affecting SPI commands that I was sending like SDATAC and RDATAC. Sometimes the CS would change before an SPI command was completed. So I realised there were timing issues that I had not addressed properly. The ADS1298 manual mentions such timing issues and I began to insert 'short waits' before and after CS switching and SDATAC and RDATAC commands. Eventually all 16 channels showed properly and I am very happy with my multiple configuration setup now.

    Again, just out of interest, I am using 2 ADS1298ECGFE boards connected through the SPI interface to a ByVac BV513 board containing a PIC32MX processor, connected through USART to a FTDI USB board. For data collection and analysis I am using the free OpenVibe software with a supplied driver adapted to suit my data collection which is done in 60 byte packets. The 16 channel Test signals transfer and display perfectly in OpenVibe.

    Hope this is helpful for other non-professional users like myself.

    Robert (r.davey@city.ac.uk)

     

  • 0 in reply to Robert Davey
    TI__Mastermind 46290 points

    Robert,

    Glad to hear the boards are working and that you had success with your design! Let us know if we can help you with any future work.