Separate names with a comma.
Some features disabled for guests. Register Today.
Discussion in '3D printers' started by Oderbang, Dec 6, 2015.
Yep. If you're on Linux/Unix/Mac, dd command will do as well
yep, mac. OK. but I assume Tom can dump it that way too instead of file by file?
Tom is code stupid.
the question is: can you still read the original SD in it's original condition?
Yes, you can read the SD.
No, I meant YOU. If you sitll have access to it or you already assembled it back.
Just so you can download an app and do an ISO backup in 1 click....
Oh, mine hasn't been apart yet. Got the word out to the one we take apart to see if he still has the data. I don't even have time to breath much less play around with things I want to play with.
And with my luck I'd end up quick formatting every drive on my network... no thanks Did I say I am code stupid? That's only putting it mildly.
Any of. You that took apart the Cube and changed electronics.... Can you please gimme. The exact. Measurements of. The motherboard and a hi res pic of front and back please?
I may have Goooood news for. The cube3 community....
MoBo is 260x52mm. The SD Card is 4Gb. It holds a Config, Several .mrl files and any prints you submit via USB or WiFi. The .mrl files are Graphics Images of what is displayed in the LCD.
When loading a Firmware update the proper language pack is selected and saved to the SD card. So, what I am saying you're flogging a dead horse pursuing the contents of the SD.
If you want something to look at, grab any .ar firmware update file and look at with a Hex editor. There are three areas of interest: first one is all the .mrl files, next Image695 which is the actual hex code
for the G-Code executable and the flash boot loader. The third is Boot.bin which brings everything up after the Flash is loaded and btn.bin which is the hard reset.
The processor is a PIC32MX695F512L.Which is actually a MIPs M4Core.
Download MPLAB IDE from Microchip (it's free). Load Image695.hex, run the simulator and look at the code until you get X-eyed and throw up.
I'll give ya all one clue that once you figure it out, will be fun for the next year! "The Cube 3 and the CubePro use the same Motherboard. It's not that difficult after all 3D can be simplified".
I am Truly Grateful for all of the hard work that you have
put in this openbuild!
After finding this forum, it inspired me to purchase a 3rd
gen, just to modify it into an even more portable unit that I
can take on the road as a touring bicyclist.
I am accustomed to modding, but honestly am a newbie
when it comes to 3d printing in general and this arduino/
marlin firmware magic.
I purchased the mks-base v1.5 and the mks-tft28 v1.2,
as this board is powered by either 12v or 24v(so I am
using the cube power supply), and it has support for dual
I tried to use your firmware, changing the board type to 36,
compiles and uploads fine, but TFT doesn't communicate
so i have to use the firmware makerbase offered(see
attachment), but obviously there are configuration
options that need to be made(of which I am clueless)
for this particular machine. Any suggestions?
I have a Gray unit, and the thermistor/extruder connector
wires are not all white as yours, but i am confident I can wire
all but pins 6,8 & 5,7 - could you look at the attached photo
of the mks-base and offer a suggestion?
Also, could you share any more info on the 15 pin
extruder connector you may have(particularly for the
second extruder fan, and/or any other, lights, leveling,
Many Thanks again for your contribution to opensourcing
Greetings To All!
Does any1 knowif the lcd is propietary to them (pinning/wiring) or something more standard?
There is somewhat of a lack on documentation.
The datasheet(attached) says it can connect to aux-1 on a ramps.
The makerbase github site is GitHub - makerbase-mks/MKS-TFT: MKS -TFT
Hope this helps you.
No, i meant the One in the cube3.
Any of you who have performed the filament hack on the Cube3 can enlight us on how to "modify" the cartridges to run the new filament etc?
They come apart real easy so you could simply reload them.
Its easier to just feed them exetrnallly I think...
Of course, a spool holder. You can easily feed through the push-hole under the feeder.
I have very little space for my printer, so keeping the form-factor in check it important.
I do want to join this thread. There is no conversation going on here. Is this thread dead?
I did buy a CubePro and want to help out. It seams that the mainboard for Cube3 and Cubepro are the same.
I am familiar with IDA and can also help out with some reading / writting the firmware onto my board.
I was active with some Stratasys hacking (googlegroup Stratahackers). See my posts here:
Using Insight with any Printer and sending it your own
Howto use Insight with Dimension Models
I did have to sell my Stratasys printer and got me the Cubepro. Will do what is necessary to get this printer going.
I did load the hex file into MPLAB IDE but the Simulator isnt working for me.
Can you give a little bit of assistance?
Starting the Simulator gives me Error :E0108-SIM: Failed simulator operation: java.lang.NullPointerException
I can attach the hex file if needed.
Did someone check if the installed Bluetooth module is working?
I have found the ICSP header. Will get a pic32 programmer from ebay.
I did find it too Waiting for my programmer for arrive so I can try to do some tracing as well. Digging through PIC32 assembly is quite hard for me. Without an access to the live system I'm trying to run the firmware on Qemu with PIC32MX7 support. But it is quite raw, have to write some additional code for it. So far I know that SD Card is on SPI2, chip select is on Port C, pin 3. But no luck having SD card working with it. The reason I want to see the contents of SD Card is to find out if we can disable cartridge checking through configuration files.
MPLAB X SIM didnt work for me. Used the old IDE MPLAB and could search in the memory for some stuff.
In addition to what geezer70 posted I did find these things:
The User 3d and Password print3d doesn't work for Telnet. Should be for ftp. But ftp is disabled.
The FTP Server ftp.cubify.com is also in the firmware. But the login data doesn't work.
Did find something else in memory about Cartridge quantity check present True. Maybe this can be useful.
I have seen this too. 3d/print3d do not work for me either with telnet. I have seen the contents of ftp.cubify.com, you can find user/pass for it in the firmware. Nothing interesting there, only last versions of the firmware for different boards. "Cartridge quantity check present True" sounded very interesting for me as well, that's why I'm digging through the routines, responsible for config file reading and parsing. Hope to find the answer there.
How did you dissamble the files? IDA cant do PIC32.
It can. PIC32 is MIPS, little endian, you also need to create proper memory segments. I have IDA files if you need them.
Would be nice to get them. Thank you.
I will look into them. Did you get your Pickit3 yet?
When attaching the PICKit3 to the ICSP header, MCLR is low this causes the Cube to hard reset and not restart until it is removed
I did disconnect all hardware and attempt to power the motherboard with PICKit3. However, it can only supply about 80ma. Noit enough to bring up the board. I'm going to attempt connecting via JTAG and muddle around.
Parsing an .ar file so that only the Intel Hex remains can be Imported, I repete IMPORTED, into MPLAB IDE.
Create a new project, setup with PIC32MX695F512L. File Import *.hex. Set active project to the current one.
Set Debugger to MPLAB - SIM. View/CPU Registers, /SFR peripherals, /Memory. The Memory window has all the code disasembled
Click Data View for data or Code View for Duh, Code. You can save either to a txt file by right clicking on the widow "output to file".
If you run the Sim you'll get an error because it executes at the beginning of the boot loader which attempts to load the executable
at 9D00_0200 which is side 0, upper memory and fails because it is non-existing address.
This will NOT debug the software. But, it allows you to view the Code and Data for disassempled clues.
In order to actually run code and set break points, etc. you have to have an image loaded on a PIC32 chip and interfaced with a PICKit3.
You can choose to load it on the Cube or a dev board. Either way the Flash area of the device will be ERASED before loading
the new Image. That's just the it works. That's the reason you can't dump the Flash from the Cube via a PICKit3 through the ICSP header. I think the Code Protect fuse is set. But I haven't looked into it.
If anyone knows how to get around this, please let us know.