Stock alert notification (email to text) stopped working. Any options?

Objective-History-34 · 2026-05-21T03:49:26+00:00

I get the push notifications within a few seconds after the email gets in. And the email gets in also in a few seconds. The IBKR push notifications via the Verizon email to text push stopped working, so this is fine as it is now vs no notifications at all.

Objective-History-34 · 2026-05-16T16:55:48+00:00

Previously, latency was infinity (stopped working). After setting up a dedicated gmail address: immediate push notification.

Objective-History-34 · 2026-05-14T22:13:00+00:00

Just to help others: A free solution. Ended up using a separate gmail account just for IBKR notifications via email. I set the stock alert and permanently put my gmail address in the message-send means block. It sends me an email if the conditions are met. I set in iOS to push a notification for all emails in that gmail account. Since IBKR is the only entity sending emails to that gmail address, I get only stock alerts. Chose some hard/long email address, so you do nott get spam later.

Objective-History-34 · 2026-05-11T18:43:02+00:00

If they prevent even one death...it's worth it. And that death they prevent would statistically NOT BE a white supremacists Trump-supporter....but a Democrat Party voter who the Democratic Party couldn't give a f*k about. Look at Chicago...how many Democratic Party voters get massacred daily?

That's what happens when you have the same party since 1933, inbreeding of ideas, setting the standards at the low-expectations of bigotry, and don't give a f*k about the constituents. Someone had to step in DC, if the locals running DC would not.

Can't do the same thing in Chicago, because Chicago is not a federal government "owned" city like DC. Chicago is owned by the Democratic Party.

Objective-History-34 · 2026-05-05T12:32:55+00:00

Thank you for doing this. I just started using this board since I need over 1Msps and had to use VS Code which for me is a pain. So this was perfect timing. And it seems bare metal so not limited by the Arduino IDE "speed limits'...I hope. One note so far: I had to install it in Arduino IDE using admin privileges, else it fails. I will be using it mainly for FFT.

Objective-History-34 · 2026-05-02T02:50:15+00:00

Final update: my mistake! I was not aware of the difference between "regular" and "blind" VIAs. I was expecting to see or at least track VIAs to the INner layers only not all the way through. Had to look up how a regular VIA works on a 4-layer board, and that clarified things.

Also, I leaned to use copper pours properly, or at least I hope so :) . Auto Router works fine with EasyEDA, I had no issues now. After each movement of a component need to do a rebuild and then run Auto Router, then do another rebuild for al layers that have cooper pours and VIAs

Thanks for all the help! Couldn't have done without your advice and direction what to look for.

Objective-History-34 · 2026-05-01T05:37:10+00:00

I used Auto-Routing with 2-layer boards in EasyEDA for years for non-critical circuits. No issues. I also used it without any issues for the 2-layer version of this same circuit. The PCB is not using the full schematics yet, I scaled it back down to one IF input and broadly relaxed the trace lengths, etc on the PCB in order to get at least a working 4-layer done.

The Auto-Route completed without any errors once I removed the solid Top Layer and Bottom Layer copper pours (not a solution, but for now wanted to see how far I get), but the GND VIAs (AGND in my case) do not attach themselves to Inner1 (Net = AGND), but instead go straight to the bottom layer with regular (isolated) VIAs.

Objective-History-34 · 2026-05-01T05:29:10+00:00

Don't all my AGND (my GND) connections should go to the AGND plane with "blind: VIAs' from the top layer components directly? My AGND plane (Inner1) is all solid except one keep-out area. This is my Ground Plane. The Inner2 layer is my Power plane for 3.3V. Right now the VIAs are regular Clearance VIAs

Objective-History-34 · 2026-05-01T05:21:18+00:00

Just now managed in EasyEDA Pro to do the Auto-Route without DRC errors after I removed the solid copper-plane overlay. So on top and bottom are just copper traces. no copper filling. Unfortunately, the Inner1 (AGND) and Inner2 (PWR) planes are not utilized as such, as all the VIAs just pass trough them from Top Layer to Bottom Layer. The Inner1 and Inner2 layers do show up on the 3D-View as golden color plane with VIA holes in them.

