The homing operation is it’s own function too. But, even the M2 Nano’s speed codes are all off by 8.9% (comparing the chinese software code with the actual values). You might require small bit of multiplication there. And the formulas for that are pretty much linear. You’re converting a 16-bit number into an amount of time to wait. ![]() The type of board is set in all the software because it shifts. They would actually scale with regard to the CPU used and are basically always just fed into a counter thing. The speedcodes don’t really need to be right, at least not really. I’d actually code up the egv parser a lot differently now, since I better understand the states its setting. I don’t actually think the code would be that massive especially with my better understanding. The EgvParser code is actually a lot smaller than the devices code as a whole. But attiny84 has two PWM ports that aren’t hardware serial ports, and really has 8 GPIO ports free that aren’t RESET or serial.īut an ESP32 is much more capable and only a few dollars. Just like on the m2nano, you might want a schmitt trigger as a gate drive for the mosfet for clean engraving. This would probably fit on the attiny84 but I’d be worried about it working with softusb I’d think you would still want a USB interface chip rather than using softusb. Getting the frequencies and divisors set up to mimic the configuration on the 8051 could well be the trickiest part. (Obviously can give a better answer, that’s just what makes sense to be breezing through it.)Īfter the relatively easy task of parsing the language, I’d think that getting the speed codes right would be the primary challenge for faithfully implementing the lhymicro-gl language on an arduino, since it looks like their interpretation isn’t 100% clearly understood, looking at LaserSpeed.py:get_acceleration_for_speed(). You can start reading it from the EgvParser:parse() method followed by parse_egv if you are interested. It feels to me like “1000 lines of code” (more than 100, fewer than 10,000) to implement this language on Arduino, where you would have a much larger buffer to avoid stuttering. I think that the question starts with “will there be an Arduino sketch that implements the lhymicro-gl language?” There’s a python implementation of it in LhystudiosDevice.py in meerk40t to learn from. The guess was that the bar moving for the Y needs more oomph.ĭatasheets for all the primary chips (has 2 A4988s) There’s also that section where it clearly has some lineouts from the processor go to the active pins.Īlso for a kinda unknown reason the X stepper chip has a R470 resister and the Y-stepper chip has a R360 resistor. I’ve sort of wanted to cap one of those chips and dump that firmware. The 8051 tends to have up to, I think, 4k firmware space which is where the interpretation code would be. ![]() I also corrected where I called the CH341A a serial chip, its really a universal USB interface chip and runs in Parallel mode for the M2 Nano specifically EPP 1.9. The only thing that’s even slightly unique or identifying is that the CH341A/B tends to have a version number which can be requested and differs from board to board a lot depending on the run. Damn thing doesn’t even have an eeprom to store a serial number. The entire rig doesn’t do math and doesn’t have memory. A couple bytes in the processor, but that’s it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |