Successful build, but still some things to figure out

Discuss building, using, and modifying the Rotary Un-Smartphone.
Post Reply
joelsef
Posts: 12
Joined: Sun Nov 05, 2023 4:37 pm

Successful build, but still some things to figure out

Post by joelsef »

Finished my build. Finally! Build quality came out well.

I got it booted up and lights and display work. However, the numbers dialed do not correspond to the correct number on the display. I'm getting some -1 values too!

One thing I ran into towards the end of the build: It comes with six M2 brass washers, but the instructions specify more. However, I think at least 1-2 of those should use the nylon washer--or should they? I used nylon washers for those last few, and I think they fit better. But maybe that's not right?

Anyway, I need to figure out why the dial is not dialing the correct numbers. I'd love to see if I can make a call! I am using Mint Mobile in the US...not sure if that will work yet but really want to get to a point where I can try.

I did try calling that number from another phone and did not get an incoming call, so I assume it's either not working or something else is wrong.

Justine, should we get the latest firmware from GitHub? or should that already be on the motherboards you sent?
Attachments
IMG_7062-sm.jpg
IMG_7062-sm.jpg (152.7 KiB) Viewed 26038 times
IMG_7061-sm.jpg
IMG_7061-sm.jpg (151.33 KiB) Viewed 26038 times
IMG_7060-sm.jpg
IMG_7060-sm.jpg (83.86 KiB) Viewed 26038 times
zero1tango
Posts: 7
Joined: Sun Jan 07, 2024 4:13 pm

Re: Successful build, but still some things to figure out

Post by zero1tango »

Re. wrong numbers appearing during dialing...
You may want to verify that the lobe of the Cam Gear is touching the limit switch's roller ("Rotary Mechanism" step 6) during assembly. The lobe's position is easy to miss and/or slip out of alignment while scrunching the Mother and Daughter Boards together. It might be helpful to put a dot on the top of the Cam Gear lobe's highest point with a Sharpie to make it easier to orient when placing the gear in the Mother Board.
joelsef
Posts: 12
Joined: Sun Nov 05, 2023 4:37 pm

Re: Successful build, but still some things to figure out

Post by joelsef »

Thank you! I don’t know how many times I had to readjust the gears while I re-attached the boards together. I must have messed this up. Time to take it apart again! 😃
dafe
Posts: 6
Joined: Wed Jan 24, 2024 9:25 pm

Re: Successful build, but still some things to figure out

Post by dafe »

Done with the assembly and repeated reassembly (my fault..).
I also have the issue with the display of 2 whatever dial. Buttons were a bit tricky, I had to cut out and will again have to, for the Fn button. Other than that it went well, considered my experience and finger motor (drummer.. :).
Greetings from merry Glarus
David
User avatar
imyxh
Site Admin
Posts: 23
Joined: Wed Jun 05, 2024 5:28 am
Location: Sky's Edge

Re: Successful build, but still some things to figure out

Post by imyxh »

Regarding the numbers dialing wrong, if you want a perspective from the firmware side of things feel free to check out my comments here: viewtopic.php?p=301#p301

In short, apart from mechanical tweaks you can try:
dafe
Posts: 6
Joined: Wed Jan 24, 2024 9:25 pm

Re: Successful build, but still some things to figure out

Post by dafe »

Hello there again, after a while.
I'm fairly innocent in respect to the various implicit whatabouts in it-rotronics, so:

"Flashing" the firmware is being executed by loading the github files onto the sd card?
There are only the three files on it, contacts, config and sms. Since, hooking the telephone into the computer yields the window-style "marimba" sound but no disk/device appears in the explorer.
I happened to load one of my think pads with linuxmint 21.3 cinnamon (which is really good), but no mounting in sight either.

Sorry for the basic question, but I'm sure one of my fellow rotarians (us holding smartness between the ears rather than under the fingertips, if i may say so..) can help me out for this one.

Thx all,
David
dafe
Posts: 6
Joined: Wed Jan 24, 2024 9:25 pm

Re: Successful build, but still some things to figure out

Post by dafe »

