hi there, im running on
windows 10,
rambo mini board from V1
drivers for rambo installed , bit and baud rate the same. board has power and shows up in my device manager on windows.
but when trying to connect on repetier host i get the message,
so start signal detected - forcing start
What program are you trying to connect with, what rates are the same as what, is it plugged in?
im using Repetier Host to connect to the Rambo.
the rates are 115200 (250000 is not an option in my port settings)
com3 is the port. both are the same in RH and device manager.
i have tried other rates too but the same outcome.
i have tried to connect with local host on and off also.
The board is flashed at 250000, so you will need to reflash if your computer can’t do that.
so im trying to reflash . followed the instructions on v1.
changed the board name and baud rate in configuration.h
at the end im getting this message
bootloader file specified but missing: c:\users\ultra laptop\appdata\local\arduino15\packages\rambo\hardware\avr\1.0.0\bootloaders\stk500boot_v2_mega2560.hex
then on uploading i get the following timeout message. (see photo)
i even put the hex file into the bootloader folder and it looks like more communication is happening with the board. the rx light blinks from time to time, but the same message comes up.
even tryed doing the reset button trick.
Arduino 1.9, link in the instructions.
i have now tryed to use the beta version of arduino 1.9 and im getting the same message
You followed my pictures and installed the json file, selected the right com port, powered it up?
They are test flashed at least twice before they are shipped. So there must be a missed step.
You should not have that many tabs and the buad rate should be 250000.
Did you ever get Repetier working? Same problem
What is the problem you are having Dave? We need to get the same sort of info as we got from Helmet. What board do you have? Are the drivers installed? Which COM port is it on? What firmware are you trying to install? Screen shots would help a lot…
Well, the problem I WAS having was that Repetier would connect to the MKS Gen L V1.0, but in manual mode, the commands would queue but not get executed. The “No start received” message was mixed in there someplace Troubleshooting at the Repetier site suggested that this command queuing was due to communication being one way only (I found similar results when I tried Pronterface, which was also available.)
Note that my firmware must be OK because I had complete control of the machine using the RepRap discount full graphic display. So it clearly pointed to some sort of communication problem over the USB. I checked/corrected the port and baud rate, but no success. The only suspicious issue was that I had used a USB 3.0 extension cable because the short one that came with the MKS was insufficient.
This was confirmed when I tried again this morning when I found it possible to connect to Repetier using only the short cable and with no steppers connected. It was apparent in the log file that the gcode commands were actually getting sent to the MKS, which was not evident yesterday. .
Connecting everything back up this PM using a longer USB cable with no extension found everything working, and in fact, I was able to nicely print the crown
Why did it get fixed? I have no idea really. Was it the USB extension? Maybe, but everything was power cycled and Repetier was closed and restarted. Bottom line is it’s working I’m responding here so that there is closure to my inquiry.
Thanks for your support.
Some cheaper USB products are designed for power and not data. Perhaps that’s what the extension is?