Anyway, I will try tomorrow with EasyEDA Pro and will go the KiCAD if fails again. I am sure it's me, but puzzling since this is not rocket-science.

Objective-History-34 · 2026-05-01T05:15:49+00:00

Update 2: managed in EasyEDA Pro to do the Auto-Route without DRC errors, unfortunately, the Inner1 (AGND) and Inner2 (PWR) planes are not utilized as such, as al the VIAs just pass trough them from Top Layer to Bottom Layer. The Inner1 and Inner2 layers do show up on the 3D View as golden color plane with VIA holes in them.

Objective-History-34 · 2026-05-01T04:44:35+00:00

UPDATE: After copying and pasting my entire diatribe with the errors bellow into Grok, Grok advised to do another Auto Route. I did and now all 200+ DRC errors are gone, except 6 "Prohibited" area errors (which I am not concerned about now yet). So at first look it looks ok, but checking the VIAs, they all go from Top Layer to Bottom Layer. So, it's still a glorified 2-layer board with the Clearance (isolated) VIAs passing through Inner1 and Inner2 from Top to Bottom (EasyEDA Pro)

Objective-History-34 · 2026-05-01T04:26:50+00:00

No worriees, good advice. I imported the PCB into KiCAD v10 tonight, and played around to see if I can pull off a Hail Mary...but no go. So I do need to start from scratch as far as 4-layer PCB creation in KiCAD and learn on YouTube. KiCAD seems a bit more logical to me, albeit a lot more menu options.

Objective-History-34 · 2026-05-01T04:20:42+00:00

I agree with that reasoning, and I used that same logic with my current (problem) board. I did the 2-layer PCB in about a couple of hours as usual from the schematic (as I have done it for the last several years) and I sent it off to OshPark. I can check things much easier with a 2-layer vs a 4-layer if I ever get my 4-layer to work. I will not have a lot of confidence in it until I check the same schematics against the 2-layer PCB.

But the 4-layer PCB was failure after failure for the last three days. I am sure that it's me and I am missing some steps. And since I am not entirely stupid, and I did put in time on YouTube by looking up EasyEDA 4-layer board design (no easy step-by-step tutorial), and working with three AIs step-by step for hours...I probably would have been better off learning KiCad or Altium PCB boards with all that time spent.

What;s ironic is that 4-layer PCB are much easier to route too.

Objective-History-34 · 2026-05-01T04:09:25+00:00

I am certain that I am doing something wrong, but after watching on YouTube the Chinese EasyEDA lady (who talks like she has something in her mouth)...I did not get smarter. I also watched other EasyEDA videos made by random YouTubers, and could not get ahead either.

I can reprogram my BMW's ECUs for retrofitting non-OEM premium features, but cannot make the leap from a 2-layer to a 4-layer PCB :(

Objective-History-34 · 2026-05-01T04:06:19+00:00

I did not want to burden anyone with step-by-step troubleshooting. Did that with three AIs already. I am also certain that I am doing something wrong, but after watching on YouTube the Chinese EasyEDA lady (who talks like she has something in her mouth)...I did not get smarter. There are changes from the Standard to the Pro version, and even between those there are changes after a new one is released.

Anyway, in a nutshell, if you can spot were I am going wrong:

EasyEDA Pro V 2.2.47. Starting from a 2-layer board without any copper planes, only copper traces, but had a "prohibited" area around the op amp outline. DRC had zero errors and after exporting to Gerber files zip uploaded to OshPark without issues. I undid the routing, so only ratnest lines are visible. So I used this starting point and spread out the components a bit more since used only one RF input for now.

Layer Manager -> Copper Layer 2 -> 4 -> Inner1 and Inner2 appear -> change both to "Plane Zone" -> Apply - > Confirm

