| |
Page 6 of 6 |
| Author |
Message |
mozzie Guru
 Joined: 15/06/2020 Location: AustraliaPosts: 469 |
| Posted: 10:15am 22 Oct 2026 |
Copy link to clipboard |
 Print this post |
|
G'day Peter / Phil, I am seeing the same symptoms on the PicoMiteHDMIBTH V7.00.00RC3 as Phil.
As suggested, removing the CDC device and unplug / plug in the USB drive restores normal operation. The copy then transfers as normal.
After a successful transfer the HELP.txt file is all there but will only list to "FRAME" directly, however HELP ZMODEM* works so it must be a limitation of the list command. (598559 bytes)
Regards, Lyle. |
| |
flip Senior Member
 Joined: 18/07/2016 Location: AustraliaPosts: 135 |
| Posted: 10:37am 22 Oct 2026 |
Copy link to clipboard |
 Print this post |
|
Thanks for the confirmation Lyle, I can also confirm exactly same.
Regards Phil |
| |
ville56 Guru
 Joined: 08/06/2022 Location: AustriaPosts: 646 |
| Posted: 12:49pm 22 Oct 2026 |
Copy link to clipboard |
 Print this post |
|
Peter,
just trying to get both, the internal clock and the RTC clock as close as possible to NTP time. When setting OPTION MILLISECONDS ON it seems that the millisecond counter is never set to 0 when updating the time. The manual says:
"The milliseconds counter is set to zero whenever the time is updated using the TIME command, WEB NTP command or RTC GETTIME command."
Whatever I use to set the time, the milliseconds counter always just seems to count up continuously. Can be confirmed by measuring the elapsed time for the time-setting command and adding the milliseconds to the start value.
Environment: PicoMitePC3 MMBasic USB RP2350B Edition V7.00.00RC3
Gerald 73 de OE1HGA, Gerald |
| |
matherp Guru
 Joined: 11/12/2012 Location: United KingdomPosts: 12051 |
| Posted: 06:11pm 22 Oct 2026 |
Copy link to clipboard |
 Print this post |
|
I'm modifying the code so that web ntp will set the accurate milliseconds - the information is in the ntp packet. RTC AUTO will then only update every 24 hours after the last web ntp. This should give clock accuracy to within 10 or so milliseconds |
| |
ville56 Guru
 Joined: 08/06/2022 Location: AustriaPosts: 646 |
| Posted: 06:48pm 22 Oct 2026 |
Copy link to clipboard |
 Print this post |
|
Thanks Peter,
the ntp solution sounds great.
But it also concerns TIME$="..." here the millisecond is also not reset. TBH, I found no function that actually resets milliseconds.
Gerald 73 de OE1HGA, Gerald |
| |
matherp Guru
 Joined: 11/12/2012 Location: United KingdomPosts: 12051 |
| Posted: 07:00pm 22 Oct 2026 |
Copy link to clipboard |
 Print this post |
|
All will now reset it to zero except ntp which will set it correctly |
| |
flip Senior Member
 Joined: 18/07/2016 Location: AustraliaPosts: 135 |
| Posted: 11:35pm 23 Oct 2026 |
Copy link to clipboard |
 Print this post |
|
Does anyone know a way (without relying on 'ON ERROR') to check for the existence of C: drive? There is a command:MM.INFO$(SDCARD) for the B: drive...I couldn't find anything similar for C: ?
Also a possible bug, on a fresh boot with no USB drive plugged in, I get an unexpected result
?MM.INFO(EXISTS DIR "C:/") 1 (PC2 version 7 RC3 latest) Regards Phil PS When plugging and unplugging USB drives, the following messages are displayed, so I'm guessing there might be a way to 'know' it somehow> USB Flash Drive Connected (addr 2) > USB Flash Drive Disconnected Regards Phil Edited 2026-10-24 16:21 by flip |
| |
| |
Page 6 of 6 |