Bluetooth Problem with V0.92.8 on Ramps 1.4 with JY-MCU modul
Hi there,
in order to use Bluetooth I have updated my Repetier Firmware from V0.91 to V0.92.8. I´m currently using a Ramps 1.4 with an LCD- Screen (conroler: Smartcontroller from RepRapdiscount on a ramps or rumba board) and wanted to connect with my JY- MCU modul at AUX1 as described in the wiki: http://reprap.org/wiki/Jy-mcu
I managed to get it working and now I´m able to connect to Repetier Host V1.60 via Bluetooth and control my printer. But the LCD screen is flickering if the JY- MCU modul is just inserted into the AUX1 port and not connected to the host. Besides that the temperature values (heat bed and extruder) are changing permanently. If I connect the JY- MCU modul to the host wireless the problem is gone and everything is fine.
I spent a couples of hours searching on the internet for this issue and found nothing. Due to the fact that the connection of the modul generally works fine for me - besides the mentioned issues above - I assume that this problem has to do with the beta state of the firmware.
Is this issue know? Thanks a lot for your reply.
Frank
in order to use Bluetooth I have updated my Repetier Firmware from V0.91 to V0.92.8. I´m currently using a Ramps 1.4 with an LCD- Screen (conroler: Smartcontroller from RepRapdiscount on a ramps or rumba board) and wanted to connect with my JY- MCU modul at AUX1 as described in the wiki: http://reprap.org/wiki/Jy-mcu
I managed to get it working and now I´m able to connect to Repetier Host V1.60 via Bluetooth and control my printer. But the LCD screen is flickering if the JY- MCU modul is just inserted into the AUX1 port and not connected to the host. Besides that the temperature values (heat bed and extruder) are changing permanently. If I connect the JY- MCU modul to the host wireless the problem is gone and everything is fine.
I spent a couples of hours searching on the internet for this issue and found nothing. Due to the fact that the connection of the modul generally works fine for me - besides the mentioned issues above - I assume that this problem has to do with the beta state of the firmware.
Is this issue know? Thanks a lot for your reply.
Frank
Comments
Frank