Home
JAQForum Ver 20.06
Log In or Join  
Active Topics
Local Time 15:52 25 Apr 2024 Privacy Policy
Jump to

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.

Forum Index : Microcontroller and PC projects : Pico Lipo Issues

     Page 2 of 2    
Author Message
pwillard
Senior Member

Joined: 07/06/2022
Location: United States
Posts: 274
Posted: 01:55pm 30 Aug 2022
Copy link to clipboard 
Print this post

I believe it is due to MMCC's (justified) expectation that there is no delay between ">" prompts.  When a "NEW" command is issued, which MMCC does before sending "AUTOSAVE", the result is that MMCC will "timeout" and give up.

But to be clear... the DELAY with ">" prompt is specific to the PicoLipo for some reason.
Edited 2022-08-31 00:00 by pwillard
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 8578
Posted: 02:06pm 30 Aug 2022
Copy link to clipboard 
Print this post

Please try the attached with teraterm (any other terminal problem is an SEP)

NB: will erase all options


PicoMite.zip
 
Tinine
Guru

Joined: 30/03/2016
Location: United Kingdom
Posts: 1646
Posted: 02:40pm 30 Aug 2022
Copy link to clipboard 
Print this post

Not to muddy the waters but my preferred method is to select-copy the source and then, at the MMCC prompt, type AUTOSAVE -> Enter, paste the code followed by Ctrl-Z.

Subsequently use the UP arrow key to avoid having to retype AUTOSAVE.
Edited 2022-08-31 00:40 by Tinine
 
pwillard
Senior Member

Joined: 07/06/2022
Location: United States
Posts: 274
Posted: 02:43pm 30 Aug 2022
Copy link to clipboard 
Print this post

Erase all options... no big deal... this is all experimenting now...

Anyway... whatever you did...  fixed it.  No delays in Teraterm getting a ">" prompt back and MMCC is now behaving again...




Issuing a "NEW" command no longer causes the excessive delay in getting back to ">" and additional <CR> are not delayed in getting the prmpt back (as it was before) so the behavior is again matching what is expected.  :)

Thanks.
Edited 2022-08-31 00:49 by pwillard
 
     Page 2 of 2    
Print this page


To reply to this topic, you need to log in.

© JAQ Software 2024