Hi Tiga Leung .
Sorry. Only Fuji PIDs are compatible with artisan at this moment.
There are many PIDs and they all work different. The only ones that work with artisan are the Fuji PIDs model PXR and model PXG. Plus, they also need to be equipped with the modbus protocol option in order to be able to communicate with a PC.
If the Fuji PID is compatible with an RTD, then it will work with artisan.
The Arduino TC4 is cheaper and the hardware and software is open source. Requires some knowledge. It is being develop at this moment and it is already capable of controlling the roaster from artisan.
Cheers
--- On Wed, 6/22/11, Tiga Leung <hihitiga(a)yahoo.com.hk> wrote:
From: Tiga Leung <hihitiga(a)yahoo.com.hk>
Subject: Questions [Could I use PT-100 instead of K-thermocouple]
To: artisan-user-owner(a)lists.einfachkaffee.de
Date: Wednesday, June 22, 2011, 2:59 AM
Dear all,
I am a new user to use the software. I tried my PID with the software. I cannot use the software properly. It could not communicate with the PID. Could I use PT-100 to measurse temperature? Did any one try PT-100 before?
Regards and thanks,
Tiga
It would be nice to have an event alarm with sound.
Moreover, I'd like to save my cup profile settings inside the default
scrolling window so I can recall it for any new roast. I use the IIAC
(Istituto Internazionale Assaggiatori Caffè) cup profile form that is a
specific form for espresso.
Thanks.
Rubens Gardelli
Italy
Hi
Any chance that National Instrument
USB-9211A<http://sine.ni.com/nips/cds/view/p/lang/en/nid/201881>will
be supported within a few months ?
If not which of the already supported PID devices is most recommended ?
Regards Kenneth
Dear all,
First of all we would like to thank you all for your feed-back during the
beta testing of this new release. Several bug fixes and improvements made it
just in time.
Although some of the new features of release 0.5.0 have already been
introduced in the beta versions, here is quick summary of what you can
expect with this release:
- Unlimited number of devices/curves running at the same time
- Virtual devices
- Profile designer
- Wheel graph editor
- Mathematical plotter
- Localizations (translations for German, French, Spanish, Swedish,
Italian)
- Enhanced multi-core CPU performance
- Template/background reproduction playback aid
- Alarms with programmable outputs
- Custom event buttons
- Fully configurable cupping graphs
- Enhanced delta plotting
- Mac OS X 10.4 support
- Omega HHM28 support
- Enhanced Arduino TC4 support
As you start using Artisan 0.5.0, you will notice that ET and BT have been
switched around compared to 0.4.1. This was necessary in order to support an
unlimited number of devices. We apologize for the inconvenience.
You can find the binaries for Windows and Mac at the usual place (Linux
version is to be published):
http://code.google.com/p/artisan/downloads/list
Please report using our issue tracker at
http://code.google.com/p/artisan/issues/list
and this mailing list.
Thank you for your continuous support. We look forward to your feed-back and
input.
Regards,
The Artisan team
Hi!
I tried to test the b2 but twice during the same roast it generated an exception and closed down, so i had to give up and revert to b1, wich worked fine. :-(
I don't use any fancy functions at all, not even the HUD. Just started up artisan, saved a file, added some roast properties and pressed the on button. Both times it worked well for 3-4 minutes and the suddenly generated a windows error. Before shuting down it worked well, noticably faster than b1.
I use a HP mini with only 1Gb RAM and running XP 32-bit.
I would also like to suggest that the Axis max value is the one used whenever doing a reset. Reset currently sets the x axis to 1 if the keep max time after reset is not checked.
It appears that the BT delta plot still has the 50 deg offset. It refreshes
the display when I select event or extra menu but immediately jumps right
back with the next data point reading.
Oh and I also generated an exception error for the first time and crashed
Artisan so could not save or finish the roast profile.
Fred
Hi zb,
I have scanned and selected the correct COM port in Artisan. If I select the same COM port with the Omega software it works, select the same port with Artisan I get errors. I'm not trying to run Artisan and Omega at the same time. I worked on this all weekend and have tried everything I can think of.
Is it possible that something has changed with the Omega? Is there some way I can view the communications between the Omega software and the COM port and the communications between Artisan and the COM port so that I can compare?
Regards
Paul
> From: artisan-user-request(a)lists.einfachkaffee.de
> Subject: Artisan-User Digest, Vol 5, Issue 9
> To: artisan-user(a)lists.einfachkaffee.de
> Date: Mon, 6 Jun 2011 02:24:42 +0200
>
> Send Artisan-User mailing list submissions to
> artisan-user(a)lists.einfachkaffee.de
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.mokelbu.de/listinfo/artisan-user
> or, via email, send a message with subject or body 'help' to
> artisan-user-request(a)lists.einfachkaffee.de
>
> You can reach the person managing the list at
> artisan-user-owner(a)lists.einfachkaffee.de
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Artisan-User digest..."
>
>
> Today's Topics:
>
> 1. relased 0.5.0 beta 2 (zb)
> 2. Omega HH806AU problem (Paul Wynne)
> 3. Re: Omega HH806AU problem (Rich Helms)
> 4. Re: Omega HH806AU problem (zb)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 5 Jun 2011 05:21:08 -0700 (PDT)
> From: zb <zauborg(a)yahoo.com>
> Subject: [Artisan-user] relased 0.5.0 beta 2
> To: artisan-user(a)lists.einfachkaffee.de
> Message-ID: <807844.91911.qm(a)web121605.mail.ne1.yahoo.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Dear all.
>
> Enhancements and additions were made to the previous beta 1 thanks to the collaboration of? volunteers. This new beta version brings fully configurable cupping graphs, better time annotations, an enhanced arduino TC4 support, an enhanced multi-core CPU support (runs faster on CPUs with more than one core), and bug fixes.
>
> The artisan team ask for your support testing this new version in an effort to improve the quality and extend the features of the software. Your help and ideas are welcome and an important contribution to the success of this project.
>
> You can find the binaries for Windows and Mac at the usual place (Linux version is to be published):
>
> http://code.google.com/p/artisan/downloads/list
>
> Please report using our issue tracker at
>
> http://code.google.com/p/artisan/issues/list
>
> and this mailing list.
>
> Thanks,
> The Artisan team
>
Hi All,
I have just purchased a Quest M3 and Omega HH806AU datalogger and am having problems getting Artisan to connect to the Omega. No matter what I try I get the "HH806AUtemperature(): 0 bytes received but 14 needed" error and BT & ET display "-1". I have tried everything I can think of and Artisan will not connect. The PC software supplied by Omega finds the COM port, connects and works perfectly.
My laptop is running Windows 7 x64 SP1. I have tried using the USB drivers supplied with the Omega and I have tried downloading the latest drivers from http://www.ftdichip.com/Drivers/VCP.htm. I have tried COM ports 11, 7 & 2. I have tried another laptop running Windows 7 x32. I have tried another USB cable. I have tried Artisan 4.1, 5.0b1 and 5.0b2. I have tried removing USB drivers, Omega software and doing a system restore and reinstalling just the USB drivers.
I believe I have tried everything except swapping the Omega, the Omega works perfectly with the Omega software so I don't think that is the issue.
Please help, any ideas would be appreciated.
Regards
Paul
Dear all.
Enhancements and additions were made to the previous beta 1 thanks to the collaboration of volunteers. This new beta version brings fully configurable cupping graphs, better time annotations, an enhanced arduino TC4 support, an enhanced multi-core CPU support (runs faster on CPUs with more than one core), and bug fixes.
The artisan team ask for your support testing this new version in an effort to improve the quality and extend the features of the software. Your help and ideas are welcome and an important contribution to the success of this project.
You can find the binaries for Windows and Mac at the usual place (Linux version is to be published):
http://code.google.com/p/artisan/downloads/list
Please report using our issue tracker at
http://code.google.com/p/artisan/issues/list
and this mailing list.
Thanks,
The Artisan team
aArtisan release 1.05 is now available in zip file here:
http://tc4-shield.googlecode.com/files/aArtisan-REL-105.zip
View description, etc. here:
http://code.google.com/p/tc4-shield/downloads/detail?name=aArtisan-REL-105.…
This release should fully support the upcoming 0.5.x release of Artisan.
Thanks to Sebastien and the Artisan team for their persistence in
working out the little bumps in getting Artisan and aArtisan to
communicate smoothly.
Jim
On Thu, Jun 2, 2011 at 9:50 PM, PIDKits <pidkits(a)gmail.com> wrote:
> Success!
>
> Here is what I checked:
>
> 1. Startup OK
> 2. Stop/start OK
> 3. Change units to C OK
> 4. Change units back to F OK
> 5. Reset OK
>
> The commands are echoing exactly the way I believe they should be. Wonderful!
>
> Many thanks for your hard work on this.
>
> Next, I need to take the time to learn about the custom buttons. I
> will do this, and report back to you with results. But for now, I
> believe this is ready to go. I will put a release together and let
> you know when it has been posted.
>
> Thanks again.
>
> Jim
>
>
> On Thu, Jun 2, 2011 at 9:45 PM, PIDKits <pidkits(a)gmail.com> wrote:
>> I will let you know.
>>
>> On Thu, Jun 2, 2011 at 9:46 PM, Sebastien Delgrande
>> <sebastien(a)delgrande.org> wrote:
>>> OK. There you have it. I have updated the exe. Can you see if it is fine
>>> this time?
>>>
>>> http://dl.dropbox.com/u/30502234/artisan.zip
>>>
>>> Thanks,
>>>
>>> Seb
>>>
>>> -----Original Message-----
>>> From: PIDKits [mailto:pidkits@gmail.com]
>>> Sent: Thursday, June 02, 2011 9:30 PM
>>> To: Sebastien Delgrande
>>> Subject: Re: [Artisan-user] Artisan serial data format
>>>
>>> The startup code works perfectly. I can see the CHAN command,
>>> followed immediately by UNIT, followed by READ's. Well done.
>>>
>>> There is an issue when using the ON and OFF button. Each press of the
>>> ON button causes a reset on the Arduino. As a result, it reverts back
>>> to its default settings for CHAN and UNIT.
>>>
>>> I think it will be necessary to execute the initial startup sequence
>>> each time ON is pressed. (Note: OFF sometimes causes a reset, and
>>> sometimes does not. But since ON always causes one, the behavior with
>>> the OFF button is not relevant).
>>>
>>> Jim
>>>
>>> On Thu, Jun 2, 2011 at 9:23 PM, PIDKits <pidkits(a)gmail.com> wrote:
>>>> Yes, I will let you know right away.
>>>>
>>>> On Thu, Jun 2, 2011 at 9:23 PM, Sebastien Delgrande
>>>> <sebastien(a)delgrande.org> wrote:
>>>>> Jim,
>>>>>
>>>>> I have made the modification. Can you download the latest exe and try?
>>>>>
>>>>> http://dl.dropbox.com/u/30502234/artisan.zip
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Seb
>>>>>
>>>>> -----Original Message-----
>>>>> From: PIDKits [mailto:pidkits@gmail.com]
>>>>> Sent: Thursday, June 02, 2011 7:41 PM
>>>>> To: Sebastien Delgrande
>>>>> Subject: Re: [Artisan-user] Artisan serial data format
>>>>>
>>>>> I think you are correct that the message is a garbled combination of
>>>>> CHAN and UNIT.
>>>>>
>>>>> I think we should send the CHAN command repeatedly until it is
>>>>> acknowledged, probably flushing the buffer each time. Then we could
>>>>> do away with the 3 second delay?
>>>>>
>>>>> The other alternative, which I have used successfully on other
>>>>> applications, is to use a RESET command. The reply is "# Reset".
>>>>> Only the first four letters of a keyword are read, so we cannot use
>>>>> READY ;-)
>>>>>
>>>>> I think either alternative is fine. But it might be easier to use
>>>>> CHAN since we already have that one programmed. But I am happy to go
>>>>> either way.
>>>>>
>>>>> Jim
>>>>>
>>>>>
>>>>> On Thu, Jun 2, 2011 at 6:54 PM, Sebastien Delgrande
>>>>> <sebastien(a)delgrande.org> wrote:
>>>>>>>>I see on the screen is "UNIT;F200", or "UNIT;C200" My display is
>>>>>>
>>>>>> What??? I have no clue why you would see that! I have checked again and
>>>>>> there is no such code going on...
>>>>>>
>>>>>>>> I have not seen any instance of the CHAN command, however.
>>>>>>
>>>>>> Ah, I may have an idea then!
>>>>>>
>>>>>> Could it be that the first message which is CHAN;1200\n does not get
>>>>>> processed by the Arduino and then gets overwritten (how on earth is that
>>>>>> possible)? I have a 3 sec delay after the
>>>>>>
>>>>>> Should we:
>>>>>> - Make the CHAN command a compulsory communication initialization
>>> command
>>>>>> that needs to be acknowledge before we fire any READ command or send a
>>>>>> READY\n command to which we wait for a READY\n reply (hand-shake)?
>>>>>> - Flush the serial buffer before every command we send? I only flush it
>>> to
>>>>>> start with but I could do that already.
>>>>>>
>>>>>> Tell me and I upload a new exe.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: PIDKits [mailto:pidkits@gmail.com]
>>>>>> Sent: Thursday, June 02, 2011 5:47 PM
>>>>>> To: sebastien(a)delgrande.org
>>>>>> Subject: Re: [Artisan-user] Artisan serial data format
>>>>>>
>>>>>> Success .... mostly!
>>>>>>
>>>>>> There seems to be a small issue upon initial startup. The string that
>>>>>> I see on the screen is "UNIT;F200", or "UNIT;C200" My display is
>>>>>> limited to 9 characters, so it is possible what I am seeing is a
>>>>>> truncated version. Since the TC4 code only looks at the first
>>>>>> character following UNIT, though, the command is still recognized and
>>>>>> the units are set correctly.
>>>>>>
>>>>>> Subsequent changes in units (using the Artisan menu) result in
>>>>>> "UNIT;C" or "UNIT;F" and also work correctly.
>>>>>>
>>>>>> The READ command is being accepted and is working fine.
>>>>>>
>>>>>> I have not seen any instance of the CHAN command, however. Since I
>>>>>> expect that you send that early in the startup, my guess is that it is
>>>>>> getting sent too early, or that it is not terminated with a newline?
>>>>>>
>>>>>> We are very close! I wish there was something I could do with the
>>>>>> Artisan code to help.
>>>>>>
>>>>>> Jim
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 2, 2011 at 5:02 PM, sebastien(a)delgrande.org
>>>>>> <sebastien(a)delgrande.org> wrote:
>>>>>>> Jim,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I may have found the bug (just looking at the code, so no certainty).
>>> Can
>>>>>>> you download the exe again and let me know if it works?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> http://dl.dropbox.com/u/30502234/artisan.zip
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>> On June 2, 2011 at 2:13 PM PIDKits <pidkits(a)gmail.com> wrote:
>>>>>>>
>>>>>>>> Here is the log file:
>>>>>>>>
>>>>>>>> Traceback (most recent call last):
>>>>>>>> File "artisan.py", line 12668, in scanforport
>>>>>>>> File "serial\serialwin32.pyc", line 30, in __init__
>>>>>>>> File "serial\serialutil.pyc", line 260, in __init__
>>>>>>>> File "serial\serialwin32.pyc", line 68, in open
>>>>>>>> File "serial\serialwin32.pyc", line 177, in _reconfigurePort
>>>>>>>> ValueError: Cannot configure port, some setting was wrong. Original
>>>>>>>> message: [Error 1] Incorrect function.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Jun 2, 2011 at 1:24 PM, sebastien(a)delgrande.org
>>>>>>>> <sebastien(a)delgrande.org> wrote:
>>>>>>>> > Thanks Jim.
>>>>>>>> >
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > There is still a 3 seconds delay after the port is opened. I did not
>>>>>>>> > change
>>>>>>>> > that part. I probably messed up in the serial communication though.
>>>>>>>> > Wasn't a
>>>>>>>> > log file generated (in the folder of Artisan.exe)? I bet you that my
>>>>>>>> > error
>>>>>>>> > handling is flawed... ;-)
>>>>>>>> >
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > Seb
>>>>>>>> >
>>>>>>>> > On June 2, 2011 at 12:21 PM PIDKits <pidkits(a)gmail.com> wrote:
>>>>>>>> >
>>>>>>>> >> Hi, Sebastien -
>>>>>>>> >>
>>>>>>>> >> Unfortunately, the new version is not communicating with the
>>> Arduino.
>>>>>>>> >>
>>>>>>>> >> I believe that the communication parameters are OK because the
>>>>> Arduino
>>>>>>>> >> resets after pressing the Artisan ON button. This reset is an
>>>>>>>> >> indication that the serial port has been opened.
>>>>>>>> >>
>>>>>>>> >> But I am seeing no command strings coming from Artisan. I have the
>>>>>>>> >> TC4 set up to echo every string it receives, triggered by the \n
>>>>>>>> >> character. Even an unrecognized command would be echoed to the
>>> LCD.
>>>>>>>> >> But I am seeing nothing being echoed.
>>>>>>>> >>
>>>>>>>> >> I think there is a chance that Artisan is sending its first command
>>>>>>>> >> too soon after opening the COM port? It takes a second or so for
>>> the
>>>>>>>> >> Arduino to reset after sensing the port opening. This is built
>>> into
>>>>>>>> >> the hardware. So it is safest for Artisan to delay a little after
>>>>>>>> >> opening the port, or try sending commands repeatedly until an
>>>>>>>> >> acknowledgement is received.
>>>>>>>> >>
>>>>>>>> >> I do see the RF2000 and RC2000 commands coming from the previous
>>>>>>>> >> Artisan beta release, but not from the version I just downloaded
>>> from
>>>>>>>> >> your dropbox.
>>>>>>>> >>
>>>>>>>> >> Jim
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >> On Thu, Jun 2, 2011 at 11:59 AM, PIDKits <pidkits(a)gmail.com> wrote:
>>>>>>>> >> > OK. I understand.
>>>>>>>> >> >
>>>>>>>> >> > 1. I will enable the # ack's for the CHAN command (only)
>>>>>>>> >> > 2. There is no comment sent before, or after, a READ command.
>>> No
>>>>>>>> >> > change required.
>>>>>>>> >> > 3. I will disable the # ack's for the port and write commands
>>>>>>>> >> > 4. I will download the zip and give things a try!
>>>>>>>> >> >
>>>>>>>> >> > Thanks.
>>>>>>>> >> >
>>>>>>>> >> > Jim
>>>>>>>> >> >
>>>>>>>> >> > On Thu, Jun 2, 2011 at 10:38 AM, sebastien(a)delgrande.org
>>>>>>>> >> > <sebastien(a)delgrande.org> wrote:
>>>>>>>> >> >>> Yes, that sounds great. A few things to keep in mind:
>>>>>>>> >> >>> 1. The CHAN command only needs to be sent once. It is sticky.
>>>>>> It
>>>>>>>> >> >>> doesn't hurt to send multiple times, but not needed.
>>>>>>>> >> >>
>>>>>>>> >> >> Yes, I understood that. I coded that way.
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>> 2. The CHAN command will respond with a "# Active channels set
>>>>> to
>>>>>>>> >> >>> xxxx\n" acknowledgement if the command was understood.
>>>>>>>> >> >>
>>>>>>>> >> >> I handled the response and log the error if not a comment.
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>> 3. Any input from the TC4 that begins with "#" is a comment
>>> and
>>>>>>>> >> >>> should be ignored by Artisan.
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >> You are not sending a comment first before the values in reply
>>> to
>>>>>>>> >> >> the
>>>>>>>> >> >> READ
>>>>>>>> >> >> command or are you?
>>>>>>>> >> >>
>>>>>>>> >> >>> 4. If it would be easier, I can disable all of the "#"
>>>>>>>> >> >>> acknowledgements?
>>>>>>>> >> >>
>>>>>>>> >> >> The custom buttons will not be able to handle it right now. I
>>> will
>>>>>>>> >> >> add
>>>>>>>> >> >> it
>>>>>>>> >> >> for the next release. Maybe it would be nice to disable for the
>>>>>>>> >> >> WRITE
>>>>>>>> >> >> and
>>>>>>>> >> >> port commands?
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>> I did not know that. I will have to study the docs to figure
>>> out
>>>>>>>> >> >>> how
>>>>>>>> >> >>> to do that! These commands also respond with an
>>> acknowledgement
>>>>>>>> >> >>> message that begins with "#", but this can be disabled if
>>> needed.
>>>>>>>> >> >>
>>>>>>>> >> >> Yes, disable it just for now.
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>> So, I think you are suggesting that I proceed with release of
>>> the
>>>>>>>> >> >>> enhanced aArtisan?
>>>>>>>> >> >>
>>>>>>>> >> >> Yes, I would like that!
>>>>>>>> >> >>
>>>>>>>> >> >>> Is there a way that I would be able to test it? I am not set
>>> up
>>>>>> to
>>>>>>>> >> >>> create executables from python source, unfortunately.
>>>>>>>> >> >>
>>>>>>>> >> >> I have created them for you to try. I have put a zip for you in
>>> my
>>>>>>>> >> >> DropBox:
>>>>>>>> >> >> http://dl.dropbox.com/u/30502234/artisan.zip. It would help if
>>> you
>>>>>>>> >> >> could
>>>>>>>> >> >> give it a rough try. I remoted to my home machine in order to
>>> make
>>>>>>>> >> >> the
>>>>>>>> >> >> change in Artisan. The interface works but I have no way of
>>>>>> remotely
>>>>>>>> >> >> attaching the TC4 and see if it actually works as you can
>>> imagine.
>>>>>>>> >> >> Let
>>>>>>>> >> >> me
>>>>>>>> >> >> know!
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >>
>>>>>>>> >> >> Thanks a lot,
>>>>>>>> >> >>
>>>>>>>> >> >> Sebastien
>>>>>>>> >> >>
>>>>>>>> >> >> On June 2, 2011 at 9:49 AM PIDKits <pidkits(a)gmail.com> wrote:
>>>>>>>> >> >>
>>>>>>>> >> >>> Hi, Sebastien -
>>>>>>>> >> >>>
>>>>>>>> >> >>> I understand time shortages! I think it is amazing what your
>>>>> team
>>>>>>>> >> >>> has
>>>>>>>> >> >>> accomplished so far, so please don't think I was being
>>> critical.
>>>>>>>> >> >>>
>>>>>>>> >> >>> > Here is what I suggest:
>>>>>>>> >> >>> > 1 - I take 10 minutes right now to replace the RF2000\n and
>>>>>>>> >> >>> > RC2000\n
>>>>>>>> >> >>> > commands by hard-coded CHAN setup then READ\n.
>>>>>>>> >> >>>
>>>>>>>> >> >>> Yes, that sounds great. A few things to keep in mind:
>>>>>>>> >> >>> 1. The CHAN command only needs to be sent once. It is sticky.
>>>>>> It
>>>>>>>> >> >>> doesn't hurt to send multiple times, but not needed.
>>>>>>>> >> >>> 2. The CHAN command will respond with a "# Active channels set
>>>>> to
>>>>>>>> >> >>> xxxx\n" acknowledgement if the command was understood.
>>>>>>>> >> >>> 3. Any input from the TC4 that begins with "#" is a comment
>>> and
>>>>>>>> >> >>> should be ignored by Artisan.
>>>>>>>> >> >>> 4. If it would be easier, I can disable all of the "#"
>>>>>>>> >> >>> acknowledgements?
>>>>>>>> >> >>>
>>>>>>>> >> >>> > 2 - The code is there already for users to take advantage of
>>>>>> OT1,
>>>>>>>> >> >>> > OT2,
>>>>>>>> >> >>> > and
>>>>>>>> >> >>> > IO3 as per custom buttons. Same with the DWRITE, AWRITE
>>>>>> commands.
>>>>>>>> >> >>>
>>>>>>>> >> >>> I did not know that. I will have to study the docs to figure
>>> out
>>>>>>>> >> >>> how
>>>>>>>> >> >>> to do that! These commands also respond with an
>>> acknowledgement
>>>>>>>> >> >>> message that begins with "#", but this can be disabled if
>>> needed.
>>>>>>>> >> >>>
>>>>>>>> >> >>> Here is a link to the files required for the current, enhanced
>>>>> TC4
>>>>>>>> >> >>> code:
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>
>>>>>
>>> http://tc4-shield.googlecode.com/svn/applications/Artisan/aArtisan/trunk/src
>>>>>> /aArtisan
>>>>>>>> >> >>>
>>>>>>>> >> >>> To compile this new version, the following library must be
>>>>> present
>>>>>>>> >> >>> in
>>>>>>>> >> >>> the user's libraries folder:
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>
>>>>>
>>> http://tc4-shield.googlecode.com/svn/applications/libraries/trunk/libraries/
>>>>>> cmndproc
>>>>>>>> >> >>>
>>>>>>>> >> >>> So, I think you are suggesting that I proceed with release of
>>> the
>>>>>>>> >> >>> enhanced aArtisan?
>>>>>>>> >> >>>
>>>>>>>> >> >>> Is there a way that I would be able to test it? I am not set
>>> up
>>>>>> to
>>>>>>>> >> >>> create executables from python source, unfortunately.
>>>>>>>> >> >>>
>>>>>>>> >> >>> Jim
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>>
>>>>>>>> >> >>> On Thu, Jun 2, 2011 at 9:11 AM, sebastien(a)delgrande.org
>>>>>>>> >> >>> <sebastien(a)delgrande.org> wrote:
>>>>>>>> >> >>> > Hi Jim,
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >> I'm beginning to see that the enhanced Artisan / TC4
>>> interface
>>>>>>>> >> >>> >> is
>>>>>>>> >> >>> >> probably not going to make it into the upcoming release.
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > Well, I am sorry I could not find the time yet to create the
>>>>> new
>>>>>>>> >> >>> > TC4
>>>>>>>> >> >>> > CHAN
>>>>>>>> >> >>> > config window but apart from that I would say that we can go
>>>>>> with
>>>>>>>> >> >>> > the
>>>>>>>> >> >>> > new
>>>>>>>> >> >>> > code! Thanks for the wake-up call. Very tight at work at the
>>>>>>>> >> >>> > moment...
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > Here is what I suggest:
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > 1 - I take 10 minutes right now to replace the RF2000\n and
>>>>>>>> >> >>> > RC2000\n
>>>>>>>> >> >>> > commands by hard-coded CHAN setup then READ\n.
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > 2 - The code is there already for users to take advantage of
>>>>>> OT1,
>>>>>>>> >> >>> > OT2,
>>>>>>>> >> >>> > and
>>>>>>>> >> >>> > IO3 as per custom buttons. Same with the DWRITE, AWRITE
>>>>>> commands.
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > How does that sound? I think it would be a huge step forward
>>>>> and
>>>>>>>> >> >>> > the
>>>>>>>> >> >>> > next
>>>>>>>> >> >>> > version can include the CHAN setup.
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >> I've done some testing using the Artisan 0.5.1b release, and
>>>>>>>> >> >>> >> found
>>>>>>>> >> >>> >> that I needed to reverse the order of ET and BT in the TC4
>>>>>>>> >> >>> >> output.
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > Yes, Rafael confessed to have inverted them.
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >> I really hope the Artisan team proceeds with the enhanced
>>>>>>>> >> >>> >> interface
>>>>>>>> >> >>> >> with the TC4 because I think it would be widely used. Let
>>> me
>>>>>>>> >> >>> >> know
>>>>>>>> >> >>> >> if
>>>>>>>> >> >>> >> there is anything else I can do to help.
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > Definitely!
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > Thanks,
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > Sebastien
>>>>>>>> >> >>> >
>>>>>>>> >> >>> > On June 2, 2011 at 8:47 AM PIDKits <pidkits(a)gmail.com> wrote:
>>>>>>>> >> >>> >
>>>>>>>> >> >>> >> Hi, Sebastien -
>>>>>>>> >> >>> >>
>>>>>>>> >> >>> >> I'm beginning to see that the enhanced Artisan / TC4
>>> interface
>>>>>>>> >> >>> >> is
>>>>>>>> >> >>> >> probably not going to make it into the upcoming release.
>>> I've
>>>>>>>> >> >>> >> been
>>>>>>>> >> >>> >> watching the list messages and understand that there is much
>>>>> to
>>>>>>>> >> >>> >> be
>>>>>>>> >> >>> >> done just to support the currently planned upgrades.
>>>>>>>> >> >>> >>
>>>>>>>> >> >>> >> If that's the case, I think it is best if I release a
>>> version
>>>>>> of
>>>>>>>> >> >>> >> aArtisan.pde that supports only the interface that will be
>>>>>>>> >> >>> >> active,
>>>>>>>> >> >>> >> i.e., RF2000\n and RC2000\n commands.
>>>>>>>> >> >>> >>
>>>>>>>> >> >>> >> I can also provide a pre-release version of the TC4 code
>>> with
>>>>>>>> >> >>> >> the
>>>>>>>> >> >>> >> enhanced command set for the Artisan team to use for testing
>>>>>> new
>>>>>>>> >> >>> >> commands if you would like.
>>>>>>>> >> >>> >>
>>>>>>>> >> >>> >> I've done some testing using the Artisan 0.5.1b release, and
>>>>>>>> >> >>> >> found
>>>>>>>> >> >>> >> that I needed to reverse the order of ET and BT in the TC4
>>>>>>>> >> >>> >> output.
>>>>>>>> >> >>> >> I
>>>>>>>> >> >>> >> have done that, and have a tested version of aArtisan.pde
>>>>> ready
>>>>>>>> >> >>> >> that
>>>>>>>> >> >>> >> supports the current Artisan interface. It will be released
>>>>> as
>>>>>>>> >> >>> >> version 1.04. I plan to put that up as a download on the
>>>>>>>> >> >>> >> tc4-shield
>>>>>>>> >> >>> >> site today. I'll post here once that is done and ready for
>>>>>>>> >> >>> >> download.
>>>>>>>> >> >>> >>
>>>>>>>> >> >>> >> I really hope the Artisan team proceeds with the enhanced
>>>>>>>> >> >>> >> interface
>>>>>>>> >> >>> >> with the TC4 because I think it would be widely used. Let
>>> me
>>>>>>>> >> >>> >> know
>>>>>>>> >> >>> >> if
>>>>>>>> >> >>> >> there is anything else I can do to help.
>>>>>>>> >> >>> >>
>>>>>>>> >> >>> >> Jim
>>>>>>>> >> >>> >>
>>>>>>>> >> >>> >>
>>>>>>>> >> >>> >> On Mon, May 30, 2011 at 3:15 PM, PIDKits <pidkits(a)gmail.com>
>>>>>>>> >> >>> >> wrote:
>>>>>>>> >> >>> >> > Sebastien -
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> > I also thought about adding DREAD and AREAD, but then
>>>>>> stopped.
>>>>>>>> >> >>> >> > These
>>>>>>>> >> >>> >> > commands would result in the need for Artisan to read the
>>>>>>>> >> >>> >> > results, so
>>>>>>>> >> >>> >> > we will have to decide how best to format the output from
>>>>> the
>>>>>>>> >> >>> >> > TC4. I
>>>>>>>> >> >>> >> > see this as a somewhat lower priority?? But maybe I am
>>>>>>>> >> >>> >> > overlooking
>>>>>>>> >> >>> >> > something.
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> > Your understanding of the CHAN command is correct. Once
>>> the
>>>>>>>> >> >>> >> > mapping
>>>>>>>> >> >>> >> > has been done, it is sticky. CHAN would only have to be
>>>>> sent
>>>>>>>> >> >>> >> > again
>>>>>>>> >> >>> >> > if
>>>>>>>> >> >>> >> > the mapping changed for some reason. If no CHAN command
>>> is
>>>>>>>> >> >>> >> > given
>>>>>>>> >> >>> >> > at
>>>>>>>> >> >>> >> > all, the default condition is CHAN 1200, which matches the
>>>>>>>> >> >>> >> > current
>>>>>>>> >> >>> >> > default configuration.
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> > I have already written a library (class CmndBase) for a
>>>>>>>> >> >>> >> > command
>>>>>>>> >> >>> >> > interpreter. Once this library is done, then a program
>>> can
>>>>>>>> >> >>> >> > just
>>>>>>>> >> >>> >> > derive a new class from CmndBase and define only a
>>> specific
>>>>>>>> >> >>> >> > processCommand() method. It is working in well in a small
>>>>>>>> >> >>> >> > test
>>>>>>>> >> >>> >> > program, but needs a little more testing and development.
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> > My higher priority would be for the OT1, OT2, and IO3
>>>>>> commands
>>>>>>>> >> >>> >> > to
>>>>>>>> >> >>> >> > be
>>>>>>>> >> >>> >> > available through Artisan. These provide direct control
>>> of
>>>>>>>> >> >>> >> > the
>>>>>>>> >> >>> >> > SSR
>>>>>>>> >> >>> >> > and PWM drives I put on the TC4 for the purpose of
>>>>>> controlling
>>>>>>>> >> >>> >> > a
>>>>>>>> >> >>> >> > roaster. I think that these have more value to most TC4
>>>>>> users
>>>>>>>> >> >>> >> > than
>>>>>>>> >> >>> >> > the WRITE commands.
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> > NOTE: each of these new commands (except READ) throw back
>>> a
>>>>>>>> >> >>> >> > confirmation (in the form of "# some text") to Artisan. I
>>>>>>>> >> >>> >> > think
>>>>>>>> >> >>> >> > it
>>>>>>>> >> >>> >> > will be important that Artisan look for this, particularly
>>>>>> for
>>>>>>>> >> >>> >> > commands that are sent immediately after initializing
>>> serial
>>>>>>>> >> >>> >> > communications with the remote.
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> > Before officially releasing this new version of aArtisan,
>>> I
>>>>>>>> >> >>> >> > would
>>>>>>>> >> >>> >> > like
>>>>>>>> >> >>> >> > someone to test it with a version of Artisan that supports
>>>>>> the
>>>>>>>> >> >>> >> > new
>>>>>>>> >> >>> >> > features. Here is a link to the current code:
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> >
>>>>>>
>>>>>
>>> http://tc4-shield.googlecode.com/svn/applications/Artisan/aArtisan/branches/
>>>>>> TRY-NewCommands/aArtisan/
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> > If you have a chance to try it out, that would be a big
>>>>> help.
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> > Jim
>>>>>>>> >> >>> >> >
>>>>>>>> >> >>> >> > On Mon, May 30, 2011 at 2:47 PM, sebastien(a)delgrande.org
>>>>>>>> >> >>> >> > <sebastien(a)delgrande.org> wrote:
>>>>>>>> >> >>> >> >> Jim,
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >> Sorry I did not get back to you earlier... I could not
>>> test
>>>>>>>> >> >>> >> >> the
>>>>>>>> >> >>> >> >> new
>>>>>>>> >> >>> >> >> code
>>>>>>>> >> >>> >> >> this week-end either. Sorry about that.
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >> I like it though! Just a thought: For good measure,
>>>>>> shouldn't
>>>>>>>> >> >>> >> >> we
>>>>>>>> >> >>> >> >> also
>>>>>>>> >> >>> >> >> have
>>>>>>>> >> >>> >> >> DREAD and AREAD to read a pin directly?
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >> The CHAN command is great. You would only send it once to
>>>>>> set
>>>>>>>> >> >>> >> >> up
>>>>>>>> >> >>> >> >> and
>>>>>>>> >> >>> >> >> then
>>>>>>>> >> >>> >> >> use READ, correct?
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >> Also, I was trying to see if we could have the command
>>>>>>>> >> >>> >> >> "interpreter"
>>>>>>>> >> >>> >> >> in
>>>>>>>> >> >>> >> >> its
>>>>>>>> >> >>> >> >> own library so that different Arduino sketches could just
>>>>>>>> >> >>> >> >> reference
>>>>>>>> >> >>> >> >> it
>>>>>>>> >> >>> >> >> to
>>>>>>>> >> >>> >> >> interpret Artisan's command? Most command would still
>>> have
>>>>>> to
>>>>>>>> >> >>> >> >> be
>>>>>>>> >> >>> >> >> post-processed in the main sketch though. Probably little
>>>>>>>> >> >>> >> >> value
>>>>>>>> >> >>> >> >> to
>>>>>>>> >> >>> >> >> it
>>>>>>>> >> >>> >> >> unless
>>>>>>>> >> >>> >> >> you see an opportunity there.
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>>>What is the process for getting these commands active on
>>>>>> the
>>>>>>>> >> >>> >> >>>> Artisan
>>>>>>>> >> >>> >> >>>> side?
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >> Well, I think that for the current release and given its
>>>>>> Beta
>>>>>>>> >> >>> >> >> status
>>>>>>>> >> >>> >> >> already, we will only document the WRITE commands to be
>>>>> used
>>>>>>>> >> >>> >> >> in
>>>>>>>> >> >>> >> >> user
>>>>>>>> >> >>> >> >> custom
>>>>>>>> >> >>> >> >> buttons. As soon as the development resumes I will be
>>> happy
>>>>>>>> >> >>> >> >> to
>>>>>>>> >> >>> >> >> both
>>>>>>>> >> >>> >> >> change
>>>>>>>> >> >>> >> >> the serial command and implement a configuration form in
>>>>>>>> >> >>> >> >> which
>>>>>>>> >> >>> >> >> users
>>>>>>>> >> >>> >> >> can set
>>>>>>>> >> >>> >> >> their channels.
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >> Since your code should be compliant with Artisan 0.5, do
>>>>> you
>>>>>>>> >> >>> >> >> think I
>>>>>>>> >> >>> >> >> should
>>>>>>>> >> >>> >> >> include it in the release?
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >> Thanks,
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >> Sebastien
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >> On May 30, 2011 at 1:39 PM PIDKits <pidkits(a)gmail.com>
>>>>>> wrote:
>>>>>>>> >> >>> >> >>
>>>>>>>> >> >>> >> >>> Sebastien -
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> I've made a couple of changes to the draft commands (see
>>>>>>>> >> >>> >> >>> below). I
>>>>>>>> >> >>> >> >>> think that DWRITE and AWRITE are more descriptive for
>>> the
>>>>>>>> >> >>> >> >>> commands
>>>>>>>> >> >>> >> >>> that set a digital pin and that set the duty cycle for
>>> one
>>>>>>>> >> >>> >> >>> of
>>>>>>>> >> >>> >> >>> the
>>>>>>>> >> >>> >> >>> Arduino's PWM pins.
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> What is the process for getting these commands active on
>>>>>> the
>>>>>>>> >> >>> >> >>> Artisan
>>>>>>>> >> >>> >> >>> side?
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> JIm
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> Artisan TC4 Commands - revised 30May2011
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> RF2000\n return Fahrenheit temps for two channels
>>>>> (legacy)
>>>>>>>> >> >>> >> >>> RC2000\n return Celsius temps for two channels (legacy)
>>>>>>>> >> >>> >> >>> READ\n return temperatures according to current
>>> settings
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> UNITS;a\n set temperature scale
>>>>>>>> >> >>> >> >>> where a = F or C
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> CHAN;ijkl\n map logical channels to physical channels
>>>>>>>> >> >>> >> >>> where
>>>>>>>> >> >>> >> >>> i = physical channel mapped to logical channel 1 (0, 1,
>>>>> 2,
>>>>>>>> >> >>> >> >>> 3,
>>>>>>>> >> >>> >> >>> 4);
>>>>>>>> >> >>> >> >>> 0
>>>>>>>> >> >>> >> >>> means channel is off
>>>>>>>> >> >>> >> >>> j = physical channel mapped to logical channel 2
>>>>>>>> >> >>> >> >>> k = physical channel mapped to logical channel 3
>>>>>>>> >> >>> >> >>> l = physical channel mapped to logical channel 4
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> [port];ddd\n
>>>>>>>> >> >>> >> >>> where
>>>>>>>> >> >>> >> >>> ddd = output level, 0 to 100 percent on [port]
>>>>>>>> >> >>> >> >>> [port]=OT1, OT2, IO3
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> DWRITE;pp;HIGH\n or DPIN;pp;LOW\n directly set the
>>> status
>>>>>>>> >> >>> >> >>> of a
>>>>>>>> >> >>> >> >>> pin
>>>>>>>> >> >>> >> >>> (
>>>>>>>> >> >>> >> >>> digitalWrite() )
>>>>>>>> >> >>> >> >>> where pp = digital pin number
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> AWRITE;pp;ddd\n directly set the analog output level of
>>> a
>>>>>>>> >> >>> >> >>> pin (
>>>>>>>> >> >>> >> >>> analogWrite() )
>>>>>>>> >> >>> >> >>> where pp = pin number
>>>>>>>> >> >>> >> >>> ddd = output level, 0 to 255
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> Rev. 5/30/2011
>>>>>>>> >> >>> >> >>>
>>>>>>>> >> >>> >> >>> On Sat, May 28, 2011 at 4:49 PM, PIDKits
>>>>>> <pidkits(a)gmail.com>
>>>>>>>> >> >>> >> >>> wrote:
>>>>>>>> >> >>> >> >>> > Hi, Sebastien -
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > I went a bit further with aArtisan than I initially
>>>>>>>> >> >>> >> >>> > planned,
>>>>>>>> >> >>> >> >>> > but
>>>>>>>> >> >>> >> >>> > I
>>>>>>>> >> >>> >> >>> > think you will be pleased with the results.
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > Current working code can be found here:
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> >
>>>>>>
>>>>>
>>> http://tc4-shield.googlecode.com/svn/applications/Artisan/aArtisan/branches/
>>>>>> TRY-NewCommands/
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > It is easy to demonstrate the new commands using a
>>>>>>>> >> >>> >> >>> > terminal
>>>>>>>> >> >>> >> >>> > window
>>>>>>>> >> >>> >> >>> > in
>>>>>>>> >> >>> >> >>> > the Arduino IDE. They are not case sensitive, and the
>>>>>>>> >> >>> >> >>> > delimiters
>>>>>>>> >> >>> >> >>> > between tokens can be semi-colon (;), space, or comma.
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > I especially like the CHAN command. This allows you
>>> to
>>>>>>>> >> >>> >> >>> > map
>>>>>>>> >> >>> >> >>> > logical
>>>>>>>> >> >>> >> >>> > channels 1 through 4 to physical ADC channels 1
>>> through
>>>>>> 4.
>>>>>>>> >> >>> >> >>> > The
>>>>>>>> >> >>> >> >>> > output
>>>>>>>> >> >>> >> >>> > from aArtisan is arranged in order of the logical
>>>>>>>> >> >>> >> >>> > channels.
>>>>>>>> >> >>> >> >>> > So
>>>>>>>> >> >>> >> >>> > you
>>>>>>>> >> >>> >> >>> > can put BT on any ADC channel you like, and then
>>> receive
>>>>>>>> >> >>> >> >>> > the
>>>>>>>> >> >>> >> >>> > BT
>>>>>>>> >> >>> >> >>> > reading back in whichever position you prefer in the
>>>>>>>> >> >>> >> >>> > output
>>>>>>>> >> >>> >> >>> > stream,
>>>>>>>> >> >>> >> >>> > for example.
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > Default values give same result as sending
>>>>> "CHAN;1200\n".
>>>>>>>> >> >>> >> >>> > This
>>>>>>>> >> >>> >> >>> > also
>>>>>>>> >> >>> >> >>> > matches the current behavior.
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > ------------------------------------
>>>>>>>> >> >>> >> >>> > New command format: (also see comments in source)
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > RF2000\n return Fahrenheit temps for two channels
>>>>>>>> >> >>> >> >>> > (legacy,
>>>>>>>> >> >>> >> >>> > needs
>>>>>>>> >> >>> >> >>> > to
>>>>>>>> >> >>> >> >>> > eventually be abandoned)
>>>>>>>> >> >>> >> >>> > RC2000\n return Celsius temps for two channels
>>> (legacy,
>>>>>>>> >> >>> >> >>> > abandon
>>>>>>>> >> >>> >> >>> > ASAP)
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > READ\n return temperatures according to current
>>>>> settings
>>>>>>>> >> >>> >> >>> > (this
>>>>>>>> >> >>> >> >>> > still
>>>>>>>> >> >>> >> >>> > is a good choice going forward, I think)
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > UNITS;a\n set temperature scale
>>>>>>>> >> >>> >> >>> > where a = F or C
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > CHAN;ijkl\n map logical channels to physical
>>> channels
>>>>>>>> >> >>> >> >>> > where
>>>>>>>> >> >>> >> >>> > i = physical channel mapped to logical channel 1; 0
>>>>>>>> >> >>> >> >>> > means
>>>>>>>> >> >>> >> >>> > channel
>>>>>>>> >> >>> >> >>> > is
>>>>>>>> >> >>> >> >>> > off
>>>>>>>> >> >>> >> >>> > j = physical channel mapped to logical channel 2
>>>>>>>> >> >>> >> >>> > k = physical channel mapped to logical channel 3
>>>>>>>> >> >>> >> >>> > l = physical channel mapped to logical channel 4
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > [port];ddd\n
>>>>>>>> >> >>> >> >>> > where
>>>>>>>> >> >>> >> >>> > ddd = output level, 0 to 100 percent on [port]
>>>>>>>> >> >>> >> >>> > [port]=OT1, OT2, IO3 (OT1 and OT2 are SSR drives;
>>> I/O3
>>>>>> is
>>>>>>>> >> >>> >> >>> > 490Hz
>>>>>>>> >> >>> >> >>> > PWM
>>>>>>>> >> >>> >> >>> > at 5 volts, good for DC fan control)
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > DPIN;pp;HIGH\n or DPIN;pp;LOW\n directly set the
>>> status
>>>>>>>> >> >>> >> >>> > of a
>>>>>>>> >> >>> >> >>> > digital
>>>>>>>> >> >>> >> >>> > pin
>>>>>>>> >> >>> >> >>> > where pp = digital pin number
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > APIN;pp;ddd\n directly set the analog output level of
>>> an
>>>>>>>> >> >>> >> >>> > analog
>>>>>>>> >> >>> >> >>> > pin
>>>>>>>> >> >>> >> >>> > where pp = analog pin number
>>>>>>>> >> >>> >> >>> > ddd = output level, 0 to 100 percent
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > Rev. 5/28/2011
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > Jim
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> > On Fri, May 27, 2011 at 2:53 PM, PIDKits
>>>>>>>> >> >>> >> >>> > <pidkits(a)gmail.com>
>>>>>>>> >> >>> >> >>> > wrote:
>>>>>>>> >> >>> >> >>> >>
>>>>>>>> >> >>> >> >>> >> I am with you now.
>>>>>>>> >> >>> >> >>> >>
>>>>>>>> >> >>> >> >>> >> I'll send a draft command format for your
>>>>> review/comment
>>>>>>>> >> >>> >> >>> >> over
>>>>>>>> >> >>> >> >>> >> the
>>>>>>>> >> >>> >> >>> >> weekend. I've done a little more work on it since
>>> our
>>>>>>>> >> >>> >> >>> >> last
>>>>>>>> >> >>> >> >>> >> email.
>>>>>>>> >> >>> >> >>> >>
>>>>>>>> >> >>> >> >>> >> Jim
>>>>>>>> >> >>> >> >>> >>
>>>>>>>> >> >>> >> >>> >> On Fri, May 27, 2011 at 8:15 AM,
>>>>> sebastien(a)delgrande.org
>>>>>>>> >> >>> >> >>> >> <sebastien(a)delgrande.org> wrote:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Thanks Jim. I will copy the sketch to the Artisan
>>>>>>>> >> >>> >> >>> >>> project
>>>>>>>> >> >>> >> >>> >>> tonight.
>>>>>>>> >> >>> >> >>> >>> I'll try to give it a shot this week-end.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Also regarding your question about how far the
>>> Artisan
>>>>>>>> >> >>> >> >>> >>> team
>>>>>>>> >> >>> >> >>> >>> wants
>>>>>>>> >> >>> >> >>> >>> to
>>>>>>>> >> >>> >> >>> >>> take the roaster control, I must say I am not sure.
>>>>>> This
>>>>>>>> >> >>> >> >>> >>> being
>>>>>>>> >> >>> >> >>> >>> said with the
>>>>>>>> >> >>> >> >>> >>> custom buttons a user could already take it quite
>>> far
>>>>>>>> >> >>> >> >>> >>> (they
>>>>>>>> >> >>> >> >>> >>> can
>>>>>>>> >> >>> >> >>> >>> probably fit
>>>>>>>> >> >>> >> >>> >>> up to 5 buttons on today's screens).
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> As far as I am concerned I would like to have full
>>>>>>>> >> >>> >> >>> >>> control
>>>>>>>> >> >>> >> >>> >>> of
>>>>>>>> >> >>> >> >>> >>> the
>>>>>>>> >> >>> >> >>> >>> roaster from the software. But my point was more to
>>>>>>>> >> >>> >> >>> >>> provide
>>>>>>>> >> >>> >> >>> >>> a
>>>>>>>> >> >>> >> >>> >>> complete set
>>>>>>>> >> >>> >> >>> >>> of "commands" that could be interpreted by an
>>> Arduino
>>>>>>>> >> >>> >> >>> >>> board.
>>>>>>>> >> >>> >> >>> >>> Basically,
>>>>>>>> >> >>> >> >>> >>> since we were at the stage of defining a command
>>>>> format
>>>>>>>> >> >>> >> >>> >>> I
>>>>>>>> >> >>> >> >>> >>> wanted
>>>>>>>> >> >>> >> >>> >>> to see
>>>>>>>> >> >>> >> >>> >>> beyond the TC4 board while still using the same
>>>>> command
>>>>>>>> >> >>> >> >>> >>> format.
>>>>>>>> >> >>> >> >>> >>> Does that
>>>>>>>> >> >>> >> >>> >>> make any sense?
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Thanks,
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Sebastien
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> On May 27, 2011 at 7:56 AM PIDKits
>>> <pidkits(a)gmail.com>
>>>>>>>> >> >>> >> >>> >>> wrote:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Sebastien:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> TC4/Arduino application aArtisan.pde, version
>>>>> 1.04beta,
>>>>>>>> >> >>> >> >>> >>> is
>>>>>>>> >> >>> >> >>> >>> now
>>>>>>>> >> >>> >> >>> >>> available for download here:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>> http://tc4-shield.googlecode.com/files/aArtisan-REL-104beta.zip
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> If you do testing of the upcoming Artisan 0.5.x beta
>>>>>>>> >> >>> >> >>> >>> release
>>>>>>>> >> >>> >> >>> >>> with
>>>>>>>> >> >>> >> >>> >>> the
>>>>>>>> >> >>> >> >>> >>> TC4/Arduino, please use this version of aArtisan and
>>>>>>>> >> >>> >> >>> >>> report
>>>>>>>> >> >>> >> >>> >>> any
>>>>>>>> >> >>> >> >>> >>> problems.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> This is the same code as you posted in the Artisan
>>>>>>>> >> >>> >> >>> >>> googlecode
>>>>>>>> >> >>> >> >>> >>> repository, except that the version number has been
>>>>>>>> >> >>> >> >>> >>> changed
>>>>>>>> >> >>> >> >>> >>> to
>>>>>>>> >> >>> >> >>> >>> reflect the
>>>>>>>> >> >>> >> >>> >>> beta status, and some obsolete #define's have now
>>> been
>>>>>>>> >> >>> >> >>> >>> removed
>>>>>>>> >> >>> >> >>> >>> from user.h
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Thanks.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Jim
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> On Thu, May 26, 2011 at 9:57 AM, PIDKits
>>>>>>>> >> >>> >> >>> >>> <pidkits(a)gmail.com>
>>>>>>>> >> >>> >> >>> >>> wrote:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Sebastien -
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> In the interest of keeping aArtisan up to date with
>>>>>>>> >> >>> >> >>> >>> Artisan, I
>>>>>>>> >> >>> >> >>> >>> plan to
>>>>>>>> >> >>> >> >>> >>> put a new "official" release (Version 1.04) of
>>>>> aArtisan
>>>>>>>> >> >>> >> >>> >>> up
>>>>>>>> >> >>> >> >>> >>> for
>>>>>>>> >> >>> >> >>> >>> download over
>>>>>>>> >> >>> >> >>> >>> on the TC4 googlecode site. It will be the same
>>> code
>>>>>>>> >> >>> >> >>> >>> that
>>>>>>>> >> >>> >> >>> >>> you
>>>>>>>> >> >>> >> >>> >>> have placed
>>>>>>>> >> >>> >> >>> >>> on the Artisan hardware folder, so there shouldn't
>>> be
>>>>>>>> >> >>> >> >>> >>> any
>>>>>>>> >> >>> >> >>> >>> issues
>>>>>>>> >> >>> >> >>> >>> with
>>>>>>>> >> >>> >> >>> >>> consistency.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Have you tested the current working aArtisan
>>> (version
>>>>>>>> >> >>> >> >>> >>> 1.04)
>>>>>>>> >> >>> >> >>> >>> with
>>>>>>>> >> >>> >> >>> >>> the
>>>>>>>> >> >>> >> >>> >>> upcoming release of Artisan? Is it safe to go ahead
>>>>>> and
>>>>>>>> >> >>> >> >>> >>> release
>>>>>>>> >> >>> >> >>> >>> this
>>>>>>>> >> >>> >> >>> >>> version prior to the Artisan new release?
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> You can find my current working trunk source here:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>
>>>>>
>>> http://tc4-shield.googlecode.com/svn/applications/Artisan/aArtisan/trunk/src
>>>>>> /aArtisan
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Jim
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> PS -- Just to refresh memories (mostly mine), the
>>>>>>>> >> >>> >> >>> >>> current
>>>>>>>> >> >>> >> >>> >>> aArtisan
>>>>>>>> >> >>> >> >>> >>> release (1.03) must be told if it is being compiled
>>>>> for
>>>>>>>> >> >>> >> >>> >>> Artisan
>>>>>>>> >> >>> >> >>> >>> 0.3.x or
>>>>>>>> >> >>> >> >>> >>> Artiscan 0.4.x. Different code is activated
>>> depending
>>>>>>>> >> >>> >> >>> >>> on
>>>>>>>> >> >>> >> >>> >>> the
>>>>>>>> >> >>> >> >>> >>> Artisan
>>>>>>>> >> >>> >> >>> >>> release.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> In 0.3.x, the command issued by Artisan was
>>> "READ\n".
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> In 0.4.1, it changed to "RF2000" or "RC2000" without
>>> a
>>>>>>>> >> >>> >> >>> >>> newline
>>>>>>>> >> >>> >> >>> >>> command
>>>>>>>> >> >>> >> >>> >>> terminator.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> So the aArtisan code in release 1.03 could not work
>>>>>> with
>>>>>>>> >> >>> >> >>> >>> both
>>>>>>>> >> >>> >> >>> >>> Artisan
>>>>>>>> >> >>> >> >>> >>> versions. Hence the need for the compile-time
>>> switch.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> The current aArtisan working code (1.04), which has
>>>>> not
>>>>>>>> >> >>> >> >>> >>> officially
>>>>>>>> >> >>> >> >>> >>> been released over on the TC4 site, will support
>>> both
>>>>>>>> >> >>> >> >>> >>> 0.3.x
>>>>>>>> >> >>> >> >>> >>> and
>>>>>>>> >> >>> >> >>> >>> the upcoming
>>>>>>>> >> >>> >> >>> >>> Artisan release. But it will not support Artisan
>>>>>> 0.4.1.
>>>>>>>> >> >>> >> >>> >>> The
>>>>>>>> >> >>> >> >>> >>> new
>>>>>>>> >> >>> >> >>> >>> release of
>>>>>>>> >> >>> >> >>> >>> Artisan, as I understand things, will again append
>>> the
>>>>>>>> >> >>> >> >>> >>> newline
>>>>>>>> >> >>> >> >>> >>> character to
>>>>>>>> >> >>> >> >>> >>> the command strings.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> On Thu, May 26, 2011 at 7:17 AM, Sebastien Delgrande
>>>>>>>> >> >>> >> >>> >>> <sebastien(a)delgrande.org> wrote:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> I forgot one line just before my last bullet point
>>>>>>>> >> >>> >> >>> >>> (inserted in
>>>>>>>> >> >>> >> >>> >>> this
>>>>>>>> >> >>> >> >>> >>> message):
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> · Arduino respond to the serial command of
>>>>>>>> >> >>> >> >>> >>> Artisan
>>>>>>>> >> >>> >> >>> >>> by
>>>>>>>> >> >>> >> >>> >>> sending:
>>>>>>>> >> >>> >> >>> >>> t0,t1,t2
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Thanksn
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> S.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> From: artisan-user-bounces(a)lists.einfachkaffee.de
>>>>>>>> >> >>> >> >>> >>> [mailto:artisan-user-bounces@lists.einfachkaffee.de]
>>>>> On
>>>>>>>> >> >>> >> >>> >>> Behalf
>>>>>>>> >> >>> >> >>> >>> Of
>>>>>>>> >> >>> >> >>> >>> Sebastien
>>>>>>>> >> >>> >> >>> >>> Delgrande
>>>>>>>> >> >>> >> >>> >>> Sent: Thursday, May 26, 2011 7:13 AM
>>>>>>>> >> >>> >> >>> >>> To: 'zb'; 'Mike Wolfe';
>>>>>>>> >> >>> >> >>> >>> artisan-user(a)lists.einfachkaffee.de
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Subject: Re: [Artisan-user] Artisan serial data
>>> format
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Mike,
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> I see that your device is actually Arduino-based. I
>>> am
>>>>>>>> >> >>> >> >>> >>> looking
>>>>>>>> >> >>> >> >>> >>> after
>>>>>>>> >> >>> >> >>> >>> that part of the program these days…
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Please look in the hardware folder of the project
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>
>>> (http://code.google.com/p/artisan/source/browse/#svn%2Ftrunk%2Fhardware).
>>>>>>>> >> >>> >> >>> >>> You will find 2 sketches made for 2 interfaces built
>>>>>>>> >> >>> >> >>> >>> around
>>>>>>>> >> >>> >> >>> >>> Arduino:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> · AD594 is for a simple thermocouple
>>> interface
>>>>>>>> >> >>> >> >>> >>> using an
>>>>>>>> >> >>> >> >>> >>> AD594
>>>>>>>> >> >>> >> >>> >>> chip to linearize/amplify a J thermocouple.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> · aArtisan is for the TC4 shield (see
>>>>>>>> >> >>> >> >>> >>> http://code.google.com/p/tc4-shield/)
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> In a nutshell:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> · Set Artisan to use Arduino TC4 device
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> · Serial communication with Arduino is set
>>> at
>>>>>>>> >> >>> >> >>> >>> 19200
>>>>>>>> >> >>> >> >>> >>> bauds
>>>>>>>> >> >>> >> >>> >>> by
>>>>>>>> >> >>> >> >>> >>> default
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> · Your Arduino must listen to this serial
>>>>>>>> >> >>> >> >>> >>> command
>>>>>>>> >> >>> >> >>> >>> formatted as
>>>>>>>> >> >>> >> >>> >>> such: Read command, unit, arguments, end of line.
>>>>>>>> >> >>> >> >>> >>> Practically
>>>>>>>> >> >>> >> >>> >>> Artisan sends:
>>>>>>>> >> >>> >> >>> >>> "R" + Temperature Unit set in Artisan (“C” or “F”) +
>>>>>>>> >> >>> >> >>> >>> Number
>>>>>>>> >> >>> >> >>> >>> of
>>>>>>>> >> >>> >> >>> >>> temperature
>>>>>>>> >> >>> >> >>> >>> returned after ambient temp (currently hard-coded to
>>>>> 2)
>>>>>>>> >> >>> >> >>> >>> +
>>>>>>>> >> >>> >> >>> >>> arguments on 3
>>>>>>>> >> >>> >> >>> >>> characters (currently hard-coded to none that is
>>>>> “000”)
>>>>>>>> >> >>> >> >>> >>> +
>>>>>>>> >> >>> >> >>> >>> "\n"
>>>>>>>> >> >>> >> >>> >>> (end of
>>>>>>>> >> >>> >> >>> >>> line). For example: RC2000\n
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> · Arduino respond to the serial command of
>>>>>>>> >> >>> >> >>> >>> Artisan
>>>>>>>> >> >>> >> >>> >>> by
>>>>>>>> >> >>> >> >>> >>> sending:
>>>>>>>> >> >>> >> >>> >>> t0,t1,t2
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> · Artisan will assume that t0 = ambient;
>>> t1
>>>>> =
>>>>>>>> >> >>> >> >>> >>> ET;
>>>>>>>> >> >>> >> >>> >>> t2
>>>>>>>> >> >>> >> >>> >>> =
>>>>>>>> >> >>> >> >>> >>> BT.
>>>>>>>> >> >>> >> >>> >>> If no ambient temp sensor, then just send 0 (See
>>> AD594
>>>>>>>> >> >>> >> >>> >>> sketch).
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Happy to help if you need more details for your
>>>>> sketch.
>>>>>>>> >> >>> >> >>> >>> Also, I
>>>>>>>> >> >>> >> >>> >>> think
>>>>>>>> >> >>> >> >>> >>> we would have no problem including your sketch in
>>> our
>>>>>>>> >> >>> >> >>> >>> project
>>>>>>>> >> >>> >> >>> >>> if
>>>>>>>> >> >>> >> >>> >>> you liked.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Regards,
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> S.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> From: artisan-user-bounces(a)lists.einfachkaffee.de
>>>>>>>> >> >>> >> >>> >>> [mailto:artisan-user-bounces@lists.einfachkaffee.de]
>>>>> On
>>>>>>>> >> >>> >> >>> >>> Behalf
>>>>>>>> >> >>> >> >>> >>> Of
>>>>>>>> >> >>> >> >>> >>> zb
>>>>>>>> >> >>> >> >>> >>> Sent: Thursday, May 26, 2011 6:03 AM
>>>>>>>> >> >>> >> >>> >>> To: Mike Wolfe; artisan-user(a)lists.einfachkaffee.de
>>>>>>>> >> >>> >> >>> >>> Subject: Re: [Artisan-user] Artisan serial data
>>> format
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Hi.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Thanks for the pictures. Nice looking device. We
>>> will
>>>>>> be
>>>>>>>> >> >>> >> >>> >>> glad
>>>>>>>> >> >>> >> >>> >>> to
>>>>>>>> >> >>> >> >>> >>> make
>>>>>>>> >> >>> >> >>> >>> your device work with artisan.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> If you send us the device protocol/format, then we
>>>>> will
>>>>>>>> >> >>> >> >>> >>> try
>>>>>>>> >> >>> >> >>> >>> to
>>>>>>>> >> >>> >> >>> >>> add
>>>>>>>> >> >>> >> >>> >>> your device as compatible. Artisan works by using
>>> the
>>>>>>>> >> >>> >> >>> >>> serial
>>>>>>>> >> >>> >> >>> >>> port.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> We need to know if your device accepts serial
>>> commands
>>>>>>>> >> >>> >> >>> >>> and
>>>>>>>> >> >>> >> >>> >>> how
>>>>>>>> >> >>> >> >>> >>> to
>>>>>>>> >> >>> >> >>> >>> interpret the answer from your device. We also need
>>>>> the
>>>>>>>> >> >>> >> >>> >>> serial
>>>>>>>> >> >>> >> >>> >>> settings your
>>>>>>>> >> >>> >> >>> >>> device use. Is there a web link that explains it?
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> In the case it does not use commands we need to know
>>>>>> how
>>>>>>>> >> >>> >> >>> >>> to
>>>>>>>> >> >>> >> >>> >>> start
>>>>>>>> >> >>> >> >>> >>> the
>>>>>>>> >> >>> >> >>> >>> device to send temperature info, and how to
>>> interpret
>>>>>>>> >> >>> >> >>> >>> the
>>>>>>>> >> >>> >> >>> >>> info.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Cheers
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> --- On Thu, 5/26/11, Mike Wolfe <hadad(a)telus.net>
>>>>>> wrote:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> From: Mike Wolfe <hadad(a)telus.net>
>>>>>>>> >> >>> >> >>> >>> Subject: [Artisan-user] Artisan serial data format
>>>>>>>> >> >>> >> >>> >>> To: artisan-user(a)lists.einfachkaffee.de
>>>>>>>> >> >>> >> >>> >>> Date: Thursday, May 26, 2011, 3:35 AM
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Hi:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> I am not sure if this is the right place to make
>>> this
>>>>>>>> >> >>> >> >>> >>> enquiry ,
>>>>>>>> >> >>> >> >>> >>> but
>>>>>>>> >> >>> >> >>> >>> here it is.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> I made a temperature sensor/transmitter to send
>>>>>>>> >> >>> >> >>> >>> information
>>>>>>>> >> >>> >> >>> >>> to
>>>>>>>> >> >>> >> >>> >>> logger
>>>>>>>> >> >>> >> >>> >>> software.
>>>>>>>> >> >>> >> >>> >>> I plan to use this software courtesy of Tom Coxon at
>>>>>>>> >> >>> >> >>> >>> www.toomuchcoffee.com
>>>>>>>> >> >>> >> >>> >>> I would like to try the Artisan version , but I need
>>>>> to
>>>>>>>> >> >>> >> >>> >>> know
>>>>>>>> >> >>> >> >>> >>> the
>>>>>>>> >> >>> >> >>> >>> format of the serial data the software requires.
>>>>>>>> >> >>> >> >>> >>> Can anyone tell me the format of the serial data
>>>>>>>> >> >>> >> >>> >>> required
>>>>>>>> >> >>> >> >>> >>> for
>>>>>>>> >> >>> >> >>> >>> the Artisan logger software?
>>>>>>>> >> >>> >> >>> >>> For the curious, attached are pictures of the probe
>>>>>>>> >> >>> >> >>> >>> unit.
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> I want to know the format of the serial data
>>> required
>>>>>> by
>>>>>>>> >> >>> >> >>> >>> the cs
>>>>>>>> >> >>> >> >>> >>> logger. For example , is it :
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> (temperature) , (time)
>>>>>>>> >> >>> >> >>> >>> (temperature) , (time)......
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> or
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> (temperature), (temperature),(temperature)......
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> or some other?
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Tom Coxton's software requires this format:
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> t1=(value)
>>>>>>>> >> >>> >> >>> >>> t2=(value)
>>>>>>>> >> >>> >> >>> >>> power=(value)
>>>>>>>> >> >>> >> >>> >>> t1=(value)
>>>>>>>> >> >>> >> >>> >>> t2=(value)
>>>>>>>> >> >>> >> >>> >>> power=(value).......
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> Mike
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> -----Inline Attachment Follows-----
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> _______________________________________________
>>>>>>>> >> >>> >> >>> >>> Artisan-User mailing list
>>>>>>>> >> >>> >> >>> >>> Artisan-User(a)lists.einfachkaffee.de
>>>>>>>> >> >>> >> >>> >>> https://lists.mokelbu.de/listinfo/artisan-user
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>> _______________________________________________
>>>>>>>> >> >>> >> >>> >>> Artisan-User mailing list
>>>>>>>> >> >>> >> >>> >>> Artisan-User(a)lists.einfachkaffee.de
>>>>>>>> >> >>> >> >>> >>> https://lists.mokelbu.de/listinfo/artisan-user
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>>
>>>>>>>> >> >>> >> >>> >>
>>>>>>>> >> >>> >> >>> >
>>>>>>>> >> >>> >> >>> _______________________________________________
>>>>>>>> >> >>> >> >>> Artisan-User mailing list
>>>>>>>> >> >>> >> >>> Artisan-User(a)lists.einfachkaffee.de
>>>>>>>> >> >>> >> >>> https://lists.mokelbu.de/listinfo/artisan-user
>>>>>>>> >> >>> >> >
>>>>>>>> >> >
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