and, thank you, imyxh, for the concise guidance. I will carry them out after i've got my homework done :roll:
dafe
Posts: 6
Joined: Wed Jan 24, 2024 9:25 pm

Re: Successful build, but still some things to figure out

Post by dafe »

Found the step by step instructions for firmware flashing :
https://docs.google.com/document/d/e/2P ... orLRnM/pub
dafe
Posts: 6
Joined: Wed Jan 24, 2024 9:25 pm

Re: Successful build, but still some things to figure out

Post by dafe »

Problems here

GxEPD2-RUSP-main.zip not recognized by Arduino IDE

installed the Zingg version instead

upon upload on RUSP on COM5 (says "Arduino Mega or Mega 2560"):

Sketch uses 574 bytes (0%) of program storage space. Maximum is 130560 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 8183 bytes for local variables. Maximum is 8192 bytes.
avrdude warning: attempt 1 of 10: not in sync
avrdude warning: attempt 2 of 10: not in sync
avrdude warning: attempt 3 of 10: not in sync
avrdude warning: attempt 4 of 10: not in sync
avrdude warning: attempt 5 of 10: not in sync
avrdude warning: attempt 6 of 10: not in sync
avrdude warning: attempt 7 of 10: not in sync
avrdude warning: attempt 8 of 10: not in sync
avrdude warning: attempt 9 of 10: not in sync
avrdude warning: attempt 10 of 10: not in sync
avrdude warning: programmer is not responding; try -xstrict and/or vary -xdelay=100
avrdude error: unable to open programmer urclock on port COM5
Failed uploading: uploading error: exit status 1


Tried removing "-main" in the downloaded .zip, cable working. Green lights in RUSP flashing.

Zingg too different?
User avatar
imyxh
Site Admin
Posts: 23
Joined: Wed Jun 05, 2024 5:28 am
Location: Sky's Edge

Re: Successful build, but still some things to figure out

Post by imyxh »

dafe wrote: Mon Jul 29, 2024 10:00 pm Problems here

GxEPD2-RUSP-main.zip not recognized by Arduino IDE

installed the Zingg version instead
Ah, this is because the way Justine set up the folders, you cannot simply use GxEPD2-RUSP-main.zip. You have to unzip it, find GxEPD2 inside there, and then zip that, and use that.

Alternatively, I just forked Justine's repo (https://github.com/skysedge/GxEPD2) and deleted the outermost folder, so you can just download the zip from there and include it directly.
dafe wrote: Mon Jul 29, 2024 10:00 pm upon upload on RUSP on COM5 (says "Arduino Mega or Mega 2560"):

Sketch uses 574 bytes (0%) of program storage space. Maximum is 130560 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 8183 bytes for local variables. Maximum is 8192 bytes.
avrdude warning: attempt 1 of 10: not in sync
avrdude warning: attempt 2 of 10: not in sync
avrdude warning: attempt 3 of 10: not in sync
avrdude warning: attempt 4 of 10: not in sync
avrdude warning: attempt 5 of 10: not in sync
avrdude warning: attempt 6 of 10: not in sync
avrdude warning: attempt 7 of 10: not in sync
avrdude warning: attempt 8 of 10: not in sync
avrdude warning: attempt 9 of 10: not in sync
avrdude warning: attempt 10 of 10: not in sync
avrdude warning: programmer is not responding; try -xstrict and/or vary -xdelay=100
avrdude error: unable to open programmer urclock on port COM5
Failed uploading: uploading error: exit status 1
This is an annoying problem that just means we are failing to talk to the programmer on the Arduino. It could be that you got a faulty bootloader, faulty firmware for the 16U2, or there is something wrong in the hardware. However, I think sometimes it's just because the phone is running and the serial connection is interfering with the programmer. Try turning the phone off, then uploading immediately after you switch it back on.
dafe wrote: Mon Jul 29, 2024 10:00 pm Tried removing "-main" in the downloaded .zip, cable working. Green lights in RUSP flashing.
Oh, so the upload works then? Interesting. It should have nothing to do with the name of the zip file.

By the way, I just edited the "RUSP Development Notes" page to fix the link to the new firmware, etc.
Post Reply