09-18-2015, 10:07 PM
(09-18-2015 05:43 PM)Massimo Gnerucci Wrote: [ -> ](09-18-2015 04:24 PM)Namir Wrote: [ -> ]Dave,
You should be able to convert it to an HP-16, HP12C, or HP-11C.
Namir
A 10C or, maybe, even a 41C.
Will this do?
(09-18-2015 05:43 PM)Massimo Gnerucci Wrote: [ -> ](09-18-2015 04:24 PM)Namir Wrote: [ -> ]Dave,
You should be able to convert it to an HP-16, HP12C, or HP-11C.
Namir
A 10C or, maybe, even a 41C.
(09-18-2015 10:07 PM)brickviking Wrote: [ -> ](09-18-2015 05:43 PM)Massimo Gnerucci Wrote: [ -> ]Will this do?(09-18-2015 04:24 PM)Namir Wrote: [ -> ]You should be able to convert it to an HP-16, HP12C, or HP-11C.A 10C or, maybe, even a 41C.
(09-18-2015 03:04 PM)Dave Frederickson Wrote: [ -> ]was in response to Dave Britten's comment.(09-18-2015 11:26 AM)Dave Britten Wrote: [ -> ]Holy crap. Anxiously awaiting a 16C...In the mean time, flash it with the 16C firmware and make an overlay.
(09-18-2015 10:07 PM)brickviking Wrote: [ -> ](09-18-2015 05:43 PM)Massimo Gnerucci Wrote: [ -> ]A 10C or, maybe, even a 41C.
Will this do?
(09-18-2015 08:58 AM)jebem Wrote: [ -> ]On a more positive note, if Swissmicros can do it, why on earth is so hard to get the vapourware 43S hardware built in the same way and cost?
(09-18-2015 08:58 AM)jebem Wrote: [ -> ]On a more positive note, if Swissmicros can do it, why on earth is so hard to get the vapourware 43S hardware built in the same way and cost?Maybe it is easier and more tempting to stea..., erm reproduce a given design with a known large target audience.
(09-19-2015 07:33 AM)Paul Dale Wrote: [ -> ](09-18-2015 08:58 AM)jebem Wrote: [ -> ]On a more positive note, if Swissmicros can do it, why on earth is so hard to get the vapourware 43S hardware built in the same way and cost?
Feel free to offer your time and expertise to help produce the 43S hardware.
It's obviously an easy task.....
- Pauli
(09-18-2015 11:26 AM)Dave Britten Wrote: [ -> ]Holy crap. Anxiously awaiting a 16C...
(09-19-2015 03:56 PM)Dan B Wrote: [ -> ]A 42s version would be perfect for my needs/wants if the keyboard feel is good!
(09-19-2015 03:56 PM)Dan B Wrote: [ -> ]A 42s version would be perfect for my needs/wants if the keyboard feel is good!
(09-20-2015 06:13 PM)Chasfield Wrote: [ -> ]Seeing more of the stack, via a two line display, would be cool, as Matthias suggests. I guess the original 15C ROM code would have to be broken into and quite heavily re-engineeered to achieve this - a bigger job than just getting the original version to run, as is, on an emulation layer.While I have no direct insight into their implementation, I don't think it would be very difficult. After all, the Y register of the emulated machine must be stored somewhere in the microcontrollers RAM. I assume that it is quite easy to find out where it resides, even if the emulated code isn't fully understood. Once this location is known, it could be read out periodically (or at certain events) from outside the emulator's domain (that is by the operating system or driver layer underneath the emulator). The numeric contents could then be decoded and translated into whatever representation is necessary to display it on the pixel display. Just reading out the Y register at random times in a concurrent process might cause some temporary garbage to be displayed if the multi-byte register is read out at the same time as it is being updated by the emulated machine, but I'm quite sure that the emulator provides enough state-information to let the read out happen in a mutex and only when appropriate. In fact, it is possible, that a similar technique is used already in order to retrieve and translate the X register value.
Quote:Hello Jose,
our new calculator has a single plastic part which required a mold of two parts. We designed the plastic part in a 3D modeling software, based on that the producer made a 3D model for the mold.
The cost for the mold was about USD7000.
Usually it doesn't make sense to produce less than 1000pcs. The setup-cost for each run is equal to several hundred units.
What are real keys? Our calculator has a PCB with contact areas for the domes under the keys.
I'm not sure this is of any help for you.
Best regards,
Michael Steinmann
(09-20-2015 08:12 PM)matthiaspaul Wrote: [ -> ](09-20-2015 06:13 PM)Chasfield Wrote: [ -> ]Seeing more of the stack, via a two line display, would be cool, as Matthias suggests. I guess the original 15C ROM code would have to be broken into and quite heavily re-engineeered to achieve this - a bigger job than just getting the original version to run, as is, on an emulation layer.While I have no direct insight into their implementation, I don't think it would be very difficult. After all, the Y register of the emulated machine must be stored somewhere in the microcontrollers RAM. I assume that it is quite easy to find out where it resides, even if the emulated code isn't fully understood. Once this location is known, it could be read out periodically (or at certain events) from outside the emulator's domain (that is by the operating system or driver layer underneath the emulator). The numeric contents could then be decoded and translated into whatever representation is necessary to display it on the pixel display. Just reading out the Y register at random times in a concurrent process might cause some temporary garbage to be displayed if the multi-byte register is read out at the same time as it is being updated by the emulated machine, but I'm quite sure that the emulator provides enough state-information to let the read out happen in a mutex and only when appropriate. In fact, it is possible, that a similar technique is used already in order to retrieve and translate the X register value.
Matthias
(09-21-2015 02:30 PM)Mike (Stgt) Wrote: [ -> ]Anyway the demand was "bring back the 15C" and not "bring back the 42S".