Communication Problems
-
This is wrong:
Supply voltage: min 0.0, current 1.1, max 1.1, under voltage events: 0, over voltage events: 0
It should be around 12V or whatever your VIN voltage is.
Please check with a multimeter that you really are getting 12V or 24v (depending on your power supply at the VIN terminal block.
-
I tested my power cord that plugged into a regular wall socket at 110V and the multimeter read 113V. I then plugged the cord into the power supply for the printer and tested the wires that hook up to the board and they read about 21V.
Does that seem like a normal reading? -
Was that 21V reading with the board connected to the power supply?
What power supply are you using?
-
No that reading was from the leads from the power supply which was plugged into a wall socket.
I am using the power supply that came with the D300VS printer. The number on it is DA16082403420. It has a built in fan that automatically turns on and off and has the option of changing the input voltage that it receives from the outlet (115/230V)Also if this helps at all, when the power supply is hooked up to the board and I turn it on the printers LED lights do come on along with the hot end fan,
-
Does anybody have any suggestions?
-
When you mean M122 and got the voltage reading of 1.1V in the report, did you definitely have VIN power applied, and was the blue LED definitely lit? Please run that test again to make sure.
-
What do you mean by VIN power?
-
He means external power connected to the screw terminals, something between 12v and 24v.
-
Hey guys!
I have come to the conclusion that my multimeter was broken! I borrowed my buddies and it is giving me a reading of 27.3 DC volts at the terminals on the board. I believe that is normal right? -
Yes, although 27v is a little high, we recommend 25V maximum.
-
This is the new M122 Command, I believe everything looks right
Used output buffers: 1 of 32 (1 max)
=== Platform ===
Memory usage:
Program static ram used: 20304
Dynamic ram used: 74064
Recycled dynamic ram: 3936
Current stack ram used: 3288
Maximum stack ram used: 4120
Never used ram: 28648
Last reset 00:00:52 ago, cause: power up
Last software reset code not available
Error status: 0
[ERROR] Error status: 0Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 10.3, current 15.1, max 16.7
Supply voltage: min 0.0, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Current date and time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.000656; fastest: 0.000031
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle
telnet is idle
file is idle
serial is ready with "M122"
aux is idle
daemon is idle -
I sent the G28 command and hit send and the head started going down towards the bed until it randomly stopped about 5 inches down. I tried it again and the same thing keeps happening.
Any suggestions? -
I suggest you test X, Y and Z homing individually until they are all working. Make sure that your M574 command in config.g is correct, and make sure that your homez.g file is correct according to whether you are using a microswitch or a Z probe to home Z. See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_files.
