I have purchased the RAMPS 1.4. I was wondering if you could help me. How do I wire the stepper motors? They are different than the ones I see in videos as they have 6 pin connector. I assume I need to wire the 4 wires to the ramps board, but I do not know which wire goes where . Also, how about end stops? Does this have end stops to wire to the ramps board?
Ok the xml file which was mentioned is on the cubify server. This is called when starting cube print. Private Const Cubify_Version_XML As String = "http://cubify.s3.amazonaws.com/public/cube3/magellan_software.xml" I did find something else. The config files in the cubify folder are encrypted. The scrambled password is : eXbfXoDj^e\\>?/12 AND this is the unscrambled one 221BBablfsNzdspgu The files are encrypted with blowfish. Maybe someone can find out how to decrypt them. There is a file in the cubify folder which is named cubefyit.exe . This loads the file ConfigurationCube123.xml which then is used for configuration of the printer. If someone wants to look into the code. I have attached it.
That looks like the internal version of the 4.03 windows software. When you put the x.cube3 file on a memory stick, the internal processor does a lot of processing. When you send it over WiFi, it is much faster, so there is a difference in the way you interface with the system.
That's not the unscrambled password ^_^. Working on decryption, I will post whenever there is a result
Does that have anything to do with this? cube-utils/cube-decoder.c at master · fritzw/cube-utils · GitHub
Good But so far I could not decode for some reason, decode function has a strange behavior. It does not decode more than 30 bytes at a time no matter what length you will specify. And mostly it complains about the length itself. Will try more tomorrow.
OHHH TOM you made my Day. Just use CubeX to decode the files!!! It works: <?xml version="1.0" encoding="utf-8"?> <Config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="XML Schema"> <global> <ConfigurationFileVersion>X560</ConfigurationFileVersion> <m_ModelColor> <red>0</red> <green>204</green> <blue>255</blue> </m_ModelColor> <m_BkgrndColor> <red>201</red> <green>211</green> <blue>226</blue> </m_BkgrndColor> <Model>CUBE3</Model> <Material>PLA</Material> <NetworkName /> <NetworkKey /> <Cube3Support>true</Cube3Support> <NewComp>true</NewComp> <ModelColor> <red>0</red> <green>204</green> <blue>255</blue> </ModelColor> <BkgrndColor> <red>201</red> <green>211</green> <blue>226</blue> </BkgrndColor>....
Start CubeX64 or X32. Choose Cubepro and decode. Go to browse and Choose all Files in filetype. Go to cubify dir and pick config123.xml and Press ok. File will be named *.bfb. Open with notepad.
Any switches in there for DIAGNOSTIC MODE, ADMIN MODE, DISABLE XXX? If anything, this is exactly where you'd put diagnostic switches that could include the security chip. Once you know that switch, we can probably add it to another config file. If all this handshaking is going on with Cubify, how do you force a local XML file to take precedence?
I was able to use a program called Fiddler, worked in a few minutes to host the magellan_software.xml on my pc
Ok, found an interesting dialog from the cube print software, here is the request and response. Can anyone make sense of it?
That looks like an ad-hoc network connection with encryption request. Mine will connect to a neighbor's protected router and consider itself connected but not be found on my network. This is what I mean about persistence.
@Naldarn The Software cubeX was mentioned by Tom Dirriwachter . I looked into the XML Files but couldnt find any references to a admin / debug mode.
The sv.symcd.com is referenced in communications from the cube print software when first starting up.
Finally had a look on our *.ar files. Appeared to be pretty straight-forward, no checksums, only sizes of files plus overal size and couple of signatures in the begining. That means once we modify our *.hex file, there will be no problem putting it back to printer. Here is my small tool for firmware un-pack/pack (sorry, very raw, must be very buggy, change extension to exe and have framework 4.5 installed). P.S. Just tried to upgrade from my re-packed firmware, it worked, printer is not bricked! Whohooo Disclaimer: Everything you do to your printer, you do on your own risk
Great!! Any idea what the mrl files are? I think they are for the lcd display, but can't find any way to view them.
As I remember, somebody here mentioned that it's LCD images. But I have no idea about format, haven't looked at it yet.
Ok, I found the .mrl files as being MIPSEB MIPS-III ECOFF executable not stripped - version 185.252 anyone have an idea how to read them and see what they do?
The cube 3 software generates and stores a lot of images. This is likely an internal image generator. Go find the cube user files on the PC. You will find everything ever created.
Also know there is an image stored in firmware. If you press and hold the smiley on the info page (cube screen) a cube 3 team image appears.