What language can IsoPod use?

[z_ruixiang]

Now I only know how to program some simple programs using Isomax. Such like Machine, State and so on. I want to know how to control several sevevo motors in Isomax. And also, what language can IsoPod use? What's the difference?

[petegray]

zhang ruixiang,

I'll leave the "How to do it in IsoMax" question to someone who knows more about IsoMax than I, although controlling multiple servos isn't difficult.

As to the languages, IsoMax is a powerful interactive development environment (not just a language). Small C and the associated Assembler are designed for developers who are more comfortable working with the C language. Example code (including source code for controlling the multiple servos of Lynxmotion's L5 robot arm) available here - http://home.attbi.com/~petegray

Regards,
-Pete.
petegray@ieee.org

[RMDumse]

As Peter suggests, you can use Small C, Assembler, IsoMax(TM), or Max-Forth(TM) currently on the IsoPod(TM). Max-Forth(TM) is under IsoMax(TM), but all the IsoMax(TM) structures can be ignored and the 'Pod can be programmed in straight "Forth". Likewise, the Small C includes and Assembler. Code can be written entirely in Assembler.

The biggest difference between Small C, Assembler, etc.; and IsoMax(TM) and Max-Forth(TM) is the later two are interactive. The development computer acts only as an intelligent terminal. The actual compilation and interaction is with the target chip. So you can find out answers to questions interactively. For instance, if you want to know the current count in the quadrature encoder register, you can query it with the language. The same is true for almost all features of the chip.

In noninteractive development environments, the host PC is used for development, and the code to be run is cross compiled, then the image of the compiled code is shoved into the traget chip. Consequently, the method of development is more, compile it and try it. If the code doesn't work, there is little in the way of tools to see what's going on inside. In very high end systems in circuit emulators are used to be able to model and interact with the circuit, and set breakpoints and traps to get somewhat of the flavor of interactivity.

Different programmers perfer different development environments. It's much a case of personal preference.