'Table' commands - which chips?

mjy58

Member
I was originally going to reply to this thread, but think a new thread is more suitable.

Can someone explain exactly which chips the 'table' commands work with?

Programming Editor (5.5.0) 'Quick Syntax checker' states:

Command Chips applies to
table 20X2, 28X2,40X2, 28x1, 40X1
tablecopy 14M2, 20M2
readtable 14M2, 20M2, 20X2, 28X2, 40X2, 28X1, 40X1

Online manual 2 states:

Command Chips applies to
table 14M2, 18M2, 20M2, 20X2, 28X2, 40X2, 28X1, 40X1
tablecopy 14M2, 18M2, 20M2
readtable 14M2, 18M2, 20M2, 20X2, 28X2, 40X2, 28X1, 40X1

The 18M2+ is not specifically listed, but the online command reference states it works with all three commands.
 

westaust55

Moderator
Table memory applies for all X2, X1 and M2 parts including the 18M2+ but not the 08M2 and the original 18M2

This may help you with respect to the M2 parts : http://www.picaxe.com/docs/picaxem2.pdf


Programming Editor (5.5.0) 'Quick Syntax checker' states:
It would also be recommended that you upgrade to the PE V5.5.1 as there are some updates for the M2 parts:
5.5.1 Added 'Continue anyway?' option on start of duplicate instance Updated to version 2.4 compiler - M2 X2 Added 'ultra' command for ease of use of SRF005 ultrasonic sensor - M2 Added missing NAND and NOR operators - M2 Added missing outpinB.PIN, outpinC.PIN definitions - All Added write/read/peek/poke support for WORD option with the s_W? variables - All Removed the limit of 100 Cases within a single Select..EndSelect Corrected the following on-screen simulation issues: - resume/suspend/restart on 08M2 now supports all 4 tasks
 

mjy58

Member
Table memory may apply to all those chips, but which of the table commands applies?

The above list indicates that tablecopy does not apply to any 'X' chips
 

westaust55

Moderator
Correct, the TABLECOPY command is only applicable for the M2 chips. The "online" and pdf manual files both indicate the same situation.
 

mjy58

Member
Ok, I think I have the picture.

My original problem was that PE and the manual were not consistent on any of the commands, but a split across X and M types does make more sense. Presumably, then, implementation of tablecopy is dependent on chip structure.

I will upgrade PE to 5.5.1.
 
Top