s3rp crash on latest Win10/ Google Chrome when using read digital pin
ssoltek opened this issue · 4 comments
Actually doing some first steps with a Raspberry Pico and your great scratch one GPIO extension. Settings digital pins an doing blinking for example works fine, but using read digital pin leads to immediate cloding of the websocketServer because s3rp exits with signal 0:
PS C:\Users\Lucy> s3rp
backplane started
Websocket Gateway started
RPi Pico Gateway started
To exit this program, press Control-c
Websocket Gateway exited...
Exception ignored in atexit callback: <bound method S3RP.killall of <s3_extend.s3rp.S3RP object at 0x0000017408FC4230>>
Traceback (most recent call last):
File "C:\Users\Lucy\AppData\Local\Programs\Python\Python312\Lib\site-packages\s3_extend\s3rp.py", line 141, in killall
sys.exit(0)
SystemExit: 0
PS C:\Users\Lucy>
See screenshot for actual program.
python, pip and s3extend are up to date. What i find curiuos is that the screenshot in your manual is not matching the acual scratch command - the option to configure the pullup resistor is missing. May this be the problem?
Anything I can do beeing a python noop to assist in debugging?
Bye and a happy new year
Simon
Hi Simon,
Thanks for reporting this. You are correct that the pull-up drop-down is no longer in the read input block.
I am unsure when this breakage occurred, but I will need to examine the cause and implement a fix.
I will post here when a fix is available.
Thanks,
Alan
Hi Simon,
The problem should be fixed. Please let me know if it works for you so I can close the issue.
The parameter should now appear in the block.
Also, I'd like to point out that I moved the issue to the s3onegpio repository since that is where I implemented the fix.
Thanks again for reporting the issue.
Thx!
Fix is working fine for me (actually tested on Linux today because having actually no access to the windows machine)
Happy new year!
Great. Have a very Happy New Year.