Announcement

Collapse
No announcement yet.

OpenComportTerm broken ?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    OpenComportTerm broken ?

    I just realized some of my COM devices are not updated anymore, maybe after recents updates.
    I have been using for years in my startup.vb:
    hs.OpenComPortTerm(6,"1200,E,7,1",1,"teleinfo_COM.vb","logda ta",chr(&H02))

    I have checked the com, using hyperterminal : the com port is working and the data is OK.
    So I guess there is "something" broken with the hs.OpenComPortTerm().

    Has anyone any equivalent problem with hs.OpenComPortTerm ?
    Visit zee e-maison : http://www.e-maison.com

    #2
    It appears to be working here. Is it just some of your ports, or every one that you open with hs.OpenComPortTerm? What version of HS?
    Mike____________________________________________________________ __________________
    HS3 Pro Edition 3.0.0.548, NUC i3

    HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF | RFXCOM | Vantage Pro | Green-Eye | Edgeport/8 | Way2Call | Ecobee3 | EtherRain | Ubiquiti

    Comment


      #3
      I am using ver 3.0.0.425.
      I am using only one com port, where I can receive data using hyperterminal.
      For testing, does someone has a small script or oneliner that can read and log everything on a com port ,not taking care of a end of message ?
      It will help testing without having to script again...
      Visit zee e-maison : http://www.e-maison.com

      Comment


        #4
        Sorry, don't have the logging script you are looking for. Could the problem be v425 related?
        Mike____________________________________________________________ __________________
        HS3 Pro Edition 3.0.0.548, NUC i3

        HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF | RFXCOM | Vantage Pro | Green-Eye | Edgeport/8 | Way2Call | Ecobee3 | EtherRain | Ubiquiti

        Comment

        Working...
        X