Is C code or other readable format available for aducm350_eksp.hex? I need some education on how EKSP does its job. Thanks. Richard
I have attached a document which describes the UART protocol which is used in the EKSP and some of the commands that are available. This should enable you to communicate with the ADuCM350 over the UART/COM port. Please let me know if anything is unclear.
Moved to the correct category.
Someone here should be able to answer your question.
Is this with respect to the functionality of the AFE when using the EKSP or are you looking at the handshaking between the device and the UART/COMs port ?
If it is the AFE functionality it would make sense to move over to the AFE examples on the Software Development Kit - this will give you more flexibility and you will be able to tweak/fine tune the sequence to fit your requirements.
If it is the handshaking between the UART/COMs port and the device, I need to look into what we can share and it may take a few days to get back to you.
I'm trying to learn more about the handshaking steps whereby the UART/COM port opens and communicates with LabVIEW on the screen. I want to use LabVIEW to display a moving strip chart of the continuously changing complex impedance of a sensor. In addition, I want to write several hours of accumulating data to a flash SD card.
Any help that you can offer in this regard would be much appreciated.
Many thanks, Eoghan. Your attachment looks helpful.
An error has been found in the EKSP_UART_Protocol.pdf document above. In the serial port settings the document states "Stop Bits: None". In the EKSP UART protocol, the UART is configured with 1 stop bit. The document has been ammended and revised and is attached to this post.
I am using the evaluation kit for the ADuCM350 with the 4 wire board and evaluation software.
I just downloaded the port driver and the eval software and I get this intermittent error.
I tried the port speed at 115,200 but still get the error. Any Ideas!
I presume you mean the "UART Handshaking Error"? This is an issue that seems to affect a small number of people, but we have not been able to reproduce suffiently to implement a fix. It would appear to be a driver conflict on the PC, but we have not been able to confirm this. The best advice I can give is to move on from the evaluation software and perform your measurements in firmware using the examples in the SDK. Ultimately, this is how you will have to progress anyway in order to get the most out of the ADuCM350.
What is the USB port on the eval board for?
Is it there for to allow user applications connect to a host via USB?
The micro USB port on the motherboard connects to the USB PHY on the ADuCM350. If you build the USB MSC example in the SDK, you can see the ADuCM350 as a mass storage device on your PC when connected to this port.
Retrieving data ...