There is https://www.electron.build/#debug but that is only for build time investigation from what I can tell.
Okay, this works:
Then open http://localhost:8315/ and follow the link to
env ELECTRON_ENV=development ./pslab-2.4.0/pslab --remote-debugging-port=8315Then open http://localhost:8315/ and follow the link to
linker.html - that's the process that spawns the Python shell underneath. And then you can investigate errors there and should see the stdout/stderr output.
https://metaspora.org/pslab-debug.png should look like this
this is an example from not being able to connect without PSLab plugged in, and it should also output any other errors with interfacing with the Python library etc
The "just upgrade Electron" thing is a little more work than anticipated. There is quite some things going on in their future roadmap, so we might need to rework architectural bits. Don't worry though, there are always options and about every app relies on the core interfaces they are about to change.
With contributions towards testing and venv, we can gain stability around the integration. If IPC (inter process communication) turns put to be too complicated, we can always switch to TCP based RPC, like many other apps also do. Python can handle websockets for subscriptions, which we could use for continuous data flows like reading from sensors.
Is anyone still tracking the development of the original SEELablet / ExpEYES projects?
https://expeyes.in/ / https://github.com/csparkresearch looks like there is still much going on there.
https://expeyes.in/ / https://github.com/csparkresearch looks like there is still much going on there.
The made another board named kuttyPy, based on ATMEGA32: https://github.com/csparkresearch/KuttyPy-GUI
There are quite some docs, and this looks quite nice: https://github.com/csparkresearch/KuttyPy-GUI/tree/master/docs/firmware
We could wire up PSL with Pulseview: https://sigrok.org/wiki/Protocol_decoder_API#Backend_library
Then we don't need to care much about the logic analyzer GUI in our Electron app, in other words, we wouldn't need to reinvent the wheel. What do you think?
Then we don't need to care much about the logic analyzer GUI in our Electron app, in other words, we wouldn't need to reinvent the wheel. What do you think?
I opened this issue a long time ago using my phone (and I am a slow phone typer). So basically just noted down some bullet points back then as a reminder fossasia/pslab-hardware#74
Sure - and actually, we could even just write a decoder for it regardless. If all goes well, it is just a tiny bit of work, and suddenly, we are integrating with an awesome tool - no cons involved thus far except for a bit of work. :-)
The open questoin would be if we really want to have yet another full implementation of everything around logic analyzers. I think that is quite a bunch of work. The point I would like to raise is that a logic analyzer can very well be its own tool. Maybe it's something to brainstorm about on Saturday.
The open questoin would be if we really want to have yet another full implementation of everything around logic analyzers. I think that is quite a bunch of work. The point I would like to raise is that a logic analyzer can very well be its own tool. Maybe it's something to brainstorm about on Saturday.
Ah, I would move that issue to the Python repository. Nice!
The PSoC5LP from Cypress / Infineon may be a suitable SoC for a simple LA + oscilloscope sister board. A simple logic analyzer can be based on the CY7C68013A, which is what the BitMagic LA is based on: https://1bitsquared.de/products/bitmagic-basic
If we go for a more dedicated LA/oscilloscope, we may be able to offer more channels than the PSLab, on that note.
Can someone please help me to solve these errors?
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! pslab@2.4.0 start: `concurrently 'npm run react-start' 'wait-on http://localhost:3000/ && npm run electron-start'`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the pslab@2.4.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User\AppData\Roaming\npm-cache\_logs\2020-11-01T07_26_36_221Z-debug.logI already tried many solutions by reading blogs and through StackOverflow but nothing can work out. I need to run some tests to check out whether there are some breaking changes or not But because of these errors, I am not able to work further.
Please help me to resolve these errors.
If there are no objections, I'll go ahead and merge fossasia/pslab-python#148 and fossasia/pslab-desktop#639 tonight.
Hi @/all if anyone is interested to join the monthly Codeheat meeting please do so here https://meet.jit.si/codeheat
Dear @maintainers @mariobehling, I have a suggestion and a request for you, can you please make a video like this https://asciinema.org/a/370458?speed=5&autoplay=1 for the installation of fossasia/PSLab project in our local machine and please insert that in the project readme file as well. It will be very helpful for beginners like me and new joiners.
Dear @maintainers @mariobehling, I have a suggestion and a request for you, can you please make a video like this https://asciinema.org/a/370458?speed=5&autoplay=1 for the installation of fossasia/PSLab project in our local machine and please insert that in the project readme file as well. It will be very helpful for beginners like me and new joiners.
I made this request because I am constantly getting errors while running this project and I don't know where I made the mistake I went through the project readme but still facing errors.
For a log similar to the asciinema recording, you could check the output of a CI build. It won't help you with errors though.
Here is the latest one: https://travis-ci.com/github/fossasia/pslab-desktop/jobs/429079196
@orangecms sir, I tried many solutions and commands but nothing can workout and I don't know where I made mistake I already clean the log file using this command
npm cache clean --force and reinstall all node modules but it still shows errors and because of these errors I am not able to run tests to check whether there are some breaking changes or not.
I.e., what errors do you get?
@orangecms Sir, this the log file that mentions in the above error can you please analyze it and tell me where I made the mistake or what else I need to install other than node modules
Have you tried to just run the scripts one by one instead of relying on concurrently? It might be a portability issue with Windows.
@orangecms Sir I tried but it still shows errors
PS C:\Users\user\Desktop\PSlab\pslab-desktop> npm run react-start
> pslab@2.4.0 react-start C:\Users\user\Desktop\PSlab\pslab-desktop
> BROWSER=NONE react-scripts start
'BROWSER' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! pslab@2.4.0 react-start: `BROWSER=NONE react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the pslab@2.4.0 react-start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache\_logs\2020-11-07T08_52_24_597Z-debug.log
PS C:\Users\user\Desktop\PSlab\pslab-desktop> npm run electron-start
> pslab@2.4.0 electron-start C:\Users\user\Desktop\PSlab\pslab-desktop
> DEV=1 electron .
'DEV' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! pslab@2.4.0 electron-start: `DEV=1 electron .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the pslab@2.4.0 electron-start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache\_logs\2020-11-07T08_53_26_417Z-debug.log
PS C:\Users\user\Desktop\PSlab\pslab-desktop>
logging files that are mentioned in the above errors.
This is a way of setting environment variables on Unix-like systems. On Windows, there is built-in shell command
set. There are two ways to solve this: Introducing cross-env to the project, or asking Windows users to go with WSL or Cygwin etc to have a Unix-like environment. Do you have WSL set up?
Here is your answer:
'BROWSER' is not recognized as an internal or external command, operable program or batch file.
@orangecms Sir, I installed and set-upped WSL as you mentioned in the above comment but it still shows errors do I need to configure it further means some after installation commands to resolve that.
PSLab and Open Hardware meeting going on now, if anyone is interested it is here https://meet.jit.si/fossasia-hw