Unable to connect in Repetier Server, but successful in Repetier Host
I have a PrimaSelect P120 V3. It is a Malyan M200/Monoprice Select Mini V2(without the E3D clone hotend) rebrand.
It has the V2 firmware, and the board with the extra fan for the mainboard.
I have no issues connecting it to Cura, S3D, Repetier Host and such. But it just will not connect to Repetier Server. I have a V1 of the same printer, and it connects, allthough not without it's hickups.
How to fix this problem? I the reason I have Repetier Server Pro is to be able to run multiple printers from one location with cameras and all.
Specs:
Windows 7
USB
Tried:
Different drivers
Changing ComPort both phsically and in software
Restarting
Plugging/unplugging
New Cable
Adding Ferrite ring to USB cable
Connecting and printing og Repetier Host, Cura and S3D
All Baudrates
It has the V2 firmware, and the board with the extra fan for the mainboard.
I have no issues connecting it to Cura, S3D, Repetier Host and such. But it just will not connect to Repetier Server. I have a V1 of the same printer, and it connects, allthough not without it's hickups.
How to fix this problem? I the reason I have Repetier Server Pro is to be able to run multiple printers from one location with cameras and all.
Specs:
Windows 7
USB
Tried:
Different drivers
Changing ComPort both phsically and in software
Restarting
Plugging/unplugging
New Cable
Adding Ferrite ring to USB cable
Connecting and printing og Repetier Host, Cura and S3D
All Baudrates
Comments
The connection sumbol changes from RED to AMBER back and forth
Every time the connection state changes to AMBER I have like a window of a couple of seconds to for example adjust the fan speed. So the printer IS listening for what the server software has to say It just seems the server software is not listening.
Both versions seem to communicate, see no problem there. What I see are missing "ok" replies resulting in " Warning: Missed line detected - correcting buffer usage."
That server switches between amber and red means it sees the port but the response lets it think it is not working correctly. Normally baud rate or firmware mismatch. If you enable logging you might see some communication in the log file.
And yes I see in the log that there is some communication now and then, just seems they are not in sync like the other softwares
Not much, but it is what is in the logfile after adjusting the fanspeed and getting response from the printer
It is MARLIN firmware of some sort, so that is not the issue. As I get it to talk to all other software. But is there a way to make the server software to force communication like the others do? As the other softwares have two ways com it should be possible to make it work.
When you connect with host, how long does it take until you see some responses from the firmware?
I have already seen firmwares that start with a fancy intro screen, but showing that blocked communication. Will try adding such a delay and see if I can add a variable to wait longer for such firmwares.
If you look into server do you see a message like "No valid response seen within 10 seconds from printer, restarting connection" and what does server.log show when trying to connect? Normally you only see
and then communication is working. After 3 seconds it will ask for some data and if it does not get anything after 10 seconds it will show the above error message.
Since you have no response at all I suspect a problem with DTR/RTS function of the serial connection. All printers I know either ignore them or use them to reset the board. So we use it to reset the board as well setting them to false and then to true. Originally they were used for hardware flow control so it may have such a function in your case. Meaning that having these 2 signals high get interpreted as "please do not answer", which would pretty much explain the problem. On due native port for example I can only communicate with DTR set to true. Could you test your connection using coolterm
http://coolterm.en.lo4d.com/download
which is a dump serial terminal. In Options->Terminal select line mode and in SerialPort you can select connection speed and initial state of RTS and DTR pin. Test if can for example issue M119 and get an answer. If with some DTR/RTS combinations you get no answer I know what to do.
On which OS are you trying this with the server?
I ended up pressing connect/disconnect rapidly, and BANG it connected to Octoprint via PI
Changing monitoring state from 'Connecting' to 'Offline'
On server you can also try reconnect by deactivate and activate in printer menu. If that would succeed after some tries like with octoprint I can not say since we toggle the signal.
In step 2 of add new printer I eventually get
"No understandable response recieved ...."
but the home screen and device list show that the V2 printer toggles between connected (yellow) and disconnected (red) every few seconds.
I would be happy to beta test any fix you might have.
Thanks
Regarding beta test, subscribe our tweet. I will post there if a beta is available. But current version is not complete so I have no versions except inside my debugger.