Hi!
I’m starting with my first smoothieware-based board and it’s almost working fine. I can print using webinterface (uploading GCode to SD card) and I can connect using Repetier and Pronterface. I also have an TFT32 LCD, which connects to second serial on the board (MKS). All programs and LCD works fine, I can move, set temperature, etc etc….
The problema is when I try to print. The printer starts to move (let’s say the first 5 GCode lines) and then stop. I can’t send anymore any command using the same interface. Ex: If I start printinf using Repetier (USB Serial), after some lines, printer stop and I can’t send any commands using Repetier anymore, printer simple doesn’t reply. But If I go to WebInterface, I can do anything, move, change temperature, etc… Also, temperature control still working, so the board itself is not freezed.
I know about the cable length (USB). But the same problem ocours with LCD, which has a 40cm flat cable direct on the board! Exactly the same problem! So my guess is not the length of cable or interference.
If I copy the same GCode to SD, printer works fine!
MKS is considered toxic to the Smoothie project and community. It is a closed-source derivative of open-source work, and doesn’t respect the community that created the work it profits from. Helping MKS is like helping destroy the project we all worked so hard to make. As such we respectfully request that for MKS-related problems you please ask MKS for help before asking the community.
If they are ultimately not able to help you, you are welcome to ask here again, we are not refusing to help you, only asking that MKS is asked before the community is asked.
This is even more true in this case as it looks like your problem is very specific to MKS hardware.
That’s the point: I don’t think it’s hardware related problem. I know about this ‘problem’ with MKS, but as I told in another topic, unfortunatelly I can’t afford anotherd board right now. In the future, sure I’ll, but it’s impossible for me right now, specialli living here, in Brazil, with unreal customs taxs and other taxs.
Anyway, I really don’t think it’s a hardware problem, otherwise nothing would work (not even start communication). About configuratio, I have these lines related to communication:
uart0.baud_rate 250000 # Baud rate for the default hardware serial port
second_usb_serial_enable true # This enables a second usb serial port (to have both pronterface
# and a terminal connected)
The point isn’t that we don’t want to help you, or that you are forced to get a Smoothieboard, but it’s that you need to ask MKS for help before you ask for help here.
Once you have asked them for help, if you have not received it, you can then ask here.
When I say it’s a hardware problem, I mean it’s a problem that is specific to the MKS hardware, we’ve seen other users complain about this and it was only users of MKS boards. This is even more reasons to talk to MKS about it, even putting aside the fact that they are toxic to the project.
About your config, are you sure you should be using a 250000 baudrate ? 115200 should be less prone to problems. Also why did you enable the second usb serial port ? It has nothing to do with the UART port.
This is why I asked here before MKS……for example this second port: I didn’t now that was about second USB port, I tought it was for phisical second port. I’ll disable and try to slow down baud rate.
Also, I tried to connect using pronterface and eth connection, but it’s now working. I’m using the latest version of pronterface (get from Github) on windows, but getting this error when I try to connect (using TCP Stream mode, as recomended). I’m not sure this is a problem with Smoothie, it’s more like to be a problem with Pronterface. But since it’s the last available version and docs from Smoothie say that it works, I’m asking if there’s any know problem with this error?!
Connecting...
Traceback (most recent call last):
File "C:\Users\jonis\Downloads\Pronterface Files\Printrun-master\printrun\pronterface.py", line 1073, in connect
if not self.connect_to_printer(port, baud, self.settings.dtr):
File "C:\Users\jonis\Downloads\Pronterface Files\Printrun-master\printrun\pronsole.py", line 725, in connect_to_printer
self.p.connect(port, baud, dtr)
File "C:\Users\jonis\Downloads\Pronterface Files\Printrun-master\printrun\printcore.py", line 46, in inner
return f(*args, **kw)
File "C:\Users\jonis\Downloads\Pronterface Files\Printrun-master\printrun\printcore.py", line 210, in connect
"\n" + _("Serial error: %s") % e)
File "C:\Python27\lib\encodings\utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe3 in position 57: invalid continuation byte
Please ask MKS first. It’s a rule of this forum, you have to follow it. After you have done so, and if they are not able to help you, you are welcome to ask here again, but please understand this is a rule and you have to follow it. We realize you did nothing wrong, but we have to fight toxic companies like MKS, and that means we have to have these rules, and users like you have to respect them.
I swear, I tried. But they make fools of themselves. I explained for days what’s going on, send configs, etc etc….they simples said that the problem is because I don’t have G28 in my code! WTF!
Then, they said to remove my heatedbed……WTF again?!
Just to explain: I don’t have G28 because I always do manually homing and calibrate my printer before printing. Now, has anyone had this serial problem? I can’t print using Windows Host and TFT32, the same problem on both: starts to print, runs about 5 or 10 lines, then stop. But the board is not freezed/halted, I can access (by ethernet) and control everything.
Tried with pronterface and repetier host. Both connect and control printer perfectly (movements, commabds, etc). But after starting a printing, run some lines (something between 5 and 10 lines) then stop. The board itsel works fine, heaters still working and keeping specified temp. Also, I can access using web and move/control printer.
Tried with 2 different computers and one notebook.
That’s extremely strange and I can’t find any explanation for it. Are you using the latest version of the firmware and configuration file ? I can’t see any other thing to try.
Rather than start a new thread just now, I am watching this thread closely. I don’t have the MKS board but the new Re-Arm board. I am seeing the exact same issues as the OP. I was going to come here to see what I could find out before asking for help but wanted to let you know it appears to not be specific to only the MKS or it’s a coincidence that I am having the exact same symptoms.
