Announcement

Collapse
No announcement yet.

Cannot connect to Hc2a-s RH probe

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

  • Cannot connect to Hc2a-s RH probe

    Hi,
    I cannot connect ot the Hc2a-S probe either using Putty or simple serial read via labview. I connected to the sensor using the process and settings outlined in https://blog.rotronic.com/2014/07/22/technical-note-1-digital-integration-of-rotronic-devices/ Tried sending a simple read data cmd {b01RDD} via putty. But there is no response. The same when I tried to do send the same cmd via labview's serial read-write control object. Has anyone used this probe? Or did someone encounter a similar issue?

    Thank you,
    Charlie
    Last edited by charl1e; 31-10-2022, 19:36.

  • #2
    Hi Charlie

    Im not sure if your command string has a typo, but it should be { 01RDD}. And you need to bee sure, that 01 is the right address of the probe.
    As a command I would send { 99RDD}. Since 99 is the broadcast address on which all devices answer, you ensure that the probe answers if it recieves the command.

    Regards

    Comment


    • KeiBock
      KeiBock commented
      Editing a comment
      No, the probe returns the data in ASCII code. Withe the serial settings in Putty, it should display correctly

    • charl1e
      charl1e commented
      Editing a comment
      Thanks KeiBock! I got it to work with Putty. Will give my labview script a try.
      Regards,
      Charlie

    • charl1e
      charl1e commented
      Editing a comment
      Got it to work in Labview as well. Thanks again KeiBock

  • #3
    Originally posted by charl1e View Post
    Hi,
    I cannot connect ot the Hc2a-S probe either using Putty or simple serial read via labview. I connected to the sensor using the process and settings outlined in https://blog.rotronic.com/2014/07/22/technical-note-1-digital-integration-of-rotronic-devices/cluster rush​Tried sending a simple read data cmd {b01RDD} via putty. But there is no response. The same when I tried to do send the same cmd via labview's serial read-write control object. Has anyone used this probe? Or did someone encounter a similar issue?

    Thank you,
    Charlie
    Hi Charlie,

    It sounds like you're having trouble with the serial communication to the HC2A-S. I'd double-check the serial settings (baud rate, parity, etc.), as these need to match exactly with the probe's specifications. You might also want to try sending the command with or without curly braces or adding a small delay between sending the command and reading the response. If you're using PuTTY, switching to something like RealTerm could help isolate the issue. Finally, make sure the sensor is powered properly and connected to the correct COM port.

    If that doesn't work, contacting Rotronic support could provide more specific troubleshooting.

    Hope that helps!

    Comment


    • #4


      It sounds frustrating not to get a response from the Hc2a-S probe. Have you checked if the device is powered and properly connected? Sometimes, connectivity issues can be as puzzling as finding hidden Easter eggs in FNAF ! Additionally, verify the COM port settings and try a different baud rate. It might also help to reinstall the drivers or consult the manufacturer’s support. Good luck!

      Comment


      • #5
        Originally posted by charl1e View Post
        Hi,
        I cannot connect ot the Hc2a-S probe either using Putty or simple serial read via labview. I connected to the sensor using the process and settings outlined in https://blog.rotronic.com/2014/07/22/technical-note-1-digital-integration-of-rotronic-devices/ slopeTried sending a simple read data cmd {b01RDD} via putty. But there is no response. The same when I tried to do send the same cmd via labview's serial read-write control object. Has anyone used this probe? Or did someone encounter a similar issue?

        Thank you,
        Charlie
        The probe has a UART interface, so it needs a compatible USB-to-serial adapter. Verify the probe is powered. The HC2A-S typically draws power through the connection (e.g., 3.3–5 VDC), so if you’re using a Rotronic cable, it should handle this. Check for any loose connections or damage to the cable/probe.

        Comment


        • #6


          Interesting issue! Have you checked the wiring thoroughly? Also, verify the baud rate & parity settings. Perhaps a slightly delayed response is throwing off LabVIEW? It reminds me of the frantic pace in Papa's Pizzeria when orders are backing up! If the probe is brand new, ensure it's properly calibrated out-of-the-box. Good luck troubleshooting!

          Comment

          Working...
          X