Announcement

Collapse
No announcement yet.

mcsTemperature Problem Reports & Feature Requests V3.11 to V3.23.0

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

    The typical problems are:
    1. Interface page has not been setup to transfer data to database at some interval
    2. Sensor page has the Quasar sensors included and a database-friendly name defined for it

    Comment


      Hi Michael, thanks for the quick answer. Appreciated !

      After severals days of testing I made progress.

      I disabled General debug log in the Temp HS-log.
      I deleted/created 4 new Devices in HS
      And I copied and old mscTemperature.mdb to the newly installed msctemperature.

      Now mscTemperature works. So that's a big step.

      But after an undefined time it stops working (3 times in the attachment).
      From that moment it writes straight lines in the diagram (and in the msctemperature.mdb-file every 5 minutes the same temperature ).

      I do not know why it stops.

      Settings:
      QUASAR_3145_0001 till 0004
      Use Quasar 3145 to collect data on comm port 7 at update interval 5 minutes
      Transfer mapped virtual devices to database at interval 5 Minutes
      Set bad settings to zero
      Enable Temperature Control Triggers and Actions
      Enable temperature control triggers
      Include in Homeseer menu
      Run at normal priority
      , Character to replace decimal point
      C:\Program Files\HomeSeer HSPRO\mcsTemperature.mdb Temperature R

      Some suggestions?
      Is there a security issue?
      Thanks for help, Wiel


      System:
      WIN 7 Homeseer-Pro Edition 2.4.0.1 mscTemp 6.0.0.7 MSoffice-acces2007
      SSD-disk, Intel Atom CPU
      Attached Files
      Last edited by Wiel; June 3, 2010, 03:48 PM.

      Comment


        mcsTemperature has a general debug setting on the Interface page that will collect detailed execution data in the .txt file in the \Data subfolder. If you enabled it and collect data and then post after the data freezes then there may be more info to work with

        Comment


          loggings stops

          Hi Michael, thanks.

          The last logging from mscTemperature was 19.33 h
          See attachment.
          It is possible I asked for a graphic at that moment.


          A reboot from the Homeseercomputer started again the logging from temperatures in the HS-log.
          But INITALLY did not update the temperatures in the Homeseer-homepage. But after refresh the new temperatures became available on the homepage.



          Thanks for help, Wiel
          Attached Files
          Last edited by Wiel; June 4, 2010, 05:13 PM.

          Comment


            Below I showed the last successfull data sample and the following one where no data was received. The line containing "Sampling Quasar 3145 Data" is where mcsTemperature sets the control line of the Quasar unit. When it is set the Quasar should transmit RS-232 data which is read by the COM port and software. This can be seen starting at 19:33:41.

            At 19:38:46 mcsTemperature set the control line, but no data was received. This repeated every sample interval thereafter. I would like to have an good answer for you, but it does look at if mcsTemperature is working as expected and the Quasar unit stopped transmitting for some reason. It has nothting to do with any actions you have done within Homeseer or Browser.

            Code:
            4-6-2010 19:33:41 70421,05 | mcsTemperature Debug | Sampling Quasar 3145 Data
            4-6-2010 19:33:41 70421,73 | mcsTemperature | Quasar Data: R V1.0 2002-01-06 20:37:37 C
            4-6-2010 19:33:42 70422,35 | mcsTemperature | Quasar Data: 1 0023.31
            4-6-2010 19:33:42 70422,37 | mcsTemperature | Quasar Device T1=0023,31
            4-6-2010 19:33:42 70422,38 | mcsTemperature Debug | setIO T1 from 0 to 19, brightness=23
            4-6-2010 19:33:42 70422,38 | mcsTemperature Debug | setDevice T1 from 17 to 2
            4-6-2010 19:33:43 70423,23 | mcsTemperature | Quasar Data: 2 0023.12
            4-6-2010 19:33:43 70423,23 | mcsTemperature | Quasar Device T2=0023,12
            4-6-2010 19:33:43 70423,26 | mcsTemperature Debug | setIO T2 from 0 to 19, brightness=23
            4-6-2010 19:33:43 70423,27 | mcsTemperature Debug | setDevice T2 from 17 to 2
            4-6-2010 19:33:44 70424,13 | mcsTemperature | Quasar Data: 3 0017.56
            4-6-2010 19:33:44 70424,13 | mcsTemperature | Quasar Device T3=0017,56
            4-6-2010 19:33:44 70424,15 | mcsTemperature Debug | setIO T3 from 0 to 19, brightness=17
            4-6-2010 19:33:44 70424,15 | mcsTemperature Debug | setDevice T3 from 17 to 2
            4-6-2010 19:33:45 70425,02 | mcsTemperature | Quasar Data: 4 0018.18
            4-6-2010 19:33:45 70425,02 | mcsTemperature | Quasar Device T4=0018,18
            4-6-2010 19:33:45 70425,03 | mcsTemperature Debug | setIO T4 from 0 to 19, brightness=18
            4-6-2010 19:33:45 70425,05 | mcsTemperature Debug | setDevice T4 from 17 to 2
            4-6-2010 19:33:45 70425,73 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:34:15 70455,73 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:34:45 70485,76 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:35:15 70515,77 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:35:45 70545,78 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:36:15 70575,8 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:36:45 70605,81 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:37:15 70635,83 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:37:45 70665,84 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:38:15 70695,85 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:38:45 70725,88 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0
            4-6-2010 19:38:46 70726,28 | mcsTemperature Debug | Log Temperature Sensor Count=4, INSERT INTO Temperature(SampleDate,sQUASAR_3145_0001,sQUASAR_3145_0002,sQUASAR_3145_0003,sQUASAR_3145_0004) SELECT #2010-06-04 19:38:46# AS QT,2331 AS Q0,2312 AS Q1,1756 AS Q2,1818 AS Q3
            4-6-2010 19:38:46 70726,33 | mcsTemperature Debug | Sampling Quasar 3145 Data
            4-6-2010 19:39:15 70755,88 | mcsTemperature Debug | EvaluateDeviceAction DeviceActionCollection.Count=0, MonitoredEventCount=0

            Code:
            20        If DebugLog Then
            30            hsWritelog PLUGIN_DEBUG, "Sampling Quasar 3145 Data"
            40        End If
            50        Com2.DTREnable = True

            Comment


              Hi Michael, thanks.

              On my old PC mscTemperature in combination with the Quasar worked fine.
              Then the Quasar was connected directly to the RS232 on the mainboard.

              On my new PC I have no RS-232-ports.
              Today I replace (swap) the USB to RS232 converter.
              Hope this will work. ;-)

              To be cont.

              Thanks for help, Wiel

              Comment


                Michael,

                Tested #2 USB to RS232 Serial Port adaptors from www.dealextreme.com.
                Both did not work.

                Then put a PCI-card with 2 RS-232 ports in the PC.
                Now it works !! YES. I am very happy.

                Temperature is comming in Homeseer !!!

                Thanks for help, Wiel
                <!-- / message --><!-- sig -->

                Comment


                  The issues with most serial/usb adapters is with the software drivers quality. If you purchase units supported by FTDI when you will have less grief. Many are happy with the edgeport series. I know byterunning is a good product as well for USB/Serial.

                  Comment

                  Working...
                  X