Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 11:14
    asaikarthikeya opened #2181
  • 11:14
    asaikarthikeya opened #2181
  • 10:33
    arpoch opened #2180
  • 10:33
    arpoch opened #2180
  • 09:56
    bessman closed #133
  • 09:56
    bessman commented #133
  • 09:33
    bessman commented #159
  • 09:27
    cynthi8 commented #159
  • 08:51
    bessman commented #159
  • 08:47
    bessman closed #159
  • 08:47
    bessman commented #159
  • 08:42
    cynthi8 opened #159
  • 07:12
    cynthi8 commented #468
  • 04:37
    cynthi8 commented #610
  • 04:23
    KushMehta1511 opened #2179
  • 04:23
    KushMehta1511 opened #2179
  • 03:07
    KushMehta1511 commented #2172
  • 03:07
    KushMehta1511 commented #2172
  • Jan 22 18:07
    asaikarthikeya commented #2173
  • Jan 22 18:07
    asaikarthikeya commented #2173
François Cartegnie
@fcartegnie
and has discovery kits providing STLink debuggers for free
And for ADC, I wouldn't buy a board that cost more than the chinese one if the sampling rate is the same. Driving a dedicated sampling chip (The PIC one was 2Msps, can be the same) would be more valuable.
example dev board (once sold less than 10e): https://www.st.com/en/evaluation-tools/stm32f3discovery.html
François Cartegnie
@fcartegnie
F3 provides DMA (that could be interesting if I could understand how it could be used for USB)
@orangecms ^
Daniel Maslowski
@orangecms
Could you add some details to the issue on the pslab-hardware repo?
fossasia/pslab-hardware#79
Daniel Maslowski
@orangecms
As I read it, the Blue Pill board can do USB, e.g., https://github.com/Serasidis/STM32_HID_Bootloader - likewise the F4 series, like the Nucleo board: https://smile.amazon.de/dp/B08GCQSG2G/ref=cm_sw_r_cp_apa_i_2HEbGb41TJH02
Daniel Maslowski
@orangecms
A friend of mine says the F107 also has an RTC and supports battery power supply for low power mode.
Daniel Maslowski
@orangecms
https://twitter.com/OrangeCMS/status/1351334550274789377
I pushed my stupid little example to https://github.com/orangecms/stm32f103-usb-commands/tree/pslab-shim
I have implemented the PSLab version command as a PoC :)
Padmal
@CloudyPadmal
Good news! 👏🏻I got the bootloader working. But, the IDE doesn't work at all in Linux and it looks like a common issue. So I had to try in a Mac. I guess that's one way to go 🤔
Mario Behling
@mariobehling
Oh man.
But indeed good news.
nielek2
@nielek2
happy to hear that the bootloader ist up and running!
Padmal
@CloudyPadmal
🤩
Alexander Bessman
@bessman

I'm investigating some RGBLED-related code in pslab-python and pslab-firmware. I've discovered that the WS2812B method can set the color of the WS2812B LED on the new (v6) board when called with output="CS1". Cool, so far so good.

