-
-
Notifications
You must be signed in to change notification settings - Fork 477
Panucatt Wifi Backpack firmware source. #356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sources are 99% identical as this repo, the only difference is the direct access to SD, for this feature sources are not available yet - will be one day, but not yet. Here the videos so you can have a look to have an idea. I do not have any schematics, devices are done by Panucatt devices so better check there. |
The interesting part for me is the SD access. The serial upload is slow, buggy and doesn't compatible with all 3D printer firmware. So please contact with Panucatt and release the sources (at least the firmware, but it would be nice to release the hardware, too). |
Yes I agree serial upload is a outdated and slow like hell protocol - It is why I looked for a solution, I spent a lot of time on it, so for firmware sources I already answered, as I am the owner of sources, Roy from Panucatt is the owner of hardware if you have request for it, please feel free to contact him, I am sure he will answered to you if you explain you want to clone his hardware to do a prototype ^_^. Also Panucatt board + ESP3D is not the only solution for SD access, and some are fully open already: |
I guess issue can be closed |
The source for direct SD access already available? If not, are there any predictions? |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi,
Is it possible to share the firmware source? It would be even better with schematic. I only want to experiment with it on proto board before buying the actual product.
Also being open source is a nice thing🙂
The text was updated successfully, but these errors were encountered: