There is now a
pslab-desktop package in AUR. :)
I have added a suggestion to the checklist regarding the campaign: Approaching podcast shows. There are quite some out there on FLOSS, hardware and so on, e.g., https://theamphour.com/. We could also ask FLOSS Weekly for an interview. Would you do that @mariobehling or maybe someone else? I could also do it. :)
I think that would be a good chance to spread the word.
I think that would be a good chance to spread the word.
I started to adjust the README on developing, building and distributing the app, adding details on the stack and IPC: https://github.com/fossasia/pslab-desktop/tree/distribution#ipc-and-stack
In the same branch, I reenabled asar, which can create a bundle of 259MB in size. We just needed to separate the Python scripts, which is rather little. The culprit is that we need to determine the environment and load the Python scripts from the
app.asar.unpacked directory accordingly. That works with an env var.
FOSSASIA OpnTec meeting for hardware projects, PSLab, Open Spectrometer etc. is starting in a moment https://meet.jit.si/fossasia-hw
Did you ask about WS2812B @bessman? There are some variants of these LED modules. I have some SK6812 (4 color channels, RGB + warm white; https://cdn-shop.adafruit.com/product-files/1138/SK6812+LED+datasheet+.pdf) and could try out features if you want to work on that. I haven't tried it with PSLab yet.
Otherwise, whoever else asked, just let me note; I saw the question in the meeting notes. :)
I have the desktop app working on my end with the changes in fossasia/pslab-python#121 included. Could you please give it another try when convenient, @orangecms ?
Has anyone worked on the firmware for the ESP8266 yet? I had soldered one onto my board, but have to keep it on reset until it has the right firmware. I see an issue with the same UART being shared between thw UART<->USB coverter, the ESP8266 and the PIC24. So far I couldn't find a hint in the docs. Is the idea to use the ESP8266 for extension of functionality or to provide a second interface besides USB?
I just had a stupid accident and destroyed my PSLab by dropping a wire. The power supply MOSFET near the USB connector is probably dead now. Unfortunately, I am very untalented when it comes to electronics repair stuff. That saddens and frustrates me. I think I am out now, sorry. :(
It could also be a capacitor. When I plug in the board, the blue power indicator LED lights up, then fades out. And the green LED of the MCU doesn't light up at all. The wire was attached to the MCU programmer pin MCLR.
It looks like I will miss most of the meeting now because of train delays. Sorry...
@nielek2 , The one wire LED (ws2812B) can be controlled with SQ1 pin. https://github.com/fossasia/pslab-firmware/blob/master/PSLab_Original/proto2_main.c#L977
4 replies
The firmware remaps the SQR pins to a GPIO.
On Electron availability in Debian: https://wiki.debian.org/Javascript/Nodejs/Tasks/electron#Packaging_electron looks like they are on Electron 4. From what I understand, the current code should be backwards compatible.
Who of you is running Debian (or some derivative) and would like to try it out? I would assist with that.
And maybe we can ask Norbert for help with packaging.
This here is also insightful: electron-userland/electron-installer-redhat#130
Has anyone worked on the firmware for the ESP8266 yet? I had soldered one onto my board, but have to keep it on reset until it has the right firmware. I see an issue with the same UART being shared between thw UART<->USB coverter, the ESP8266 and the PIC24. So far I couldn't find a hint in the docs. Is the idea to use the ESP8266 for extension of functionality or to provide a second interface besides USB?
There's a basic demo firmware on another repo. But if the lines are shared, that's a real design issue.
Especially if both sides will have a bootloader
Yea that's maybe something worth considering for the next hardware revision, what do you think @CloudyPadmal? Is there another UART available? I think the one used for the optional Bluetooth module is separate, right? Could we then rather move the connection there so that you can use either Bluetooth or the ESP8266 addon, at least not conflicting with the main PIC24 MCU? We could also use SPI instead or I2C.
Well, previously the idea was to solder ESP8266 module and solder the reset pin of UART IC to ground to keep the USB-UART connection in reset while the ESP module is active. So only one path can be used at a time; either USB or ESP.
But in the new design this was addressed in a different way with two UARTs. So it is possible to use USB and ESP/Bluetooth without having to reset anything..
Draft for thr upcoming docs overhaul: fossasia/pslab-desktop#617
sorry, was 12 mins late
@mariobehling I am still there though
https://meet.jit.si/fossasia-hw
Ron Minnich from Plan9 and Coreboot Founder is on our open hardware call today
Ron Minnich from Plan9 and Coreboot Founder is on our open hardware call today
@bessman If you want to join in again, we are still there.
Hey everyone, first of all sorry for being late. Yesterday was such incredible - I just posted the link to our meeting in the Open Source Firmware Slack #random channel and then I thought first I was dreaming when Ron showed up out of a sudden. He really likes the PSLab project. :))
I have been working with him for quite a while on various projects that I had already mentioned briefly - coreboot, u-root, and LinuxBoot - and that's also what my friends Philipp and Kai are working on who were with me at FOSSASIA Summit last year in SG (Philipp actually introduced me to the field).
I have been working with him for quite a while on various projects that I had already mentioned briefly - coreboot, u-root, and LinuxBoot - and that's also what my friends Philipp and Kai are working on who were with me at FOSSASIA Summit last year in SG (Philipp actually introduced me to the field).
Anyway, we did quite some brainstorming on things to do, what's happening in firmware, what other hardware projects there are and may be needed, and I have added some key thoughts to our meeting notes; please check them out: https://docs.google.com/document/d/1ovFC8ZZlunQfpMuyyvuoQXiXC_JdBfX4vhm0uCuQe8I/edit
@CloudyPadmal some of the thoughts were around the UARTs and bootloaders on PSLab. We should take a look at EasyBoot (EZB); the sources are available from Microchip, although just in a zip file.
I have found the communication protocol documentation in the firmware repo: https://github.com/fossasia/pslab-firmware/tree/master/docs
It's an office spreadsheet, making it less accessible; I am rewriting it to markdown. It's not much yet, so I think we should put more effort into its extension. That should help with the development of the Python lib which is essential for the entire stack. cc @bessman
It's an office spreadsheet, making it less accessible; I am rewriting it to markdown. It's not much yet, so I think we should put more effort into its extension. That should help with the development of the Python lib which is essential for the entire stack. cc @bessman
@orangecms See also https://github.com/fossasia/pslab-python/blob/development/PSL/commands_proto.py for a complete (?) but sparsely documented list of communication protocol commands.