However, I get confused when I look at the firmware. The WS2812B method puts the firmware state machine into this state, which uses an output called CSOUT1 to send a pulse train to the LED. CSOUT1 is AKA _LATB5, which if I understand my Microchip-C correctly is used to set pin RB5 HIGH/LOW. However, the WS2812B on the v6 is not connected to RB5, but to RB2 according to the schematics (I've verified that this is correct with a multimeter).

The WS2812B method can also be called with output="CS2" and output="SQR1". SQR1 is clear enough, and looking at the firmware CS2 should be controlling RB6 (which is labelled PGC on the board). Indeed, looking at PGC with the logic analyzer while calling WS2812B() with output="CS2" confirms this. But output="CS1" does not seem to control RB5/PGD, but rather RB2.

Any ideas why that is? Also, PGC is on the programming header, so shouldn't it be an input, not an output?
Padmal
@CloudyPadmal
I see the confusion. https://github.com/CloudyPadmal/pslab-hardware/blob/pslab-v6/docs/schematics/PSLab.pdf is the schematic with RGB LED. I used RB2 (a spare pin) to control the RGB LED. I still have to push the new changes made to firmware repo..
Alexander Bessman
@bessman
That explains it, thanks!
Daniel Maslowski
@orangecms
The STM32H7 costs <€5/unit for 1000 units: https://www.mouser.de/ProductDetail/STMicroelectronics/STM32H723VET6/?qs=sPbYRqrBIVnD9Udgf5csJA%3D%3D
That'd be twice the price of the current PIC
Daniel Maslowski
@orangecms
https://www.mouser.de/ProductDetail/Microchip-Technology/PIC24EP256GP204-I-PT
Alexander Bessman
@bessman
How about the RP2040? :eyes:
https://www.raspberrypi.org/products/raspberry-pi-pico/
Daniel Maslowski
@orangecms
Oh nooo, not another one... it is hard enough on the market already, haha :D
https://www.adafruit.com/itsybitsy2040 has more details, sounds okay so far - it has a DMA controller
Alexander Bessman
@bessman
The raspberry pi pico is $4 per unit, so the RP2040 could even be competitive with our current uC at /1000 units cost.
The rpi foundation also has top notch documentation, which is nice.
It's a little light on analog inputs. It has either three or four, depending on the source. I think we have eight today.
Alexander Bessman
@bessman
I think the pico has three analog inputs, while the RP2040 itself has four.
Alexander Bessman
@bessman
Only a single ADC with sample rate 500 kS/s :frowning: Probably not what we want, then.
Daniel Maslowski
@orangecms
Yea... those important details (to us) are often a little further down in the specs/datasheets, as I found, making it a bit more time consuming to compare the chips. ^^ We should collect more information in a spreadsheet with specs for comparison, including MCUs we considered, but are unsuitable, so we remember what we looked at. @mariobehling could you create a Google Spreadsheet for us? :)
What columns would we need? Name/model, price, RAM and flash size, clock rates, DMA support, how easy the MCU is to use (toolchain, flashing, costs for programmers)... et voilà, we have defined some TCO (Total Cost of Ownership), sort of.
Mario Behling
@mariobehling
@orangecms Good idea! https://docs.google.com/spreadsheets/d/1wK7-4TWjJrDChqv04jNQcQMvftZ-Z48Z34n5H17Wtwo/edit#gid=0
Daniel Maslowski
@orangecms
That was quick, thank you! :heart:
François Cartegnie
@fcartegnie
1 - do we have some test code to test sampling rate ?
2 - do we own a real (square) signal generator (~150eur)
MCU choice will also depend on RAM, conversion speed, and USB transfert/limit. That needs a real world test with demo (nucleo/discovery) boards.
Not enough ram to store temp samples, or not being able to pull results fast enough won't help with a fast ADC :/
Daniel Maslowski
@orangecms
Yup, let's note dann the PoC requirements in the issue in the pslab-hardware repo and add a column "PoC" to the sheet :)
note down*
François Cartegnie
@fcartegnie
would also nice to have a real hard scope side to side
missed the 125e deal on amazon.de
Sai karthikeya
@asaikarthikeya
Hello this is Sai karthikeya. Currently I am contributing to PSLAB android app. Is this the right channel to ask quires related to android app?thankyou.
Erin Cold
@cynthi8
Hi Sai, yes. Here or raising an issue on the GitHub.
Sai karthikeya
@asaikarthikeya
Currently ,few guilds are missing images of related working part of Pslab hardware. It would be great if someone could provide me the images to make the guilds complete. 1)Dust sensor 2) thermometer
WhatsApp Image 2021-01-22 at 9.42.40 PM (2).jpeg
WhatsApp Image 2021-01-22 at 9.42.40 PM (1).jpeg
Randhir Kumar
@GITrandhir
Hello Everyone , I'm Randhir Kumar a 2nd Year UG. It's been 6 months since I'm exlporing and learning Android. Fossasia looks a good place to contribute and learn. Can anyone tell me about some android projects fossasia is working on. It will be so helpful for a newbie like me.