Discussion in 'International Area' started by dirtyballs, Jan 12, 2011.

  1. dirtyballs

    dirtyballs New Member

    I have a nice software idea that uses the openformat description files ( delivered with logview ) to
    get data form diffent type of chargers. Mad a parser for the description file mad a serial reader and
    to my surprise, I found out that the data coming from my 208B , doesn't match the data described
    in "Junsi iCharger 208B.ini".

    Here an image of the logview with the serial data.
    strang_values.jpg

    Looking in "Junsi iCharger 208B.ini" See below
    I see that parameter 5 and 6 are Power and Energy, You see in the data that these values
    are cell1 and cell2 voltage, what is going on here the logview software views is correct, even
    the power that is not in the serial data is displayed correct.

    I see
    - Time
    - input Voltage
    - Charge voltage
    - Current
    - Cell1 to 8 voltage
    - temp 1
    - temp 2
    - Capacity
    - CRC

    What is going on here, in this way the ini files are not reusable ?

    Messgröße5 = Power
    Einheit5 = W
    Symbol5 = P
    Faktor5 =
    OffsetWert5 =
    OffsetSumme5 =

    Messgröße6 = Energy
    Einheit6 = Wh
    Symbol6 = E
    Faktor6 =
    OffsetWert6 =
    OffsetSumme6 =
  2. dirtyballs

    dirtyballs New Member

    changed the file and did a run with openformat and it worked
    very strange ?

    Code:
    [Gerät]
    #######################################################################
    ##               Junsi - iCharge 208B Einstellungen                  ##
    #######################################################################
    ## Welches Gerät ist angeschlossen?                                  ##
    Name                            = Junsi iCharger 208B
    Hersteller                      = Junsi
    ## 01 - Ladegeräte   02 - Datenlogger   03 - Lipo Balancer           ##
    ## 04 - Stromsenken  05 - Netzteile    06 - GPS                     ##
    ## 07 - Empfänger    08 - Multimeter                                 ##
    Gruppe                          = 01
    Device_ID                       = ID_OPENFORMAT
    ## 1=in LV verwendet    0 = NICHT verwendet                          ##
    Used                            = 1
    Abbildung                       = Junsi iCharger 208B.jpg
    ChangeSettings                  = 1
    HerstellerLink1                 = www.jun-si.com
    HerstellerLink2                 = www.hillrc.com
    LogViewLink                     = www.logview.info
    TimeStep_ms                     = 2000
    TimeGiven                       = 0
    KanalAnzahl                     = 1
    WerteFormat                     = ASCII
    Prüfsummenberechnung            = XOR
    AutoStart                       = 0
    AutoOpenToolbox                 = 0
    ShowPortSettings                = 0
    DateTimeFormat                  = R_%hh"h" %nn"m" %ss"s"
    
    [Stati]
    StatiAnzahl                     = 12
    001                             = charging
    002                             = discharging
    003                             = monitor
    004                             = waiting
    005                             = test motor
    006                             = done
    007                             = error
    008                             = lixx trickle
    009                             = Nixx trickle
    010                             = foam cut
    011                             = info
    012                             = ex-discharging
    
    [serielle Schnittstelle]
    ## Konfiguration der seriellen Schnittstelle                         ##
    ## Der Port steht in der Settings.INI !! > globale Einstellung       ##
    ## Stopbits: 0=1 Stopbit, 1 = 1.5 Stopbits, 2 = 2 Stopbits           ##
    ## Parität:  0=None, 1 = Odd, 2 = Even, 3 = Mark, 4 = Space          ##
    ## Flussko.  0=None, 1 = Xon / Xoff, 2 = Hardware                    ##
    Baudrate                        = 128000
    Datenbits                       = 8
    Stopbits                        = 0
    Parität                         = 0
    Flusskontrolle                  = 0
    ## ClusterSize negativ bedeutet variable ClusterSize !!              ##
    ## Bei variabler ClusterSize wird hier der erwartete Maximalwert     ##
    ## mitnegativem Vorzeichen angegeben!!                               ##
    ## (Bei Unsicherheit lieber etwas mehr)                              ##
    ## ClusterSize null bedeutet ClusterSize unbekannt!!                 ##
    ClusterSize                     = -150
    SetDTR                          = 0
    SetRTS                          = 0
    
    [Schnittstelle TimeOuts]
    ## DelayTime :      in Mikrosekunden                                 ##
    ## ExtraDelayTime : in Millisekunden                                 ##
    RTOCharDelayTime                = 2000
    RTOExtraDelayTime               = 800
    WTOCharDelayTime                = 290
    WTOExtraDelayTime               = 100
    
    [Anzeige Einstellungen Kanal 01]
    Zeitbasis                       = Zeit
    Einheit                         = s
    Symbol                          = t
    WerteAnzahl                     = 15
    
    Messgröße1                      = Input
    Einheit1                        = V
    Symbol1                         = U
    Faktor1                         = 0.001
    OffsetWert1                     = 0.0
    OffsetSumme1                    = 0.0
    
    Messgröße2                      = Voltage accu
    Einheit2                        = V
    Symbol2                         = U
    Faktor2                         = 0.001
    OffsetWert2                     = 0.0
    OffsetSumme2                    = 0.0
    
    Messgröße3                      = Current
    Einheit3                        = A
    Symbol3                         = I
    Faktor3                         = 0.01
    OffsetWert3                     = 0.0
    OffsetSumme3                    = 0.0
    
    Messgröße4                      = Cell 1
    Einheit4                        = V
    Symbol4                         = U
    Faktor4                         = 0.001
    OffsetWert4                     = 0.0
    OffsetSumme4                    = 0.0
    
    OneAxisName4                    = Cell 1-8
    OneAxisGroup4                   = 1
    
    Messgröße5                      = Cell 2
    Einheit5                        = V
    Symbol5                         = U
    Faktor5                         = 0.001
    OffsetWert5                     = 0.0
    OffsetSumme5                    = 0.0
    
    OneAxisGroup5                   = 1
    
    Messgröße6                      = Cell 3
    Einheit6                        = V
    Symbol6                         = U
    Faktor6                         = 0.001
    OffsetWert6                     = 0.0
    OffsetSumme6                    = 0.0
    
    OneAxisGroup6                   = 1
    
    Messgröße7                      = Cell 4
    Einheit7                        = V
    Symbol7                         = U
    Faktor7                         = 0.001
    OffsetWert7                     = 0.0
    OffsetSumme7                    = 0.0
    
    OneAxisGroup7                   = 1
    
    Messgröße8                      = Cell 5
    Einheit8                        = V
    Symbol8                         = U
    Faktor8                         = 0.001
    OffsetWert8                     = 0.0
    OffsetSumme8                    = 0.0
    
    OneAxisGroup8                   = 1
    
    Messgröße9                      = Cell 6
    Einheit9                        = V
    Symbol9                         = U
    Faktor9                         = 0.001
    OffsetWert9                     = 0.0
    OffsetSumme9                    = 0.0
    
    OneAxisGroup9                   = 1
    
    Messgröße10                     = Cell 7
    Einheit10                       = V
    Symbol10                        = U
    Faktor10                        = 0.001
    OffsetWert10                    = 0.0
    OffsetSumme10                   = 0.0
    
    OneAxisGroup10                  = 1
    
    Messgröße11                     = Cell 8
    Einheit11                       = V
    Symbol11                        = U
    Faktor11                        = 0.001
    OffsetWert11                    = 0.0
    OffsetSumme11                   = 0.0
    
    OneAxisGroup11                  = 1
    
    Messgröße12                     = Int. Temperatur
    Einheit12                       = °C
    Symbol12                        = T
    Faktor12                        = 0.1
    OffsetWert12                    = 0.0
    OffsetSumme12                   = 0.0
    
    OneAxisName12                   = Int./Ext. Temperatur
    OneAxisGroup12                  = 2
    
    Messgröße13                     = Ext. Temperatur
    Einheit13                       = °C
    Symbol13                        = T
    Faktor13                        = 0.1
    OffsetWert13                    = 0.0
    OffsetSumme13                   = 0.0
    
    OneAxisGroup13                  = 2
    
    Messgröße14                     = Capacity
    Einheit14                       = mAh
    Symbol14                        = Cap
    Faktor14                        = 1.0
    OffsetWert14                    = 0.0
    OffsetSumme14                   = 0.0
    
    
  3. Dominik

    Dominik Administrator Staff Member

    In the past the Junsi used the OpenFormat.
    Now we have a direct implementation whoch is slightly different.
  4. dirtyballs

    dirtyballs New Member

    Oke, but is there a list from chargers that don't have an direct implementation, I am asking this because I would like to reuse the ini files
    I am making a remoter server that handles the data on a PC/netbook and this data then can be viewed via wifi on a android smart telephone
    Here a movie connect to a FMA PL8
    http://www.youtube.com/watch?v=XbhofURjnjM&feature=player_embedded

    DB
  5. Dominik

    Dominik Administrator Staff Member

    Hi !

    All devices which come with LogView have a direct implementation !
  6. dirtyballs

    dirtyballs New Member

    So you define an openformat, and you don't even use it your self, why should other people use it :)

    If I could reuse the INI I would have stuck to German but I have to make all the ini files my self now and they will be in English. Because that is a way bigger market then germany

    Openformat should be treated way differently then you do. It's was a good Idea but not any more.

    DB
  7. Dominik

    Dominik Administrator Staff Member

    Hi !

    The OpenFormat comes out much later. And the intention is to give developers a solution to implement their own devices.
    I think you don´t have really understood the openformat base idea ...

    If it´s not useable for you I can´t change that ...
    There are many people who use the OpenFormat. So it couldn´t be as bad as you write it here.
  8. dirtyballs

    dirtyballs New Member

    :)

    I understood it compactly, The openformat is not only that what comes over the communication port, but is also the description. Take the iChargers, they are perfect openformat, what do you do, make an internal parser for the ichargers and leave the open format parser. The result, an INI file that doen't represent the communication of the ICharger.
    The result is that I have to wrtie a new openformat ini file for the Ichargers to parse the data from the icharger, because logview didn't treat the icharger as an openformat device.

    I will make INI files that can be used by other openformat software (with English parser). The ini files from logview can't, because they don't represent the data from the Icharger.

    Tell me, who doesn't understand the openformat I or you. :confused:

    DB
  9. Dominik

    Dominik Administrator Staff Member

    Hi !

    Listen .. OpenFormat was nerver designed to use for normal devices. It is an developing tool for users with their own hardware.

    And the INI files where nerver designed to represent and describe the whole data protocoll.

    And one other thing ... The OpenFormat is not designed to implement unknown devices like chargers in LogView which have a given data protocol! If the device don´t use the OpenFormat specification you can´t use OpenFormat. It´s that simple.

    To be honest I don´t understand your problem. If the OpenFormat don´t fit your needs you have to do something by your own.
  10. dirtyballs

    dirtyballs New Member

    > To be honest I don´t understand your problem

    apparently we have sime king of languish barrier :)

    Let me try it in a different way.

    I am implementing a program that needs the data from battery chargers. To make this data available via wifi for a smart phone to show the process. a number of the chargers are open format ( as the ichargers ). Beside the Ichargers I don't know any other openformat charers because I don't have these chargers. I thought that the ini file would give me a description of the data because Open format is implemented in logview
    openformat charger --> logview , expected openformat description in the ini file. ( not the case )

    To let the charger wifi extender to work for more then only the Icharger I need the data description of the other, openformat chargers. You know that data. Again I expected that data in the ini files of the openformat chargers. As this data is not in the ini files, I want to ask you if there is any way you are willing to share the ( openformat protocols )

    Below the current implementation
    Icharger -> USB -> PC -> wifi -> smart phone ( information about charging process )
    http://www.youtube.com/watch?v=TBAn3CKycxA

    I you are not willing, I need to get the protocols from the manufactures. Big problem is I don't even know the chargers that are using open format ?

    DB,

Share This Page