Perhaps if you post a link to a working .hvs file, we can have a look if writing to or converting to that format can be easily supported.
Thanks, Maht and ahoeben for your replies! I’m out of town and away from my working computer at the moment. WHen I get home, I’ll generate a working .hvs and post it here.
Thanks again,
Marc
Guest maht
I raised this in our development standup and it's unlikely we're going to support it on our roadmap, but contributions are always welcome. I'd suggest opening an issue on our github.
Hi maht and ahoeben. I'm back at my computer and am including a link to a working .hvs file. Any help in this direction is appreciated. I will also explore your github as suggested, maht.
Here's a benchy that works on our machine.
Thanks!
Marc
The file you posted looks like a normal gcode file to me. The only thing that makes it a little special is the very first line of the file. Could you try the following:
* slice a file with Cura
* save it as a .gcode file
* rename it to .hvs (make sure it does not become .hvs.gcode!)
* open the file in a text editor (eg notepad)
* as the very first line, insert the following:
M911 3DP-310F
* save the file and try to print it
Thank you SO much for helping with this, ahoeben. I did get it to work once I'd realized that Mac OS was hiding the additional extensions. It would be so nice if the actual Cura profile could save directly in .hvs. I feel like that would be an easy edit to make to the code of the existing profile, but I've not worked with these profiles before and wouldn't know where to start.
Writing .hvs instead of .gcode is not something that can be done in a Cura profile. It can be done with a plugin, but writing plugins isn't for everybody; there's no guide or tutorial to follow for this exact usecase.
Guest maht
Good to hear progress has been made. @mcrompton, if a plugin for this is something you'd like to explore, there's relevant documentation here.
- 1 month later...
On 2/18/2020 at 10:05 PM, mcrompton said:Thank you SO much for helping with this, ahoeben. I did get it to work once I'd realized that Mac OS was hiding the additional extensions. It would be so nice if the actual Cura profile could save directly in .hvs. I feel like that would be an easy edit to make to the code of the existing profile, but I've not worked with these profiles before and wouldn't know where to start.
Hi could you give me some assistance getting Cura to work with my Cubicon single. Cura already has the first line in the code and I have altered the file type to .HVS but the machine doesn't see the file.
- 1 month later...
If anyone knows a work around to output a gcode file that has an extension of .hvs for Cubicon Style 3D printer I would appreciate it! Thank you!
Recommended Posts
Guest maht
Interesting, wasn't aware of this format. We don't have one of these printers to test so it's difficult to support this printer, especially if they decided to use a proprietary file format.
If the profile contributor wants to add support to Cura for their profile, then you can get in contact with them for this.
It was contributed by this person it seems: https://github.com/HUNIBEST-HyVISION
Just a hunch for a workaround: what happens if you zip the output gcode and change the zip extension to .hvs?
Our .ufp format works in a similar way. It could be that there's some extra printer-specific metadata in their format.
Hope this helps
Link to post
Share on other sites