Arduino uno not connect with quickeval software

Question

Hi i use a arduino uno with FT232RL from ftdi chip for convert UART to USB as Linduino use, i upload to my arduino the sketchbook DC590B and i can take the message "hello" from my serial port wich that mean sketchbook have successfully upoload and work , but the problem is that can not connect with QuickEval software, where is the problem? 
 thanks

MarkThoren · Accepted Answer

No problem! this was a nice trip down almost 20 years of Linear Tech / ADI demo board history)

MarkThoren · Answer

Hi Yiannis, 
 So QuikEval and the individual, part-specific example sketches are mutually exclusive. QuikEval requires that the "DC590 emulator" sketch be loaded: 
 https://github.com/analogdevicesinc/Linduino/blob/master/LTSketchbook/Utilities/DC590B/DC590B.ino 
 This sketch is a command interpreter and not really useful aside from using with QuikEval. 
 The idea is, get the hardware up and running with QuikEval GUI, then move on to the part-specific sketch for further application development. 
 What eval board are you connecting the Linduino to? Note that QuikEval will not do anything without an additional eval board connected, as it queries an identification EEPROM. But you do say that you see the "hello" message in the terminal, which is to be expected from the DC590 emulator, so perhaps this is the problem? 
 Another possibility - are you trying to run QuikEval with the Arduino terminal open? If so, the terminal will claim the USB serial port, and QuikEval won't be able to access it. Try closing the terminal, and the Arduino IDE, too, just to be extra sure. 
 A screenshot, and even a photo of your setup may also help. 
 -Mark

MarkThoren · Answer

Realizing I overlooked the consequences of your Arduino setup. QuikEval also requires that the FTDI chip have the following string for a description: 
 USB SERIAL CONTROLLER 
 You would need to download the FTprog utility from FTDI to program this in. But if this does not work right away, there might be some other subtlety that I haven't thought of. 
 Even after getting that sorted out, you'd need to either wire your ARduino's I2C bus to the eval board's EEPROM, or implement a hack in the DC590 emulator that's not terribly difficult, but might not be worth the effort. 
 Again, depending on which part you're using, the QuikEval GUI may just be intended to show signs of life and basic functionality. (Not always true though.) The part-specific drivers and code examples tend to be much more useful. And once we know which part you're using, we can move the discussion to the appropriate product forum. 
 -Mark

MarkThoren · Answer

Hi Yiannis, 
 So QuikEval is attempting to connect to a demo board, but you still have not told us what demo board you are connecting to. QuikEval will only work with certain product demo boards, and they all have an identification EEPROM that is pre-programmed when the board is tested. 
 We need to know which demo board you are using, or at least which product you are attempting to communicate with. 
 -Mark

MarkThoren · Answer

Okay now we are getting somewhere. To clarify - QuikEval requires that the DC590B emulator sketch be loaded: 
 https://github.com/analogdevicesinc/Linduino/blob/master/LTSketchbook/Utilities/DC590B/DC590B.ino 
 But I think you've got that right. 
 Do the following - after the "hello" message, type in a lower-case "i", which should return an ID string for the DC590B sketch. NEXT - type in an UPPER-case "I", which SHOULD return an ID string from the board. But this will ONLY happen if your Arduino Uno's I2C bus is connected to the dc1894's EEPROM, and the EEPROM is powered properly. 
 So could you double-check that you've made these connections? Refer to pins 9, 10, 11, 12 on J2. 
 If this does not work right away, send a photograph of your Arduino - dc1894 connections. You should use short wires, and make sure Arduino ground is well-connected to DC1894 ground. 
 -Mark

MarkThoren · Answer

Hi Yiannis, 
 You have the right idea - when you connect your Uno's SDA/SCL to the EEPROM on the DC1894, you should be able to execute the "I" command, and QuikEval should bring up the correct GUI. 
 But I'll give you another option - occasionally we've gotten requests for a workaround so that the EEPROM is not required, as sometimes the GUI can be a useful debugging aid during development. There is an alternative "enhanced" DC590 sketch that should be backwards compatible with the standard one, which supports "spoofing" the EEPROM. See: 
 https://github.com/analogdevicesinc/Linduino/blob/master/LTSketchbook/Utilities/DC590B_enhanced/DC590B_enhanced.ino#L63 
 I tracked down the ID for your board, try adding this: 
 //#define spoof_board_id "LTC6804-1,Cls,D6804-1,01,01,DC,DC1894A,---------" 
 at line 71, then upload to your Arduino. 
 If neither of these work, we'll have to move this over to the support forum for the LTC6804. And if it ends up taking too much time and effort, the best thing might be to just get an actual Linduino board. 
 
 Mark

MarkThoren · Answer

That's great! Glad to hear you're up and running. 
 Here's the strings I was able to turn up: 
 LTC6811-1,Cls,D6811-1,01,01,DC,DC2259A,--------- 
 LTC6811-2,Cls,D6811-2,01,01,DC,DC2260A,--------- 
 LTC6813-1,Cls,D6813-1,01,01,DC,DC2350A,--------- 
 I don't see a string for the LTC6812 though - they SHOULD be all in the same internal database, but this is an old "ecosystem" so things may have drifted a bit. 
 Could you post a new question in the Battery Management System Q&A? 
 
 Or alternatively, see if hooking up your Arduino's I2C bus to the ID EEPROM works, noting that you should revert to the "standard" DC590 emulator sketch. 
 Run the "I" command and save the string, just in case you want to use with the "spoof" technique. 
 -Mark

MarkThoren · Answer

Glad I can be of help. I don't fully understand your question - what do you mean by download a folder? If you mean "spoofing" the EEPROM string for additional boards to get the GUI to load, this should be fine. But you might want to make a couple of copies of the "enhanced" DC590 sketch (which will have to live in their own folders to keep the Arduino IDE happy), to help stay organized. Or you can just put all strings into a single sketch, and leave only one un-commented, whichever works better for you. 
 Is your end goal to use the example Linduino drivers in your end system, and port the examples to some other processor? It sounds like you are able to use the GUI effectively, but often times the purpose of a GUI is to get signs of life, basic evaluation, then throw it away and move to writing your own firmware. 
 At this point - I'm at the end of my knowledge about these parts. I can continue to help trying to get the "infrastructure" to do what you want in this conversation. But if you have follow on questions about specific details, better to start a new thread in the battery management forum: 
 ez.analog.com/.../ 
 -Mark

MarkThoren · Answer

Gotcha! I think I see what you mean. I believe SOME evaluation board manuals point to the individual installer files, but I took a quick look at one of the LTC6804 and didn't find it. 
 jeremy.sorensen , do we have a list of installers published somewhere? 
 
 -Mark

MarkThoren · Answer

And Jeremy pointed out the obvious - Page 3 in the demo manual says: 
 "The LTC6804 Graphic User Interface (GUI) is provided in a zipped file, LTC6804_GUI_Vxx_yyyymmdd.zip" 
 And the link is here: 
 https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/dc1942c.html#eb-relatedsoftware 
 Apparently the main purpose of installing QuikEval is to get the drivers installed (there are a couple of Legacy Linear Tech programs that install the same set of drivers), after which, I believe you don't have to run QuikEval any more, just pay attention to where the GUI was installed. 
 -Mark

MarkThoren · Answer

Looks like that was answered here: 
 https://ez.analog.com/power/battery-management-system/f/qa/541510/dc2259a-gui-zip-file 
 Good luck!

Partner Forums

Partner Libraries

Thread Details

Arduino uno not connect with quickeval software

Thread Summary