<p>I am using a BAUDrate of 115200 since I cannot make a connection to my printer with the advised 250000 rate. Are there any downsides or limits I reach earlier given by the lower BAUDrate?</p>

[{'answer_id': 1506, 'author': 'Tormod Haugene', 'author_id': 115, 'author_profile': 'https://3dprinting.stackexchange.com/users/115', 'pm_score': 3, 'selected': True, 'text': '<p><a href="https://learn.sparkfun.com/tutorials/serial-communication/rules-of-serial" rel="nofollow noreferrer">Baud rate</a> is the rate at which information is transferred in a communication channel, given as a number of bits per second (bps). So a baud rate of 250000 is capable of transferring a <em>maximum</em> of 250000 bits per second (31250 bytes/s). When working with serial ports, both ends of the communication line will have to &quot;talk&quot; with the <a href="https://www.quora.com/How-do-we-connect-two-devices-with-different-baud-rates" rel="nofollow noreferrer">same speed</a> - the same baud rate - to understand each other.</p>\n<p>So when using a baud rate of 11520 you will theoretically be limited to transfer data with about half the speed of 25000. If you are transferring large amounts of data, this might be a limiting factor for your application, but if you are not pushing the limits of your serial port, it probably won\'t matter at all.</p>\n'}, {'answer_id': 1507, 'author': 'darth pixel', 'author_id': 1211, 'author_profile': 'https://3dprinting.stackexchange.com/users/1211', 'pm_score': 2, 'selected': False, 'text': '<p>If your printer doesn\'t have an SD card then the whole communication between computer and arduino is performed "live". There is kinda buffer of data which arduino can swallow. Then it needs to process it (and then can send some reports to your app) and then arduino is ready to get new "set" of instructions to work on.</p>\n\n<p>Now. If a baudrate is to low then there could be a situation when arduino finishes its job and has to wait for new bite of data. In such a situation you can see the printer pauses printing as it waits for signals from arduino as it waits for data from computer. That\'s more or less a downside of a low baudrate.</p>\n\n<p>If you have a SD card then the data is sucked from it but reports are still send by port to show results on screen. In such situation you can see sligtly late screen update.</p>\n\n<p>A screen means just a fun of live preview but breaking printing process (caused by late data send) means your hot nozzle stays over the same position which can destruct a surface or even fry up a plastic a bit. It also oozes and therefore creates lasting artifacts.</p>\n\n<p>Resuming - low baudrate is evil ;)</p>\n'}, {'answer_id': 14907, 'author': 'FarO', 'author_id': 2338, 'author_profile': 'https://3dprinting.stackexchange.com/users/2338', 'pm_score': 2, 'selected': False, 'text': "<p>If a GCODE line is about 30 characters (which is about the norm), you can send at most 420 of them per second at 115200 bps.</p>\n<p>If each GCODE prints 0.15 mm (for example in arcs), you would be limited to 63 mm/s in arcs/circles (straight lines are not an issue).</p>\n<p>If that's limiting for you, then you should find a way to set 250 kbps.</p>\n<p>You don't mention the firmware you use, but if you use Klipper, which compresses data over the serial line, connection speed is not an issue.</p>\n"}]
['https://3dprinting.stackexchange.com/questions/1505', 'https://3dprinting.stackexchange.com', 'https://3dprinting.stackexchange.com/users/168/']