Post Go back to editing

Arduino uno not connect with quickeval software

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?


  • Hi Yiannis,

    So QuikEval and the individual, part-specific example sketches are mutually exclusive. QuikEval requires that the "DC590 emulator" sketch be loaded:

    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.


  • Realizing I overlooked the consequences of your Arduino setup. QuikEval also requires that the FTDI chip have the following string for a description:


    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.


  • HI Mark and thanks for your help! i make the change you ask me to FT232RL and i change it from "FT232 USB UART" as was to "USB SERIAL CONTROLLER" and yes i see a difference action:
    1) first its take about 15 sec to take from QuickEval the message " The Usb to Serial controller not connected" and only RX pin of arduino led blink, before the change i take the above message in zero time like not connect nothinc on USB port.
    2) two times was connect after ten times tray and i take the message " Usb Controller connected but not board find" and disconnect after from maybe 2 or 3 seconds.

  • 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.



    The prodcut wich tray to communicate is the ltc6804-1wich i have communicate with arduino when upload the sketchbook dc1894 and via usb i can reed the cell voltage and etc, i will send the screen shot.

    So always i have connection when upload the DC590b and take the message "HELLO"  and when upload DC1894 to my arduino i can connect with LTC6804.

    To mension when i change the description to FT232 the rx led of arduino was first time blink every time to tray to connect with QuickEval wich not happen before.

    so the problem now is that not always have connection with QuickEval wich must be and if not have any product connect to arduino to take the message " usb to serial controller has been found but the evaluthion board is not connected"


  • Here its some screenshot:

    arduino with DC590B

    Arduino with DC590B

    Arduino with DC1894

    Arduino with DC1894 :reed cells from LTC6804-1"


    First time connection with QuickEval



  • Here is some screenshot how EEPROM of my ft232 is:

    Thanks Mark

Reply Children
  • Okay now we are getting somewhere. To clarify - QuikEval requires that the DC590B emulator sketch be loaded:

    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.


  • Hi Mark and sorry for late replay!


    This is a screenshot  by type "i" when DC590B scketchbook upload to arduino  without  board LTC6804 connected.

    Now i want to understant , must be type "l" when DC590B is loaded to arduino and LTC6804 board is connected ? or when DC1894 is loaded  and LTC6804 board is connected? ( i do that tomorrow because i have LTC6804 board to my job)

    Thanks a lot Mark

  • 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:

    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.


  • Hi Mark!

    Great success! its work!

    the first time i type with "//" and not work, after i relase my mystake and type without and work.

    I post some screenshot so another people here can help from this

    I would like to ask you aslo wich is ID for LTC6811-1 , LTC6812-1, LTC6813-1 BOARDS because i want to work with this new chips.

    Thanks a lot Mark great job! keep doing this!

  • That's great! Glad to hear you're up and running.

    Here's the strings I was able to turn up:




    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.


  • Hi Mark i don't have words to thank you.
    To mention that i use my own board with LTC6804-1 and without EEPROM..
    It possible to i download the similar folder for 6811?(LTC/MultiCellbatteryMonitor/LTC6804) from a specific adress or i must to do the above procidure and automatically folder downloaded as i do for LTC6804?
    Thanks a lot Mark!

  • 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:


  • Hi Mark

    My goal was to use sketchbook of Linduino to Arduino uno and use GUI with my own boards of LTC6804 and LTC6811 to understant better how its work all things together, so latter to make somothing similar acording to me needs, with your help my goal was achieved.

    About folder:

    when i added the id //#define spoof_board_id "LTC6804-1,Cls,D6804-1,01,01,DC,DC1894A,---------" on line 71 of"enhanced" DC590 sketch and run the GUI, automatically was start a instalation of LTC6804,( can see the screenshot) my question is if i can to that by manually to find and install that.

    thanks a lot mark!

  • 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.

    , do we have a list of installers published somewhere?


  • 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,"

    And the link is here:

    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.