Palette 3 Pro OS and Firmware
What is the Pallet 3/Pro units OS based/built off of? Is it proprietary or Linux based?
How about the firmware?
Is this a good question?
Score
0
1801
3 Answers
Most Helpful Answer
Hey @emersonsc! The OS on the Raspberry Pi is Linux, but the code running on it is proprietary.
Was this answer helpful?
Score
1
Linux is open source, and the Pi, made by the Raspberry Pi foundation (UK based charity) is part of the open source hardware ecosystem. Doesn't that mean per the GNU GPL you are required to provide your source code?
@emersonsc No, its not uncommon for there to be proprietary modules integrated in an open source platform. The physical board and OS are open source, but the modules developed by Mosaic are Mosaic's intellectual property. Maybe some licensing terms the team could dig up to draw the line better than I could.
Would still be nice to share with developers so they can do the work we want and they refuse to do.
Agreed, the main complaints about the P3P seems to boil down to the unfinished software, and lack of ability to interface with the device and integrate with open source environments/standards. Which are both pretty show-stopping problems, especially in the technical maker community.
I think the hardware you’re running on the Palette 3 Pro is insufficient or lacks proper cooling with the amount of freezing we consumers are getting. What Raspberry Pi board version are you using?
Palette3 just runs Linux on a raspberry pi cm3. The firmware update package just update the docker images inside the os and the firmware of stm32. Actually it's kind of easy to get root access of this S*H*I*T product.
The docker part of the firmware is mainly built with node.js.
And of course they use some opensource components like Janus WebRTC Server (GPLv3)、mosquitto、nginx and some node.js modules.
Was this answer helpful?
Score
1
In my opinion, as a software engineer, the core issues with the deadlock and hang ups is likely poor quality control in the software that leads to failed prints.
That's also why, as far as I can tell, its common for prints to fail at the same spot over and over. To me, that's a dead giveaway that its a software issue.
There are those of us that would love to have the ability to assist in the improvement in the product if we also could gain a little more control over the device. E.g. the amount of throw away filament caused by splicing failures & bad prints is > 50% of my filament use. If filament could be spliced together by feeding filament into the splicer from both incoming and outgoing side and splice them, that would allow me to save filament that's otherwise too short. Yes, you can do this if you want to spend days of your life using the splice tuner, but seriously, cutting off short segments in order to splice it back onto another short segment is dumb.
I imagine it is a very expensive engineering and product development process. But to release the P3 to the public without as many defects as it appears to have just looks bad.
Was this answer helpful?
Score
0
