Jump to content
  • Sign in or Sign up as New User

    Sign up is free and comes with benefits:

    • Post your question to the Forums
    • Download files and sample code
    • Upload files
    • Direct Message other users.
  1. Software & Hardware Discussions

    1. LabVIEW Community Edition

      LabVIEW Community Edition discussions and Arduino, Raspberry Pi and BeagleBoard interfacing with the LINX Toolkit.



    2. LabVIEW General

      Post questions here that don't fall into any other LabVIEW programming category listed below.

    3. 55,851
    4. Hardware

      Hardware problems, questions, driver development, DAQ, Sensors, GPIB, Serial, Instrument control and any hardware specific issues.

  2. Resources

    1. LabVIEW Getting Started   (5,523 visits to this link)

    2. GCentral

      This forum is to discuss issues, raise questions and hammer out ideas for the GCentral non-profit initiative.

    3. Code Repository (Certified)

      Discussions and support topics linked to the Code Repository certified code.

    4. LAVA Code on LabVIEW Tools Network

      Forum for supporting LAVA code published on the LabVIEW Tools Network

    5. Code In-Development

      Use this forum to discuss code that may or may not qualify for the code repository but you just need somewhere to upload it and share with the LabVIEW community.

    6. 2,218
  3. Community

    1. LAVA Lounge

      Enter the lounge and discuss anything and everything. Nothing is off-topic and all discussions are encouraged. Please post LabVIEW related discussions in the other forums.

    2. 3,605
    3. 1,647
  4. LAVA Site Related

    1. Site Feedback & Support

      Please post any questions, feature requests or technical issues related to the LAVA website here.

    2. Wiki Help

      Discussions about the LabVIEW Wiki, editing, organization, guidelines, etc.

  • Who's Online   0 Members, 0 Anonymous, 151 Guests (See full list)

    There are no registered users currently online

  • Forum Statistics

    Total Topics
    Total Posts

  • Member Statistics

    • Total Members
    • Most Online

    Newest Member
    reza azadi
  • Popular Contributors

  • Posts

    • this is a little ambiguous. Header Type Length Report ID Data Check Sum...Makes sense if you put commas in the right place Header Type, Length, Report ID, Data, Check Sum. If that was the case then a msg with no data would be something like 7E 03 02 18 9B Is this your interpretation or is it stated as such? Usually a checksum is a CRC. if it is a CRC-8 (there are a number of 1 byte CRCs) then the last value would be 0x29 rather than 0x9B, for example.  
    • If you know there are no more bytes in the buffer, then you can ignore that error. That is, if the packet size is fixed, and you are receiving correctly, you don't have to reach the timeout. Also, you can set the timeout to a value less than 10 seconds, if you know that all transactions occur before the time is up.   
    • hoovahh, Tried your software... It's for an different version UPS and the protocols are different. That said I just modified your software with the current protocol commands and I get the same results, read function times out. I'm leaning toward my problem is not software related, but hardware. Probably the USB to RS-232 converters I'm using. I just had a wild thought and tried to connect to the UPS using my USB to RS-232 converter and their PowerAlert software. Of course there are variables they ask you to select the communications protocol and the protocol they sent me (4001) isn't listed out of the probably 30 protocols in their dropdown. I selected a couple that sounded right but I can't connect with their software on this port either. Crossrulz, I'll ohm out the cables they sent to see if anything looks bad. Everyone, Thanks for looking and trying.. It's just really hard working from home without the proper resources to get the job done. Bob
    • Bryan, Ok... I've always said there are no stupid questions... It's protection for me when I ask that stupid question.... I looked on the back of the unit and there is only one DB9. You're right about the "dry contact" connections. They are confusing, but Tripp-Lite tech support assures me I can communicate serial on the DB9 connector. I agree, the manual, protocol documentation and tech support for purposes of software aren't very helpful.   Bob
    • That manual also mentions "included cables".  You might want to ohm out that cable to see where pins are actually going.
    • I do believe the baud is correct at 2400.  In another thread I showed OP some code I wrote here which interfaces with a Tripp Lite UPS, which worked on the ones I was using.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.