WP34S, first impressions



#29

I finally received my WP34S, cable, xtal and overlay. It took less than a week but it seemed much longer to me ;-) Haven't installed the xtal and capacitors yet, wanted to play "stock" for a while. Re-flashing it with ver 3 (full) went flawlessly (I still keep and old computer with an actual RS232 interface for this type of tasks). Overlay installation didn't go that well, I ruined it, but because I know myself I had ordered two sets and the second time went better, almost perfect. The key top labels was a very easy task (using tweezers of course). I'm surprised with all the efforts put into this project, this has been an excellent work, congratulations to the entire team.

My only problem so far is that the calculator is crashing (freezing altogether) from time to time when doing simple calculations (nothing fancy or elaborated), I wasn't able to find any pattern yet :-(, I realize this is still a beta code, I'd just like to know if someone else is experiencing it or just me. The only way I found to recover it is either a battery pull or pressing the reset button in the back, I've tried almost all the combinations of [on]+[any other key] with no avail.

Thank you in advance.


#30

Did you flash with the latest revsion or with the file included in the zip file?
I had similar problmes with that one.
This is where you find the latest file: http://wp34s.svn.sourceforge.net/viewvc/wp34s/trunk/realbuild/


#31

Ooops, you are right, I didn't flash the latest revision... my bad. Thanks!


#32

I apologize for having put an unstable built into the release ZIP file. I should update it.


#33

Oh, no problem, I should have checked first. It hasn't crashed so far since I updated the FW. :-)

Thank you!


#34

Unfortunately, there were a couple of slightly less than stable versions. The current firmware seems pretty stable.


- Pauli


#35

Compared to the 35s (BTW, I already put it away!) I can consider the WP34S totally bug free! I already tested the program that didn't work on the 35S (due to the jump backward in the program when using Solve) and this one passed the test!

Thank you!


#36

The bugs in the 34S will be different to those in the 35s.

- Pauli


#37

They are ;-)

#38

When I read that I have to put in a capacitor, I blanched. But I understand from you that it isn't required?


#39

It's an option - you will need it for an exact real time clock. See TICKS, TIME, etc. in the manual.

#40

No, you don't have to do the crystal modification. As far as I know the only features you can't use without the modification are the stopwatch and comunication to other 34s' or the PC.


#41

Quote:
the only features you can't use without the modification are the stopwatch and comunication to other 34s' or the PC.

The latter isn't true. Please see pp. 108f of the manual for a procedure.

#42

Even the stopwatch works without a crystal but it is not very accurate.


#43

The released image with stopwatch support won't run without an installed crystal.

- Pauli


#44

Quote:
The released image with stopwatch support won't run without an installed crystal.

- Pauli


You mean someone in the team destroyed part of my hard work? Oh my...
Fortunately, it is easy for a beginner to recompile a better image itsefl :-)


Edited: 25 Mar 2012, 4:00 a.m.


#45

No, Marcus removed the non-crystal support from the stop watch images.


- Pauli


#46

Quote:
No, Marcus removed the non-crystal support from the stop watch images.

- Pauli


I know, I was just joking.


#47

It was just a convenience decision to have more than the 'official' build which does not include the stop watch. I thought it might be useful to have it but for space reasons, the non XTAL option had to go. ;-)

#48

Could I not make a crystal-less stopwatch calibration mechanism similar to the serial port one? It would require a bit of code and a byte of flash space to store the calibration constant.


#49

Quote:
Could I not make a crystal-less stopwatch calibration mechanism similar to the serial port one? It would require a bit of code and a byte of flash space to store the calibration constant.

I had planned to work on it and it still on my list. The problem was the lack of free flash space. But it is also possible to insert the calibration constant in the firmware by editing the .bin file.

If you want to implement a calibration function, feel free to do so and to contact me by email to talk about it.

#50

Quote:


The latter isn't true. Please see pp. 108f of the manual for a procedure.


I can confirm this since I do it all the time. Until the release of the Qt-based emulator for Mac, I had no problem sending RAM contents back and forth between Windows-based emulator and the calc. Now with the Mac emulator I can easily do likewise--indeed, the interface is even simpler as one selects the serial port in Preferences, whereas under Windows one has to create a wp34s.ini file containing the name of the COM port.

Right now, the only glitches I encounter seem related to the Mac emulator's older firmware. For example, if I compile a state file using a wp34s.dat created by the Mac emulator as a "seed", the revised wp34s.dat file ceases to be readable by the Mac emulator, though it works fine in the Windows emulator with much newer firmware. I am looking forward to Pascal compiling and posting a newer version to Sourceforge.


#51

This is the main reason to keep the classic Windows emulator alive. It should be always the same revision as the firmware. The Qt based emulators typically lag behind.


#52

Quote:
This is the main reason to keep the classic Windows emulator alive. It should be always the same revision as the firmware. The Qt based emulators typically lag behind.

I can perfectly make an automatic build and probably even an automatic upload for the Qt emulators.


#53

I ask you kindly to build more often, be it automatically or manually. The problem is that the release ZIP files should match each other's version. Maybe you upload the current builds somewhere else (just create a folder below the emulator directory for the most recent builds). I will keep you posted on any updates to the release binaries. I do them typically after a major bug had surfaced and has been fixed such as recently the bug in the solver causing a crash.


#54

As I said, it is very easy for me checkout & build the 3 distributions for any svn version. Just let me know when you want me to.

So far, the Qt emulator had a beta status in my mind. Once it is really used, we should move to a build/distribute production model.


Edited: 30 Mar 2012, 4:43 a.m.

#55

Quote:
I ask you kindly to build more often

+1 ;-)

#56

Quote:

+1 ;-)


Me 2!


Possibly Related Threads...
Thread Author Replies Views Last Post
  [WP34S] WP34S firmware on the AT91SAM7L-STK dev kit? jerome ibanes 1 401 10-04-2012, 04:59 PM
Last Post: Paul Dale
  [wp34s] Incomplete Gamma on the wp34s Les Wright 18 1,519 12-06-2011, 11:07 AM
Last Post: Namir
  [wp34s] Romberg Integration on the wp34s Les Wright 2 505 12-04-2011, 10:49 PM
Last Post: Les Wright
  HP 10bII+ vs. 10bII first impressions Kevin Colville (S. Africa) 6 679 10-31-2011, 04:38 AM
Last Post: Kevin Colville (S. Africa)
  HP 10bII+ first impressions Jose Gonzalez Divasson 18 1,325 04-20-2011, 03:01 PM
Last Post: Jose Gonzalez Divasson
  HP 12c+ and HP 50g - initial impressions Jose Gonzalez Divasson 44 3,381 11-19-2010, 12:45 PM
Last Post: Gerson W. Barbosa
  First impressions HP30B bt_schmidt 1 307 08-03-2010, 09:16 PM
Last Post: allen
  First impressions of new TI-NSpire CAS Don Shepherd 13 1,087 04-04-2010, 07:31 AM
Last Post: ClausB
  HP 20B - 1st impressions bt_schmidt 30 2,067 09-16-2008, 04:26 PM
Last Post: Marcus von Cube, Germany
  Yet another HP35s first impressions thread Brad Davis 15 1,112 09-10-2007, 02:08 PM
Last Post: Jeff O.

Forum Jump: