@themelle said in Minor bugs in the RepRapFirmware Configuration Tool:
M566 accepts values in mm/min, so if you input 0.34mm/sec in the RRF Configuration Tool, 20.4 is what you really do want the have in the resulting M566 command
Absolutely, 20.4 is what you want in the M566 command if you type in 0.34mm/sec in the RRF Configuration tool.
I'm not sure you want 20.400000000000002 though?
Sleepless,
I'm not related to Duet3D or Think3dPrint3d , but I read this thread and felt strongly enough to respond. Please do not take this to anything other than a post to try to educate and not any attempt at chastisement (nor am I trying to derail the thread.)
Im not tech savvy like that and dont understand what alot of that is talking about.
Then you've put yourself in an interesting position by attempting this replacement.
can i please get a direct line with a support member this forum takes way too long
The support provided for the Duet boards is second to none IMHO. I think that Duet and T3P3 have been extremely patient since the start of the thread.
Well every other 3d printer company offers support and I can spend time chatting with them learning about their machines. And recieve normal troubleshooting help and not have to use a forum to wait for a response. I know how my printers work. I know how the fw works, but this is another level of knowledge, and I am admitting my ignorance and requesting someone to take me by the hand and walk me through this like any other companies support would do if requested of them.
I don't understand, you buy an (extremely complicated) part , and expect the part manufacturer to walk you through installing it into existing printer (and there are are many,many, many different types out there).
To draw and analogy - If you had bought a car, I can well understand that you would expect support on the product in regards to how to use it (e.g. how to use the lights, turn on the stereo etc). However, would you buy a generic car engine to put into say, a BMW and then expect that car engine manufacturer to sit on the phone, helping you install it and answering questions the whole way?
No, they would expect you to have the pre-requisite knowledge before attempting the installation (or at least to have fully read the manual) and really only ask for some kind of support if the product wasn't doing what was expected due to a suspected product fault.
The Duet is very cheap for what it does, and I can well understand that offering the kind of phone support service you're asking for would double the cost of the board at least.
Ive been reading docs for the past week, so i am frustrated from hunting through them for answers when someone can quickly tell me an answer. I unfortunately dont have free time to sit around reading the docs, as it is the setup has had this machine down and my attention away from for for 4 days which I cant afford so it must get up and running today.
No-one can "quickly tell [you] an answer" when the information you provide is limited. Your first post was two lines, you had not explained what the full initial situation was, nor how you got there, nor the troubleshooting steps you'd performed to that date, and you've been drip feeding information since.
If you had started with a more comprehensive post a week ago, you'd have this resolved a lot quicker.
I highly recommend that you read http://www.catb.org/esr/faqs/smart-questions.html to assist you in the future.
I do have to wonder why you would attempt this replacement if you didn't understand fully what you were doing , don't have the free time and when you obviously require the machine working so badly...
@droftarts said in Bug:Object model discrepancies:
wondered if you were still running a mirror of the old RRP instructions!
Adrian did eventually host a copy on RepRapLtd, so my mirror was not so important (Although photos do not "expand" on his copy) The domain expired, although the website is still "live" on my hosting, but I was thinking the other day whether to buy the domain again (it's a uk domain so pretty cheap)
@droftarts said in Bug:Object model discrepancies:
try using userPosition rather than machinePosition.
I didn't notice that object, and that's fixed the problem.
Apologies for reporting as a "bug" prematurely. I'll be more careful about that in future! 
I guess I just need to scale my M208 to compensate for axis scaling, and everything is fine.
Solved!
Hey @droftarts!
On a personal note, nice to see you back around the RRF community! I remember you well, from the Reprap forums and back when I had to come to RepRapPro shed twice with my Ormerod2 
Aha! Interesting! I'll happily get rid of my axes scaling for now as it doesn't really affect me that much.
However as I'd like the script I'm developing to be applied across other printers in my printers community, my questions are:
i) Is there an object model model reading of M114? Or do I have to "process" it with my axis scaling?
ii) Is the application of the scaled value to M208 (thereby in my case, not allowing you to reach the value stated) intentional/wanted behaviour?
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2-beta1 (2020-09-15b1)
Duet WiFi Server Version: 1.23
Config.g - https://github.com/dandancheeseandham/cheeseandham-railcore/blob/master/RRF3.1/sys/config.g
Steps to reproduce bug:
Go to any larger non-zero XY position. e.g.
G1 X100 Y100
G1 X150 Y200
G1 X300 Y300
Confirm position with M114 and DWC
Compare against output of
echo "current machine position",{move.axes[0].machinePosition},{move.axes[1].machinePosition},{move.axes[2].machinePosition}
Object model is out on my machine by 0.27 every 100mm (so at position 300 on X or Y the position is reported as 300.810)
Additional: Axis limits via M208 seem to adhere to object model, so if I set max Y to 300 I can only go to 299.2 according to DWC/M114.
However if I set Y limit to 300.810 such as
M208 X-10:305 Y0:300.810 Z0:610
then I can go to Y300 (as read by DWC/M114) and the object model reads 300.810
I've just realised, I just need to wait for variables...
Use object model to get value and assign to variable. Make changes/run script, and then use variable to assign the previous values.
Nothing to see here! As you were!
I came here to ask for the same feature, although where I'm coming from is to really aid the transportability of scripts, and allowing them to be "future-proofed" against changes to your configuration.
For example, if I write a script which required changing the M558 A value to 5 for the duration of the script, currently I cannot reset it back to whatever the user had before at the end.
If it was possible to push any object or value previously set, I could push that existing value onto a stack, make my changes (i.e. change M558 A to 5) and then pop it back when finished.
For my own scripts, this is not an issue as I know what values I have set, but to be able to disseminate scripts to a community can be tricky - I may have no idea of what someone else's values are initially set at, and either have to write comments for people to change and keep updates in the script, or go for a logical/probable value within the community of my 3D printer.
"Future-proofing" is similar, perhaps my script changes my maximum jerk and accel for the duration of the script and resets to my (current) values at the end. If I modify my config.g values at a later date, I need to update any scripts that "change and set back" these values.
(loving RRF3 on the Duet2 BTW!)
I don't know if this is useful additional information but I asked someone with Duet Ethernet 1.02 or later + DueX5 and RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-RC1 (2020-02-08b3) to run
echo "fans[0].name :",fans[0].name
echo "fans[1].name :",fans[1].name
echo "fans[2].name :",fans[2].name
echo "fans[3].name :",fans[3].name
echo "fans[4].name :",fans[4].name
echo "fans[5].name :",fans[5].name
echo "fans[6].name :",fans[6].name
echo "fans[7].name :",fans[7].name
echo "fans[8].name :",fans[8].name
They reported that they got "Error: in file macro, line 7 column 23: array index out of bounds"
I've been investigating the object model and found that the following script resets my Duet.
Board: Duet WiFi 1.02 or later + DueX5
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-RC3 (2020-02-29b4)
Duet WiFi Server Version: 1.23
(also tested on Duet 2 3.01 RC1 and RC2)
echo "fans[0].name :",fans[0].name
echo "fans[1].name :",fans[1].name
echo "fans[2].name :",fans[2].name
echo "fans[3].name :",fans[3].name
M122 report is
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC3 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-95BLL-N6PSS-6JKD2-3SJ6M-10UMJ
Used output buffers: 3 of 24 (14 max)
=== RTOS ===
Static ram: 27916
Dynamic ram: 93976 of which 44 recycled
Exception stack ram used: 272
Never used ram: 8864
Tasks: NETWORK(ready,732) HEAT(blocked,1240) DUEX(suspended,136) MAIN(running,1924) IDLE(ready,76)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:36 ago, cause: software
Last software reset at 2020-02-29 22:51, reason: Hard fault, spinning module GCodes, available RAM 8536 bytes (slot 3)
Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00000001 ICSR 0x0041f803 BFAR 0xe000ed38 SP 0x20004f04 Task 0x4e49414d
Stack: 004043f7 b2c96804 000f0000 00000000 a5a5a5a5 200051b8 0042cad9 00000001 20001408 00000001 00000000
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 3.3ms, max retries 0
MCU temperature: min 41.1, current 42.5, max 43.1
Supply voltage: min 23.9, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2020-02-29 22:52:02
Cache data hit count 64014950
Slowest loop: 46.43ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 168, MaxWait: 546ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 1, completed moves: 1, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
trigger is idle in state(s) 0
queue is idle in state(s) 0
daemon is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 81.29ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 2c:3a:e8:0b:09:f7
WiFi Vcc 3.41, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24080
WiFi IP address 192.168.0.26
WiFi signal strength -51dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 0 0 0 0 0
M409 K"fans" is
{"key":"fans","flags":"","result":[{"actualValue":0,"blip":0.10,"max":1.00,"min":0.10,"name":"","requestedValue":0,"rpm":-1,"thermostatic":{"control":false}},{"actualValue":0,"blip":0.10,"max":1.00,"min":0.10,"name":"","requestedValue":0,"rpm":-1,"thermostatic":{"control":false}},{"actualValue":0,"blip":0.10,"max":1.00,"min":0.10,"name":"Part","requestedValue":0,"rpm":-1,"thermostatic":{"control":false}},null,null,null,{"actualValue":0,"blip":0.10,"max":1.00,"min":0.10,"name":"Hotend","requestedValue":1.00,"rpm":-1,"thermostatic":{"control":true,"heaters":[1],"highTemperature":45.0,"lowTemperature":45.0}},{"actualValue":0.38,"blip":0.10,"max":1.00,"min":0.10,"name":"Elec.Cab.1","requestedValue":1.00,"rpm":-1,"thermostatic":{"control":true,"heaters":[10],"highTemperature":55.0,"lowTemperature":35.0}},{"actualValue":0.38,"blip":0.10,"max":1.00,"min":0.10,"name":"Elec.Cab.2","requestedValue":1.00,"rpm":-1,"thermostatic":{"control":true,"heaters":[10],"highTemperature":55.0,"lowTemperature":35.0}}]}
Confirmed working, but as an addendum to anyone reading this , this does require RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-beta1+1 (2020-01-15b2)
RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-beta1 (2020-01-14b3) gives "unknown value initialDeviation.deviation" errors.
Thanks dc42
(Just so there is no misunderstanding, I'm swearing at myself for being so utterly stupid, and I really appreciate your reply and assistance @deckingman 
)