Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 01:59
    cynthi8 ready_for_review #677
  • 01:59
    cynthi8 edited #677
  • 01:49
    cynthi8 synchronize #677
  • 01:24
    cynthi8 opened #677
  • 01:23
    cynthi8 edited #676
  • 01:23
    cynthi8 edited #676
  • 01:22
    cynthi8 edited #676
  • 01:01
    cynthi8 synchronize #676
  • Mar 01 10:37
    bessman synchronize #173
  • Feb 28 19:52
    bessman edited #173
  • Feb 28 19:49
    bessman commented #170
  • Feb 28 19:45
    bessman edited #173
  • Feb 28 19:44
    bessman opened #173
  • Feb 28 09:14
    bessman commented #170
  • Feb 28 08:58
    cynthi8 opened #676
  • Feb 28 00:34
    orangecms commented #170
  • Feb 27 23:19
    SwapnilSoni1999 commented #170
  • Feb 27 14:48
    Purva-Chaudhari commented #626
  • Feb 27 13:34
    Kartik125 commented #171
  • Feb 27 13:25
    bessman commented #171
nielek2
@nielek2
yes starting it from the terminal works but double-clicking in nemo does not - asks what program to open it with...
"unknown file type"
Daniel Maslowski
@orangecms
Which file did you try? The pslab is an ELF (executable linkable format) binary. That should just work (tm)... :thought_balloon:
$ file pslab-2.4.0/pslab                                                                                               Sat 31 Oct 2020 08:07:58 PM UTC
pslab-2.4.0/pslab: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=ebb360e3c3f594213ec97bf809c969835f21f00a, stripped
looks okay
nielek2
@nielek2
yes pslab
Daniel Maslowski
@orangecms
My girlfriend is volunteering to try it out. I think the .deb and .rpm packages actually generate .desktop files so that you can see the app in an app launcher / menu and launch from there.
Do other binaries run when you double-click them in Nemo?
nielek2
@nielek2
yes
Daniel Maslowski
@orangecms
looks like linuxmint/nemo#2385
nielek2
@nielek2
file --mime-type pslab pslab: application/x-sharedlib
Daniel Maslowski
@orangecms

yup:

$  file --mime-type pslab-2.4.0/pslab                                                                                   Sat 31 Oct 2020 08:15:19 PM UTC
pslab-2.4.0/pslab: application/x-sharedlib

Nemo expects application/x-executable. I'll need to check if electron-builder offers that option. Thank you!

Maybe the upgrade to Electron 10 will fix it. That is a bit out of scope for us. Otherwise, I would ask people to prefer the .deb/.rpm packages if they have distros built upon those, or just run from a command line. For distros where packages can be submitted easily - like Arch -, I can simply add a .desktop file there.
Alexander Bessman
@bessman
The .deb installs, runs, and connects to the device, but none of the instruments seem to work.
Is PSL supposed to be bundled? I can't find it.
nielek2
@nielek2
tried measuring resistance in multimeter mode and it seems to work fine in the in the tar.xz, but i had PSL installed before
Daniel Maslowski
@orangecms
It's not bundled yet, no.
Maybe there is something like a debug build option. One issue I have otherwise is that all the output is omitted, so I was completely in the dark regarding what might be going wrong regarding the path lookup for the Python scripts.
There is https://www.electron.build/#debug but that is only for build time investigation from what I can tell.
Daniel Maslowski
@orangecms
Okay, this works:
env ELECTRON_ENV=development ./pslab-2.4.0/pslab --remote-debugging-port=8315
Then 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.
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
Daniel Maslowski
@orangecms
I have opened, extended and closed a couple of issues. A bunch of things have been achieved. :) I will get back to my PR for the proximity sensor next week and also look into ways to display sensor data
Mario Behling
@mariobehling
Awesome!
Daniel Maslowski
@orangecms
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.
Daniel Maslowski
@orangecms
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.
The made another board named kuttyPy, based on ATMEGA32: https://github.com/csparkresearch/KuttyPy-GUI
Mario Behling
@mariobehling
Last time I checked there was not much going on, but I see there were some updates. Nice. Do you think we could make use of anything here? Though he does not release the hardware. Cannot see it.
Daniel Maslowski
@orangecms
Not sure, I haven't checked anyway, just saw that the last commit in this repo was from 11 days ago. :)
There are quite some docs, and this looks quite nice: https://github.com/csparkresearch/KuttyPy-GUI/tree/master/docs/firmware
Daniel Maslowski
@orangecms
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?
Mario Behling
@mariobehling
Nice, need to discuss pros and cons.
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
Daniel Maslowski
@orangecms
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.
Ah, I would move that issue to the Python repository. Nice!
Mario Behling
@mariobehling
Thank you!
Daniel Maslowski
@orangecms
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.
Mario Behling
@mariobehling
cool
Daniel Maslowski
@orangecms
And this is really nice - little derailing though: https://www.crowdsupply.com/securinghw/tigard
Abhijay Jain
@Abhijay007

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.log

I 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.

Alexander Bessman
@bessman
If there are no objections, I'll go ahead and merge fossasia/pslab-python#148 and fossasia/pslab-desktop#639 tonight.
Mario Behling
@mariobehling
Hi @/all if anyone is interested to join the monthly Codeheat meeting please do so here https://meet.jit.si/codeheat
Abhijay Jain
@Abhijay007
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.
Abhijay Jain
@Abhijay007

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.

Daniel Maslowski
@orangecms
@Abhijay007 you will need to look at that log file that is mentioned there. The excerpt here doesn't include the actual error, only the summary.
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.
Abhijay Jain
@Abhijay007
@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.