Sometime Soon.any update on when it will release?
Where is 'here' ?Hmmm....what happened to the link that was here? Can somebody PM it to me? Thanks!
That is one heck of a chip for $4 direct from Microchip. I hope RevEd is working on a PICAXE emulator for it.Found it...it was a ChipKit...Microchip 32-bit MCU in a DIP package...nice!
But in this case the Mercedes is MUCH cheaperKeep things in perspective of course- it's perhaps akin to using a late model Mecedes for a shopping hack when a simpler Smart car would be far easier to get to grips with.
"Few weeks" eh?It'll keep you busy for a few weeks until PE6 emerges.
The upcoming version of the PICAXE Program Editor (PE)...supposed to have a bunch of new features / functionality...at least, that's what the rumor mill turns out.Sorry to seem stupid. What is PE6?? I did an advanced search on the Forum and came up with nothing.
Help.
Jims
The upcoming version of the PICAXE Program Editor (PE)...supposed to have a bunch of new features / functionality...at least, that's what the rumor mill turns out.
The DS18B20 is not an i2c device but a 1-Wire device.... it sure would be nice to have support for more of the unique i2C devices. Like the current "readtemp" command for the DS18B20 device.
A really cool idea would be a generic simulated I2C device.
Just an icon that you assign an I2C address to, and it then shows a set of generic registers at that I2C address.
This would let the simulation read and write to the registers, but you set the registers according to the datasheet of the specific device you want.
QUOTE]
Such a generic i2c device simulation could be useful.
Use a PE directive to set the generic i2c device slave address
The popup window then showing say 24 ($0 to $18) sequential registers with the ability to accept data via the i2cout command and return data via the i2cin command.
If a PICAXE i2c command writes/reads multiple data bytes, then starting at the designated location/register (per normal i2c syntax) write to or read from that location and increment the register after each byte.
As an idea on some i2c device register requirements:
SAA1064 – 8 bytes for control of 4 digits
DS1307 / DS1338 RTC - 8 bytes for time and control
DS1337 RTC - 16 resisters for timer and alarms
DS3232 RTC - 18 registers that might generally be used for timer and alarms plus setup also temp.
CMP03 compass module – 16 registers
SRF08 Ultrasonic range finder – 36 registers but most users likely only use the first 5 or 7 registers
MCP23017 – IO Expander - 21 registers ($0 to $15)
Probably something for PE V6.1 at this stage . . .
Then as a parallel idea, we can have a generic SPI device that operated in much the same manner.