Jump to content


  • Posts

  • Joined

  • Last visited

GalD101's Achievements

Prolific Poster

Prolific Poster (4/4)



  1. How should I create a "Hello World!" program? making it using the same logic I applied previously for the "UUUU" or "AAAA" seems cumbersome and also pretty bad in terms of memory (using a lot of bits for the counter).
  2. Hurray! That's the code. Not very pretty and I know I can use an else without an "else if" but during my debugging progress I added that and I found a few bugs when writing it. Also, the off-by-one error was present since I hard-coded those numbers and made a mistake when copying them. Yes, I know it's a bad practice to leave numbers that seem random in a program instead of using localparams or simply writing them as a multiple of 868 (while keeping 868 as a constant) but I am going to try to change it anyway so it would say "Hello World!". I'll also add the small drawing I made, It's not very readable but that was the way I thought about implementing it. I think there are cleverer ways to implement this but this was my naive approach for this. Let me know if there are better ways to implement it (other than obviously making my "if" and "else if" conditions a bit cleaner). Perhaps a better approach is to create an fsm for every letter? and on every instance give it a parameter of how many characters I want to display and thus creating another layer of abstraction? Is that type of approach good or is it not practical? finite_state_machine.sv note: doing this instead of data structures hw because it's fun lol
  3. That's cool it actually works (The problem was that the settings in the program were faulty) next will be "AAAAA" and then the classic "Hello World"
  4. "Our preliminary estimation is that if we are able to measure 100 coincidences per second, our measurement time becomes ~4-5 hours to get a target level of confidence of 4 sigma. The question now is how many coincidences do we expect to have out of single events. This is a more tricky question that we are trying to estimate now. It seems that we need to target the count rate of 100 000 single events per seconds."
  5. He said it's as simple as pressing a button to generate less photons per seconds. Please excuse me if I misunderstood your question
  6. Well at least that's something (getting white space non stop instead of U). Don't tell me why. I'll try to solve it myself. Sorry I didn't answer I just had a 6 hour lecture of Data structure. I will soon meet with my professor to discuss about the experiment
  7. Unfortunately I don't have a definitive answer as to how many coincidences we expect to capture in one second but I'll try to figure out by asking some folks here. For now all that I know is that the max is 20M so anything above that would be redundant.
  8. Note that this is the maximum so my prof would like me to build a system that can handle the max, but it would be OK if it would be a bit less than the max
  9. "The single photon detector dead time is about 50ns therefore we do not need to measure faster than 20MHz. The system should be ready to count the coincidence rate as high as 20MHz."
  10. What will this status represent? Why 9? Is it because each character is 4 bits so you doubled it and added 1 for the parity stop bit? 7N1 means 1 start bit, 7 bits of data No parity bit and 1 stop bit? Why 108? Because 4M / 108 approximately equals to 37,000? Why 234? because 4M / 234 approximately equals to 17,000? I asked my prof for this, he said he needs to check so I'll update you when I have an answer
  11. according to what you said I think I should modify it like so: wire [10:0] next_counter = (r_counter + 1) % (11'd1736); wire next_fsm_out = (next_counter < 10'd868) ? 1'b1 : 1'b0; (changed 867 to 868)
  12. that's weird because I programmed the device with it and it seems to show the same behavior. I probably missed something when compiling. Thanks for letting me know I'll check
  • Create New...