Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9755
Posted: 10:57pm 26 Mar 2019
Copy link to clipboard
Print this post
UPDATE!
Yes, the NEW command DOES seem to matter in a big way. If I issue NEW first, THEN type in AUTOSAVE and paste the code in, everything works - INCLUDING the VAR SAVE. There is no CPU exception at all, and the code runs as it should.
That is interesting.
If I now restart the system, stop it with CTRL-C and ask the command-prompt for the value of VOLUME, it reports it exactly as it should be, so it now appears to be working. Obviously, AUTOSAVE does not issue a NEW in the background first, but for some reason I thought it did.
EDIT: This is where I read that....
[Quote=MM Manual, Page 54]This mode is terminated by entering Control-Z which will then cause the received data to be saved into program memory overwriting the previous program.[/Quote]
So, I thought that doing this would effectively be a NEW, as it 'Overwrites' the previous program.
We now have a workaround, so I will continute with the 5.0501 firmware.Edited by Grogster 2019-03-28Smoke makes things work. When the smoke gets out, it stops!
PeterB Guru Joined: 05/02/2015 Location: AustraliaPosts: 655
Posted: 11:03pm 26 Mar 2019
Copy link to clipboard
Print this post
G'Day Grogster
If you go back to Jan 24 and read the last few bits it will all become clear. If you remember you wanted to knock my block off at one stage But why does MMEDIT not fix the fault?
Peter
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9755
Posted: 11:22pm 26 Mar 2019
Copy link to clipboard
Print this post
I did? Sorry....
Yes, I will have to have a re-read.Smoke makes things work. When the smoke gets out, it stops!