Micro-Robotics logoOverviewManuals and TutorialsDatasheetsApplication NotesCircuit SchematicsDownload VenomDownload VenomIDECode SnippetsFonts and ImagesSerial File TransferFAQPrice ListAsk us a questionVM1
Micro-Robotics icon Resources submenu link

Bug reports

Occasionally we find bugs in the current release of Venom2 or VenomIDE which may affect users. Usually a 'workaround' is possible. Bug reports and any workarounds applying to recent releases are documented on this page.

Bug reports for older releases of Venom2 are documented in the Release Notes.

Bug report for Venom 2

Release 2017-09-10

No bugs reported

Release 2016-10-03

No bugs reported

Release 2016-08-25

Bug: Graphics LCD debug output
Cause: When making a GraphicsLCD object in the VM2D, several lines of debug output appear on serial port 1.
Workaround: None
Fixed: In the next version
In previous versions: No

Release 2015-12-01

Bug: Touch screen reports phantom touches
Cause: Due to a low default touch threshold setting in the TouchScreen object, false (phantom) touches are sometimes reported.
Workaround: Use Touch.Value = n to set a higher threshold. Try n = 5. Note that setting very high thresholds prevents touches being detected close to one edge of the display.
Fixed: In the next version
In previous versions: Yes

Release 2015-09-01

Bug: filesystem.Find("") locks file system and returns 0
Cause: Two separate bugs: fs.Find("") should behave like fs.Find("/") and return 2 for a directory; also fs.Find("") was leaving the file system locked.
Only the empty string triggers this behaviour.
Workaround: None
Fixed: In the next release
In previous versions: Yes

Release 2015-05-20

Bug: Large programs using Class can get corrupted.
Cause: Programs that use user-classes and a large number of global names can fail during download or at runtime. Several failure modes are possible; the one seen is that the class name becomes "Undefined" after a reset.
Workaround: None
Fixed: In the next release
In previous versions: Yes

Release 2015-01-20

Bug: VM2 repeatedly resets. Only means of recovery is to remove the battery for a while before restarting
Cause: This is possible if the Flash filesystem cache control area gets corrupted in certain ways. Invalid values are now detected and the cache destroyed.
Workaround: None, other than removing battery to force loss of cache info
Fixed: In the next release
In previous versions: Yes

Release 2015-03-18

Bug: Serial Parity wrong
Cause: Some serial port settings with parity enabled were not correct.
Workaround: None
Fixed: In the next release
In previous versions: Yes

Bug: Long delays in HTTP server response
Cause: This can happen if the clock/calendar has not been set up and there is no internet connection. HTTP tries to use internet time servers if the clock/calendar is not valid, and can wait a long time if no servers respond.
Workaround: Make sure clock is valid, and if necessary write a value to clock.Time to start it.
Fixed: In next release, HTTP will only use the clock/calendar for time information, and will not send a Date: header at all if the clock/calendar is not running.
In previous versions: Yes

Bug: Flash file system loses data after reset
Cause: If a system was reset or powered off while the Flash file system was in the process of flushing its cache (writing to the flash memory), the mechanism for re-doing the write when the sytem restarted did not work properly.
Workaround: None
Fixed: In the next release
In previous versions: Yes

Bug: string.Value(float) does not skip white space
Cause: Applies only to floating point number conversions
Workaround: use string.Flush to remove blanks first
Fixed: In the next release
In previous versions: Yes

Release 2015-01-20

Bug: VM2 repeatedly resets. Only means of recovery is to remove the battery for a while before restarting
Cause: This is possible if the Flash filesystem cache control area gets corrupted in certain ways. Invalid values are now detected and the cache destroyed.
Workaround: None, other than removing battery to force loss of cache info
Fixed: In the next release
In previous versions: Yes

Release 2014-12-09

Bug: Constant Arrays of Pointers
Cause: The pointer values are not decoded from the array correctly and so point to the wrong values.
Workaround: None
Fixed: In the next release
In previous versions: Yes

Release 2014-10-08

No bugs reported

Bug report for VenomIDE

This section lists known bugs in recent releases of VenomIDE.

Release 2.2.0.18 (current)

No bugs reported

Release 2.2.0.16

Bug: Exception: <<<:>>> or TextBlock at the end of a file
Cause: VenomIDE will crash with an exception if either <<< or TextBlock syntax are used at the end of a file.
Workaround: Put a dummy comment at the end of the file. If the triggering condition is in the saved file then you may have to open the file in another text editor to change it.
Fixed: In the next release
In previous versions: Yes

Release 2.2.0.15

Bug: Exception: unbalanced quote at the end of a file
Cause: VenomIDE will crash with an exception if a quoted string that lacks the closing quote is the last text in a file.
Workaround: Put a dummy comment at the end of the file. If the triggering condition is in the saved file then you may have to open the file in another text editor to change it.
Fixed: In the next release
In previous versions: Yes

Release 2.2.0.14

Bug: Exception: comment on last line of file
Cause: VenomIDE will crash with an exception if there is a comment on the last line of a file.
Workaround: None
Fixed: In the next release
In previous versions: Yes