{"action":"closed","issue":{"url":"https://api.github.com/repos/joan2937/pigpio/issues/197","repository_url":"https://api.github.com/repos/joan2937/pigpio","labels_url":"https://api.github.com/repos/joan2937/pigpio/issues/197/labels{/name}","comments_url":"https://api.github.com/repos/joan2937/pigpio/issues/197/comments","events_url":"https://api.github.com/repos/joan2937/pigpio/issues/197/events","html_url":"https://github.com/joan2937/pigpio/issues/197","id":298992541,"node_id":"MDU6SXNzdWUyOTg5OTI1NDE=","number":197,"title":"faulty (?) RFID-Readings with python pigpio","user":{"login":"sk-gara","id":22907735,"node_id":"MDQ6VXNlcjIyOTA3NzM1","avatar_url":"https://avatars1.githubusercontent.com/u/22907735?v=4","gravatar_id":"","url":"https://api.github.com/users/sk-gara","html_url":"https://github.com/sk-gara","followers_url":"https://api.github.com/users/sk-gara/followers","following_url":"https://api.github.com/users/sk-gara/following{/other_user}","gists_url":"https://api.github.com/users/sk-gara/gists{/gist_id}","starred_url":"https://api.github.com/users/sk-gara/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sk-gara/subscriptions","organizations_url":"https://api.github.com/users/sk-gara/orgs","repos_url":"https://api.github.com/users/sk-gara/repos","events_url":"https://api.github.com/users/sk-gara/events{/privacy}","received_events_url":"https://api.github.com/users/sk-gara/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":16,"created_at":"2018-02-21T14:33:02Z","updated_at":"2018-07-23T09:03:19Z","closed_at":"2018-07-23T09:03:19Z","author_association":"NONE","body":"I'm reading RFID cards from Honeywell-Reader on a Pi3. Taking the wiegand.py example from the homepage as a start, i modified the data- and clock pin watchdogs (only on clock) and the callback functions. Works well. By the way, from inside one or more docker containers or directly on the host OS, which is Raspbian.\r\nBut when stress-testing the function with many card-scans in succesion, after some correct readings, there will follow up some corrupted values - caused by tick-values coming from the clock pin that are too \"long\" or too \"short\", triggering the watchdog on that pin too early or too late.\r\nWhen monitoring the readings with Piscope in parallel, i can see that the readings are correct, so the tick-values presented by the python package seem to be somehow corrupted.\r\nIs this a known limitation of the python implementation of pigpio or should it work as flawless as it runs in Piscope?\r\n\r\nI'm using ~~piscope~~  pigpio 64.\r\n\r\nHere some values to illustrate, the columns are:\r\n tick, ms since last tick, pin, data_level\r\n```\r\n547086377 547086377 17 1\r\n547087582 1205 17 1\r\n547088797 1215 17 1\r\n547089937 1140 17 1\r\n547091122 1185 17 1\r\n547092268 1146 17 1\r\n547093412 1144 17 1\r\n547094553 1141 17 1\r\n547095772 1219 17 1\r\n547097007 1235 17 1\r\n547098188 1181 17 1\r\n547099329 1141 17 1\r\n547100509 1180 17 1\r\n547101653 1144 17 1\r\n547102863 1210 17 1\r\n547104003 1140 17 1\r\n547105147 1144 17 1\r\n547106287 1140 17 1\r\n547107612 1325 17 1\r\n547108707 1095 17 1\r\n547109853 1146 17 1\r\n547111044 1191 17 1\r\n547118538 7494 17 2\r\n```\r\nThe sequence should be 115 bit long, but it stops at the last callback with timeout on pin 17 (7,5 ms)"}}
{"actor":{"display_login":"sk-gara"}}