Announcement

Collapse
No announcement yet.

Arduino Plugin feature requests

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DMcKnight
    replied
    Originally posted by DMcKnight View Post
    Hmm. I still seem to be getting the errors sneaking through at about the same rate. They are fairly infrequent (maybe 1 out of 200 measurements), but when they happen it looks like it sticks around long enough to get by your trap? Either than or things are still not being trapped.

    Thanks for considering this enhancement. (I'll email the log)
    Doug
    I've put in place a work-around for handling this in a script. What I do, is read the value of the Arduino device and, if it is a valid temperature write the value to another device used for this purpose only. This script is triggered on the change of the Arduino device value.

    I still think there is value is making the one-wire system more robust in software, but there are other ways to skin this particular cat.

    regards
    Doug

    Leave a comment:


  • Conrad_Turbo
    replied
    Not sure if this has been mentioned before, but interfacing to an RFID/NFC reader? The WAF would be huge if my wife could swipe a fob and it'd unlock the door. Also could be used to track specific people who enter to announce their arrival or run particular events.

    This is the one I have:

    http://www.dx.com/p/13-56mhz-nfc-rfi...2#.Veibs_lVhBc

    PS I just bought the plugin today as my trial was going to end in two days. I was sold once I had a $3 PIR able to detect my motion and trigger an event to turn some lights on at around midnight last night. The possibilities are endless with this plugin and the source of cheap Arduino's and sensors.

    Leave a comment:


  • DMcKnight
    replied
    Originally posted by enigmatheatre View Post
    Ok I have added a trap so that the rom has to send the error 3 times to the plugin before it will update the device to an error state. If this fixes the problem I may add this as an option on the config page as new people adding new one wire devices wont want to wait to see the errors.

    Try the new build form Here

    Greig.

    Hmm. I still seem to be getting the errors sneaking through at about the same rate. They are fairly infrequent (maybe 1 out of 200 measurements), but when they happen it looks like it sticks around long enough to get by your trap? Either than or things are still not being trapped.

    Thanks for considering this enhancement. (I'll email the log)
    Doug

    Leave a comment:


  • rprade
    replied
    Originally posted by enigmatheatre View Post
    marekd1 and pmiller,

    For your info LCD is now supported in the Beta that is in the updater.

    Greig.
    I am not sure how to cause an error. I've tried disconnecting the data line, the power line and the ground line for 3 minutes each and have not gotten an error. The temperature remains at the last reading. That is the behavior I would want, but I guess it should show an error at some point. How long should it take before an error condition is shown?

    EDIT: I tried again on another board and an error shows up after about a minute, but not as soon as it is disconnected. It retained the last reading for that minute, so I think this change is going to work.

    Leave a comment:


  • DMcKnight
    replied
    Originally posted by enigmatheatre View Post
    Ok I have added a trap so that the rom has to send the error 3 times to the plugin before it will update the device to an error state. If this fixes the problem I may add this as an option on the config page as new people adding new one wire devices wont want to wait to see the errors.

    Try the new build form Here

    Greig.
    Great! I'll try it as soon as I get home later today.

    Doug

    Leave a comment:


  • rprade
    replied
    Originally posted by enigmatheatre View Post
    Ok I have added a trap so that the rom has to send the error 3 times to the plugin before it will update the device to an error state. If this fixes the problem I may add this as an option on the config page as new people adding new one wire devices wont want to wait to see the errors.

    Try the new build form Here

    Greig.
    I installed the new build and it is working fine. Since I never see errors here, I will cause one later and see what happens.

    Leave a comment:


  • enigmatheatre
    replied
    marekd1 and pmiller,

    For your info LCD is now supported in the Beta that is in the updater.

    Greig.

    Leave a comment:


  • enigmatheatre
    replied
    Ok I have added a trap so that the rom has to send the error 3 times to the plugin before it will update the device to an error state. If this fixes the problem I may add this as an option on the config page as new people adding new one wire devices wont want to wait to see the errors.

    Try the new build form Here

    Greig.

    Leave a comment:


  • enigmatheatre
    replied
    Originally posted by rprade View Post
    I think Doug has a good idea, though I don't see any errors here. If the board receives updated from the OneWire devices, how about not updating the device value until there are three successive error reports. Or if the OneWire devices only report when there is a change not showing error on the HS device unless it persists for more than 3000ms? Either way would leave the HS device at the last reported value until the error was proven persistent.
    Ok I now think I know what your talking about. There are two ways that the error is produced. One is if the bus sends bad data and the second is a time out on the device not updating so I guess it is the bad data that is the problem as this sets the device in the the error state immediately but the time out waits 2min before setting the device in the error state.

    I will see what I can do.

    Greig.

    Leave a comment:


  • rprade
    replied
    Originally posted by enigmatheatre View Post
    Doug,

    Ok I think I get what you want now and I may have misunderstood what you were after. The problem is that I receive and handle the data from the onewire bus in the plugin and if it is strange data there is an error. I have no way of polling the bus from the plugin so I would need to try and handle the errors on the board or find a way to poll the device if there is an error.
    I do not have a lot of time at the moment but I will try and set up a test to see if this is possible to add.

    Greig.
    I think Doug has a good idea, though I don't see any errors here. If the board receives updated from the OneWire devices, how about not updating the device value until there are three successive error reports. Or if the OneWire devices only report when there is a change not showing error on the HS device unless it persists for more than 3000ms? Either way would leave the HS device at the last reported value until the error was proven persistent.

    Leave a comment:


  • enigmatheatre
    replied
    Doug,

    Ok I think I get what you want now and I may have misunderstood what you were after. The problem is that I receive and handle the data from the onewire bus in the plugin and if it is strange data there is an error. I have no way of polling the bus from the plugin so I would need to try and handle the errors on the board or find a way to poll the device if there is an error.
    I do not have a lot of time at the moment but I will try and set up a test to see if this is possible to add.

    Greig.

    Leave a comment:


  • DMcKnight
    replied
    Originally posted by enigmatheatre View Post
    Doug,

    I can confirm that the "9999999" is the error value of my plugin so this is being handled by my plugin is showing on the device as an error. The problem is that you are graphing the value so it records the "9999999".

    Greig.

    Hi Greig,
    I'm a little confused by your reply. I think that's what I expected. The plug-in is detecting an error and so reports an unambiguously error-style of value. I think that behaviour makes sense.

    What I'm wondering is if the plug-in could be enhanced to try again, if it detects an error condition like this.

    For example, if it could be configured to "retry 3 times" on error, for example, then I think my system would work just fine. The errors are quite rare and are proving quite stubbornly difficult to track down and eliminate in hardware.

    regards
    Doug

    Leave a comment:


  • enigmatheatre
    replied
    Doug,

    I can confirm that the "9999999" is the error value of my plugin so this is being handled by my plugin is showing on the device as an error. The problem is that you are graphing the value so it records the "9999999".

    Greig.

    Leave a comment:


  • mihaium
    replied
    Hello Greig.
    Today is happened the same error in the my system. Is 1 error to 3-4 hours. I have 1 DS18B20 (TO92 capsule ) with 8m CAT5 cable and 1 kohm resistor.


    Inviato dal mio SM-G920F utilizzando Tapatalk

    Leave a comment:


  • enigmatheatre
    replied
    Originally posted by DMcKnight View Post
    Debug log sent by email.
    Regards
    Doug
    Doug,

    I will need to check the code when I get home but looking at the log I think my plugin is reporting an error for your devices. If you look at the rom device that has the temp in it is the status value for error not "9999999" and what you are seeing is Jon00's plugin logging this value. I will confirm this when I have more time and also see if there is a way to stop this.

    Greig.

    Leave a comment:

Working...
X