Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 05:46
    KushMehta1511 opened #2170
  • 05:46
    KushMehta1511 opened #2170
  • 05:31
    KushMehta1511 commented #2169
  • 05:31
    KushMehta1511 commented #2169
  • Jan 17 20:35
    bessman synchronize #666
  • Jan 17 20:32

    bessman on development

    Fix #658 - Oscillosope not disa… (compare)

  • Jan 17 20:32
    bessman closed #660
  • Jan 17 20:32
    bessman closed #658
  • Jan 17 16:54
    bessman edited #666
  • Jan 17 16:53
    bessman opened #666
  • Jan 17 16:21
    bessman commented #127
  • Jan 17 16:13
    bessman synchronize #158
  • Jan 17 16:07
    bessman edited #158
  • Jan 17 16:07
    bessman opened #158
  • Jan 17 12:34
    asaikarthikeya edited #2167
  • Jan 17 12:34
    asaikarthikeya edited #2167
  • Jan 17 05:12
    KushMehta1511 edited #2169
  • Jan 17 05:12
    KushMehta1511 edited #2169
  • Jan 17 05:11
    KushMehta1511 opened #2169
  • Jan 17 05:11
    KushMehta1511 opened #2169
Alexander Bessman
@bessman
Waveform table size does not seem to correlate with max amplitude:

@CloudyPadmal
Padmal
@CloudyPadmal

i found this library for possibly implementing sd card functionality: http://elm-chan.org/fsw/ff/00index_e.html and a tutorial here: https://www.studentcompanion.co.za/interfacing-sd-card-with-pic-microcontroller-xc8/

Thank you @nielek2 .. I'm using this chan library generated from "Microchip Code Configurator" and it works as a separate function. Now need to integrate it with the current work flow.

Waveform table size does not seem to correlate with max amplitude:

@CloudyPadmal

Thank you @bessman ,, I'll try a simulation and hope it would narrow it down the bottleneck..

Padmal
@CloudyPadmal
So, I made some changes in pslab-hardware repo (my fork) where I added a special branch to hold diff images comparing the new changes with the previous board. https://github.com/CloudyPadmal/pslab-hardware/tree/diff-img
@mariobehling , should I integrate that in to the main repo?
Abhijay Jain
@Abhijay007
I made some changes in PSLab where I set-upped Storybook UI environment and Updated Electron to version 10. Now Codacy/PR Quality Reviewer show that some test case is not passed but I don't understand what is the reason.
@mariobehling,@orangecms sir review my PR here : fossasia/pslab-desktop#642
when you get time.
Daniel Maslowski
@orangecms
Really nice, thank you! Let's discuss further details on GitHub :)
Ir Jelle van der Linde
@Jelle007
I am still reading all documentation /source files etc..It is overwhelming and a lot of work In the mean time I build a nice case ...... Still do not know basic requirement for an Android tablet (> Android > 6 also Android 10?, Screen resolution ?) . I started a RS 232 terminal session (COM3,9800 Baud, 1 stopbit, no parity) with the board conected. I understand the firmware lissten to commands-subcommands-parameter. (three documented in an old protocol.ods document) . The command get_version (chr(11) Chr(5) or 0x0B 0x05) shoult give a response , but I only get 00 00 00 after issuing a CR/LF after the command. So that's bothering me. Broken board ? Beginners mistake ? This weekend I am not able to participate in de 5'o clock meeting. Happy to do that later on when I am more familiar with PSLAB . In the meantime any suggestions are welcome.
I am still reading all documentation /source files etc.. (difficult to get a complete and consistent view, for me of coarse ) )
But the the amount of work is overwhelming and impressive. I can not find a (functional-technical) specification document for the toolset and hardware (The intended goal is to get/improve a low cost device to be used in an experimentation environment )
In the mean time I build a nice case for de PSLAB V5...... Still I do not know basic requirements for an Android tablet (> Android > 6 also Android 10?, Screen resolution ?) so that’s stops me from buying one and starting with the Android app. . I started a RS 232 terminal session (COM3,9800 Baud, 1 stop bit, no parity) with the board connected. I understand the firmware is message driven : commands-subcommands-parameter. (three commands out of the dozens documented in an old protocol.ods document) . The command get_version (chr(11) Chr(5) or 0x0B 0x05) should give a response , but I only get 00 00 00, after issuing a CR/LF after the command. So that's bothering me. Broken board ? Beginners mistake ? This weekend I am not able to participate in de 5'o clock meeting. Happy to do that later on when I am more familiar with PSLAB . In the meantime any answers to my basic beginners questions are welcome.
Daniel Maslowski
@orangecms
@Jelle007 I have filed a PR to replace the ODS doc with a simpler Markdown table. I am not 100% certain I got it right, mostly working on the desktop app. Do you have any feedback so far @CloudyPadmal? Otherwise, for talking to the board, please have a look at the Python lib: https://github.com/fossasia/pslab-python
It has all the bits to connect and talk to the board via pyserial. That might be easier to understand.
nielek2
@nielek2
@Jelle007 you could also give the python library on the raspberry pi a try
Daniel Maslowski
@orangecms
Interesting bits on Antratek when looking at their PSLab product page - they list those related products:
https://www.antratek.com/pocketlab-voyager
https://www.antratek.com/logic-analyzer-25mhz-8-channel
Daniel Maslowski
@orangecms

I found this flow chart for the firmware:
https://github.com/CloudyPadmal/pslab-firmware/blob/pslab-v2.0/PSLabFirmwareFlowChart

And converted it to SVG:
https://metaspora.org/pslab-flowchart.svg

It is quite huge though

Daniel Maslowski
@orangecms
It was a hassle with Electron, but I finally managed to get the thing to work. We now have asar bundling reenabled, and release builds manage to locate the Python scripts correctly. Now the CI server just needs to play along and we will finally have a working binary release - .deb, .rpm, and .tar.xz for Linux. That was a :roller_coaster:
nielek2
@nielek2
great!
Daniel Maslowski
@orangecms
Thank you for volunteering to try it out. :D
I just downloaded the tar.xz and ran it - it works \o/ :tada:
That was quite some motivation++ lol :D
nielek2
@nielek2
the tar.xz also runs on my computer
Daniel Maslowski
@orangecms
Does it also detect the board?
nielek2
@nielek2
yes
Daniel Maslowski
@orangecms
Woohoo! \o/ (the tricky part was really the Python script path lookup, heh) awesome :)
nielek2
@nielek2
the file doesn't offer to run from the gui, when i double-click it
Daniel Maslowski
@orangecms
Now the basics are there for further releases. I need to dive a bit into the Docker thingies to figure out where to dig out the Windows build and we can publish that as well.
Someone already wrote in the venv issue that they could work on it. Maybe that will get us a full bundle.
nielek2
@nielek2
execute bit is set though
Daniel Maslowski
@orangecms
Hmm can you describe that a bit further? Did you navigate to the directory with a file manager like Nautilus or something?
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.