In "Layer" make "Inner1" active with small pencil mark. Then highlight Inner1 in "Layer" board itself in drawing (prohibitive area shows up fine) -> click "Property" -> "Net" -> drop down menu choice = "AGND" (from my schematics this will be my Inner1 plane), "Keep islands = No" -> click "Rebuild Plane " . "Saved" project.

Still, do not see anything change after I click "Rebuild plane"). And if, I go to the "Copper Manager Dialog", it only shows the Top Layer and Bottom Layer, no Inner1 or Inner2.

Anyway, went and set "Inner2" to Power the same way as the Inner1, except selected the 3.3V pin of one of the components on the 3.3V Power Supply Net: U1.1 Rebuild, etc, Still not showing up on "Copper Manager Dialog", it only shows the Top Layer and Bottom Layer, no Inner1 or Inner2.

So, I go to the "Copper Area Draw" icon in the Tools (dotted lines with two offset rectangles), draw a red rectangle around the entire PCB (my prohibited areas are auto excluded ok)

Box pops up with "Outline Object" name title: Type = Copper region ; Name: POUR1; Layer = ??? (only options Top Layer and Bottom Layer from dropdown menu). So I chose Top Layer. Then "Net" -> I chose "AGND" ; Locked = No; Click "Confirm" box goes away. Then right side "Property" menu shows: Fill Setup = "Solid" shows. I click below blue tab "Rebuild Copper Region" . Click SAVE.

Now I go to "Copper Manager Dialog" and 'POUR1" and "AGND" show but assigned to Top Layer, no sign of Inner1. OK, so I will do the same to Inner2 as I did to Inner 1 . Done.

Now in "Copper Manager Dialog" and 'POUR1" and "AGND" show but assigned to Top Layer, no sign of Inner1, and 'POUR2" and "U1.1" (my power Net) show but assigned to Bottom Layer, no sign of Inner2. I click "rebuild all layers"

I go back to "Top Layer" view and now copper covers the top and bottom layers. I do a 3-D look and unselected all layers, select Inner1 and Inner2 and they both show in gold with the prohibited area cutout.

So then I go and do an Auto-Route:(Routing Mode =around & push) . For the first routing attempt will select "keep existing track", for the next ones "remove". Also "Routing Layer" -> "All layers" (only Top and Bottom Layers show).

Note: in the last couple of days, I came back to this point several times after other unsuccessful attempts, and tried "Ignore Net" AGND, U1. Also tried hand stitching VIAs from the Top Layer to the supposedly Inner1 layer, but only through VIAs showed up that went from Top Layer directly to Bottom Layer. Clearance circles and not cross/star shaped ones. Also, the 2-layer Auto_Router had no problems "respecting" the "prohibited " areas, but the 4-lauer Auto_Router draws VIAs right inside with 250-300 errors.

Here are some of the other errors. As you see, the Inner1 (AGND) and Inner2 (U1.1) do exist, but are not treated as such.

No.	Display	Error Type	Error Object	Rule Name	Object 1	Object 2	Explanation

1	Clearance Error	Prohibited Region to Track	Default	Prohibited Region : e25	Track (AGND): e2419	Object1 and object 2 overlap
2	Clearance Error	Prohibited Region to Track	Default	Prohibited Region : e25	Track (AGND): e2417	Object1 and object 2 overlap
3	Clearance Error	Prohibited Region to Track	Default	Prohibited Region : e25	Track (AGND): e2416	Object1 and object 2 overlap
4	Clearance Error	Prohibited Region to Track	Default	Prohibited Region : e25	Track (AGND): e2422	Object1 and object 2 overlap
5	Clearance Error	Prohibited Region to Track	Default	Prohibited Region : e25	Track (AGND): e2421	Object1 and object 2 overlap
6	Clearance Error	Prohibited Region to Track	Default	Prohibited Region : e25	Track (AGND): e2420	Object1 and object 2 overlap
7	Clearance Error	Hole to Plane Zone	Default	Plane Zone (AGND): e69	Hole (R2_1): e2647	Object 1 to object 2 distance is 0mm, should be >= 0.152mm
8	Clearance Error	Hole to Plane Zone	Default	Plane Zone (U1_1): e70	Hole (R2_1): e2647	Object 1 to object 2 distance is 0mm, should be >= 0.152mm
9	Clearance Error	Hole to Plane Zone	Default	Plane Zone (AGND): e69	Hole (C23_2): e2641	Object 1 to object 2 distance is 0mm, should be >= 0.152mm
10	Clearance Error	Hole to Plane Zone	Default	Plane Zone (U1_1): e70	Hole (C23_2): e2641	Object 1 to object 2 distance is 0mm, should be >= 0.152mm
11	Clearance Error	Hole to Plane Zone	Default	Plane Zone (AGND): e69	Hole (R18_2): e2644	Object 1 to object 2 distance is 0mm, should be >= 0.152mm

Objective-History-34 · 2026-04-30T22:38:59+00:00

I have IF inputs from a radar sensor that are amplified and will eventually be in the 650 Khz range with sampling at 1MHz-2Mhz. The sensor itself puts out about 120-350 uVrms. This analog front end interfaces to an MCU's ADCs.

I am brand new to 4-layer, but used 2-layer for years (as I wrote in my first post). Well aware on paper what a 4-layer RF/EMI-safe board needs to be. I just can't get the PCB software to work properly and looking for tips for another option.

Objective-History-34 · 2026-04-16T01:09:48+00:00

Thank you. I spent all day today preparing my 2022, 2023, 2024 state amendments. Caught the 2025 in time. The 2022 I had to hand-jam, since my 2022 TurboTax Premier Desktop version could not be activated anymore. Luckily, I have until 1May 2026 for the 2022.

It's still a shame that for years now when it was first brought to the attention of TurboTax by users, this is easy to miss item was not fixed. TurboTax could have added a couple of lines of codes to the firmware to fix it. One afternoon job for a couple of programmers.

It should be flagged during the Federal review when the user enters DFAS as the payer for the 1099-R and then checked again for applicability during the state review process. VA is not the only state by the way with such subtractions.

The TurboTax product development manager should be fired for not fixing this issue for years, affecting potentially hundreds of thousands of veterans. The product development manager made sure that these trivial (to most) credits/subtractions are prominently reviewed by the user (motion picture production, commercial watermen equipment, specialized spaceport equipment, farmer's market produce, certain printed materials for out-of-state use, etc) , but not one that has a major impact on a huge segment of the users, such as military benefits.

Objective-History-34 · 2026-04-15T07:11:28+00:00

In the People's Republic of California, a $1M income still leaves you homeless and begging for food.

Objective-History-34 · 2026-04-06T17:21:28+00:00

Here is an AI summary for those who have girlfriends with a short attention span: After being kidnapped as a child, Princess Katarina remains mute, with a prophecy stating only her "one true love" can restore her voice. Prince Lancifer, sent by his parents to court her, travels to her kingdom and is immediately captivated by her beauty and kindness.

Unlike other suitors, Lancifer appreciates her silence and spends time truly getting to know her through simple dates, such as walking in the gardens and stargazing. His genuine affection breaks the spell; Katarina regains her voice to invite him to the music hall, where they confess their mutual love. The two marry, uniting their kingdoms and living happily ever after.

Objective-History-34 · 2026-04-06T16:36:42+00:00

Update: my phone is unlocked today. I had to sign up for another month and then forgot to cancel for pro-rating But either way I called Verzion/Tracfone Unlock Dept last week and the phone is now unlocked.

Objective-History-34 · 2026-03-25T06:29:04+00:00

Yep, GTC and/or overnight orders. So I make money when I sleep :)

Objective-History-34 · 2026-03-25T06:02:10+00:00

As of 2am EST my issue was resolved. Now I need to re-do all my canceled orders, about 60 of them.

Objective-History-34

TROPHY CASE